Product Designer

WHAT APHEX DOES

Aphex is the execution platform for major construction projects, the connected system where teams plan their upcoming work, coordinate their day-to-day, and capture the daily record. Everything draws from the same live plan.

Major contractors like Acciona, CPB Contractors, John Holland, and McConnell Dowell use Aphex to deliver projects from £50 million to multi-billion pound mega projects. We're market-leading in Australia and the United Kingdom, supporting teams building the roads, rail, tunnels, and hospitals that millions use every day.

Your mission: design Diary, our production tracking and record capture product — mostly on mobile, where the capture actually happens.

The opportunity: right now, what happens on a construction site lives in scattered notes, photos, and rigid forms that nobody looks ry is our answer to that: records connected to the live plan rather than siloed, capture low-friction enough that people on site actually do it, and AI woven through so insight surfaces on its own instead of staying buried.

That's the near-term product. The longer game is bigger. We want to become the capture layer for major projects worldwide, and then build the intelligence layer on top of it — a system that can tell a project team what really happened last month and what's likely to happen next. None of that works unless capture works. Which makes the design of it a fairly interesting problem to be handed.

Most of that capture happens on mobile, out on site. The people using it aren't y're site managers in PPE, foremen sharing a tablet, engineers moving between zones with patchy connectivity and gloves on. Designing for that is a different craft from designing for desktop, and it's where the magic in this product is. It's also where the gap between our ambition and our execution is currently widest.

We want Diary to be the rare bit of construction software people are actually pleased to open. That comes down to care taken in small places: the weight of a tap, how a photo lands, what the app does when the signal drops halfway through an entry, whether the thing feels quick in the hand at the end of a twelve‑hour shift.

Delight isn't decoration on a product like this — someone standing in the rain will simply stop using anything that makes them work for it, and then there's no record ting that right is most of the job.

It isn't only mobile, though. We organise around products rather than platforms, so the Diary team owns capture end to end — everything recorded on site has to be reviewed, reported on and made sense of, and that happens on the web. You'd design both. Mobile is the centre of gravity and where most of your time would go; the web side is the other end of the same story rather than a sideline.

You'd join a small, senior design team, working alongside the Product Leader and PMs for Diary and a development team based in the Philippines. Diary has been piloted and refined over the last 18 months and is now live with enterprise clients getting real value from it — but most of the shape is still being decided, and you'd be deciding a lot of it.

Design capture on mobile

• Take mobile features end-to-end, from briefing through to shipped UI

• Work out the interaction patterns that hold up in the field — and the ones that don't survive contact with a wet Tuesday on site

• Design around real constraints: gloved hands, outdoor visibility, shared devices, no signal

• Work with the developers so what ships is what you designed

• Help close the quality gap between our web experience and our mobile one

Design what happens to that record on web

• Own Diary's web surfaces: reviewing, reporting, and making sense of what came off site

• Make one product feel like one product…