Frontend development in Perth
Perth is where remote operations were made normal: rail networks, fleets and plants run from rooms in the city, hundreds of kilometres from the equipment. The screens around the control systems (planning boards, shift handover views, performance dashboards) are read by people on long shifts who need to see a problem at a glance and cannot afford to misread one.
We build React frontends for that environment on the business side of the OT line: dense views that stay readable, colour used for meaning rather than decoration, dark themes that suit a control room, and layouts tested at the distance and screen size they will actually be read at. We work from real shift scenarios with your operators, so each view puts first what they look for first.
Perth runs mines it cannot see. Rio Tinto controls trains, trucks and drills in the Pilbara from its operations centre in Perth, BHP runs much of its Western Australian iron ore logistics from a remote operations centre in the city, and Woodside, Fortescue and Chevron Australia keep their head offices here. Around them sits a large sector of engineering consultancies, contractors and mining equipment, technology and services firms. Most of the software work in the city exists to serve that industry, and it comes with that industry's habits: safety first, careful change control and very little tolerance for downtime.
The line that matters is between operational technology and everything else. Control systems, autonomous haulage and plant automation belong to specialists. The opportunity for outside engineers is on the business side of that line: maintenance and shutdown planning, historian data read out for analysis, contractor and workforce systems for a fly-in fly-out workforce, reporting, and the internal tools that stitch them together. Energy and utility businesses need the same kind of work, and beyond resources the state has its own buyers, from agencies and universities in the city to the wineries of Margaret River selling across the continent.
Hiring is shaped by the resources sector, which competes hard for experienced engineers and can pay for them. Indeed puts the average base salary for a software engineer in Perth at A$100,253, from 59 reported salaries, and a consultancy or scale-up bidding against a mining major for the same person often waits a long time. That is where we fit: senior engineers on a defined piece of work within days, with the code in your repositories from the first commit.
Our four hours of daily overlap land in your afternoon, moved to suit your team. Perth is the closest Australian capital to India's time zone, and neither Western Australia nor India uses daylight saving, so the window sits at the same point in your day all year. Your morning is for your own team and the site calls; the afternoon is for stand-ups, reviews and decisions with the engineer who writes your code.
We are the right fit for defined work on the business side of the operation: data, reporting, maintenance and workforce tools, and contractor systems. Senior engineers start within days, the first piece is a fixed-price two weeks, and we can carry the roadmap through the months before your own hire starts. Agencies can put the work under their own name.
Four ways this arrives.
We measure on real devices and real traffic first, not a lab score on a fast laptop. The fix is usually less JavaScript: a smaller bundle, images sized for the screen, and third-party scripts that stop blocking the first render.
A procurement checklist, a customer complaint, or a letter from a lawyer. We fix the causes rather than the line items: real buttons, labelled forms, focus that lands somewhere sensible, and automated checks in CI so it stays fixed.
Global state that everything reads, no types, and three versions of the same modal. We add TypeScript file by file, put tests on the flows that make money, and move shared pieces into one component library as screens are touched.
Usually for search visibility or first-load speed. We move it route by route behind the same URLs, so the old app keeps serving while the new one takes over, and nobody has to sign off a risky weekend cut-over.
A Next.js web app with five operational dashboards and Tableau reports rendered in place, without a second login.
Read the write-up →Asked by Perth teams.
How do you work with teams in Perth?+
We are in Bengaluru, and four hours of every working day overlap with your afternoon, moved to suit your team. Perth is the closest Australian capital to India's time, and neither side changes its clocks, so the window stays put all year. Stand-ups, code reviews and design calls happen live in it. We work in your tools, whether that is Slack, GitHub or Linear, and every call is with the engineer who writes the code.
Do you build for mining and energy companies?+
Yes, on the business side of the operation. We build pipelines that read historian data out for analysis, maintenance and shutdown planning tools, contractor management platforms, apps that put a FIFO worker's roster, flights and documents in one place, and dense planning views for remote operations teams. We integrate with the maintenance, HR and procurement systems you already run, and start with the problem that costs you most on site.
How does your rate compare to hiring in Perth?+
Indeed puts the average base salary for a software engineer in Perth at around A$100,000, and the resources sector often pays more to win experienced people. Our published rate is $35/hour with a $5,000 minimum, or $5,400 a month for one embedded engineer. There is no recruiting time and no employment overhead, and work can start within days. The first piece is a fixed-price two-week engagement at $2,800, so you judge us on what ships.
What do the first two weeks look like?+
You share the context, with an NDA signed before anything specific. Within two days you are on a 30-minute call with the engineer who would do the work, and within a week you have a written plan. Then comes a fixed-price two-week piece for $2,800: one real thing, such as a maintenance report, a contractor portal screen or a data feed, built in your repositories and reviewed with you in your afternoons.
Do we need to move to Next.js?+
Not always. If the app sits behind a login and nobody finds it through search, a well-built React single-page app on Vite is simpler to host and easier to reason about. Next.js earns its keep when first load and search visibility matter, or when you want rendering close to the data. We will tell you which case you are before anyone rewrites a route.
Can you work from our Figma files?+
Yes, and we will ask questions about them. Designs rarely show the loading state, the empty state, the error, or what happens when a name is twice as long as the mock-up assumed. We raise those early and propose something, rather than inventing it quietly in code and leaving your designer to find out in review.
Will you build us a design system?+
We will build the one your product needs, which is usually smaller than people expect: design tokens, the components you actually use, and Storybook to show them. We extract it from the screens you already have rather than designing it in isolation, because a component library nobody migrates to is just a second way of doing things.
How do you handle accessibility?+
We build to WCAG 2.2 AA by default, test with a keyboard and a screen reader, and run automated checks in CI so regressions are caught before they ship. Automated tools find only part of the problem, so we also test the key journeys by hand: sign-up, checkout, and anything a user does every day.
Do you only do the front end, or the API as well?+
Either. A lot of front-end pain is really an API shaped for a different screen, and when that is the case we can fix both sides. If your backend team owns the API, we write down what the front end needs from it and agree the contract with them, rather than working around it in the browser.