Geminum is engaging a mid-level Frontend Engineer for 2 months to build the web app front end for a digital twin. You join the Web App Squad in the engineering team, working side by side with the Design Lead and a Fullstack Engineer.

Title: Frontend Engineer
Team: Engineering Team, Web App Squad
Reports to: Engineering Lead
Works Closely With: Design Lead and Fullstack Engineer
Engagement Length: 2 Months
Location: Remote. Australian business hours, or US hours with daily overlap with the AU day. AU preferred.
Start Date: Immediately

About Geminum

Geminum is a Brisbane-based company that makes physical AI for heavy industry: live digital twins of industrial sites, and autonomy for the machines that work in them.

Purpose of the Role

This role closes the gap between design and working software for our digital twin platform. Designs often start as sketches, low-fidelity wireframes or prototypes. You turn them into a working front end and the API behind, then refine them with the Design Lead until they're right.

You own features end to end, from the screen to the endpoint, with the Fullstack Engineer alongside you on the API and data behind them. As a mid-level engineer, you get design direction and code review, and you're trusted to fill gaps with good judgement and finish work without close supervision.

This isn't an infrastructure or data-platform role: you build the API layer the web app talks to, not the pipelines behind it.

Reporting Line and Key Relationships

You report to the Engineering Lead and ship through engineering, and work every day in a three-person Web App Squad with the Design Lead and the Fullstack Engineer.

Working in the Web App Squad

You're a full member of the engineering team, working day to day in a three-person Web App Squad with the Design Lead and a Fullstack Engineer. Your line, standards and code review come from engineering; your closest collaborators are the other two people in the squad.

With the Design Lead, you:

- Work together every day, turning sketches, wireframes, briefs and prototypes into production-ready builds.
- Put a working build in front of the Design Lead.
- Review on the real screen with real or realistic data, then refine together.
- Ensure edge cases are covered, including: loading, errors, stale or missing data, late and out-of-order updates.
- Push back and work with the Design Lead on alternatives when a design is costly to build
- Build and extend shared components and design tokens together so the product stays consistent.

With the Fullstack Engineer, you:

- Agree the API contracts each screen needs,



and shape the API layer together.
- Pair on features that cross the screen and the endpoint, so front end and API changes ship together.
- Work out how live data reaches the browser and how the UI handles it arriving late or out of order.
- Review each other's code and share context with platform engineers on the services underneath.

As a member of the engineering team, you:

- Report to the Engineering Lead, who sets priorities with the Product Lead and owns architecture and engineering standards.
- Ship production code through the team's process: code review, testing, security practices and release.
- Raise technical risk early, and explain trade-offs in terms the squad and the Product Lead can act on.

The squad's working loop:

- The Design Lead brings a sketch, wireframe, prototype or brief, against priorities agreed with the Product Lead.
- You build a working version, with the Fullstack Engineer shaping the API and data behind it.
- The three of you review it on screen and decide what changes.
- You iterate until it's right, then harden it (tests, accessibility, edge states) and ship through engineering review.

Key responsibilities

- Build and maintain the Digital Twin web app: the front end and the API layer (backend-for-frontend) that serves it.
- Turn the Design Lead's designs into working screens quickly, then iterate together to the final version.
- Shape API endpoints around what the screens need with the Fullstack Engineer, with platform engineers owning the services underneath.
- Build live, data-heavy views: status, telemetry, alarms, tables, charts, plan views and the 3D twin.
- Push live updates to the browser (WebSockets or server-sent events) and keep the UI consistent when data arrives late or out of order.
- Give every view clear loading, error, stale and missing-data states.
- Contribute to the shared component library and design tokens with the Design Lead.
- Write tests, take part in code review, and meet engineering standards for quality, accessibility and security.
- Use coding agents effectively, and review and test everything they produce.
- Document decisions as you go, and hand over cleanly at the end of the contract.

Essential skills and experience





- Production experience with React and TypeScript, on web apps people use every day.
- Node and TypeScript on the server: APIs and a backend-for-frontend in production, including auth and sessions, validation, caching, pagination and error handling.
- Live updates in the browser (WebSockets or server-sent events), with a consistent UI when updates arrive late or out of order.
- A modern React framework and component-driven UI.
- Comfortable working day-to-day in a small squad with a designer and another engineer: turning rough sketches into working software, agreeing API contracts, and refining it together.
- Strong design and product sense. You can take a one-line brief, fill the gaps with good judgement, and show a working version fast.
- Comfort with iteration.
- Data-heavy interfaces: tables, charts, maps and live-updating views.
- Solid CSS and layout, accessibility, and responsive design that works on tablets and large control-room screens.
- Proficient, current use of coding agents, with the habit of reviewing and testing their output.
- Clear communication across disciplines. You ask good questions early, explain decisions plainly, and finish work without close supervision.

Desirable skills and experience

- Figma, design systems and design tokens, and a habit of working inside a designer's files.
- Typed contracts shared between client and server.
- 3D in the browser.
- Exposure to NVIDIA Omniverse or Isaac Sim.
- Data visualisation.
- Maps, plan views and geospatial UI.
- SQL databases, enough to shape the queries your screens need.
- Deploying Node services on AWS.
- UI and API testing.
- Motion and micro-interaction design.
- UX for industrial, operational or safety-critical software.

Success measures

By the end of the 2-month contract, success looks like this:

- Agreed Digital Twin screens are live in production, built from the Design Lead's designs and signed off by the Design Lead and the Product Lead.
- The Design Lead sees a working version of new work within days of handing it over.
- The Design Lead and the Fullstack Engineer describe the squad's collaboration as quick and low-friction.
- Code meets engineering standards and passes review without major rework.
- Live views stay correct and usable under late, missing or out-of-order data.
- Shared components are reusable and documented, so the team can keep building after you leave.
- Handover notes let another engineer pick up any feature you owned.

Geminum is an equal opportunity employer and welcomes applicants from all backgrounds.

📌 Frontend Engineer (Adelaide)
🏢 Geminum
📍 Adelaide