About the role

This role is for someone a few years in who builds the front end and has a view on what should be built - working alongside a fleet of AI agents rather than pretending they don't exist. We build the software Australian organisations use to run real tenders, across construction, government, energy, infrastructure and beyond. The role is 4 days a week in our West Perth office, 1 from home. That's a real commitment and we'd rather you knew now than at offer stage. It's deliberate: the arguments about what to build happen out loud, at a desk, and sitting next to people who can answer a question in ten seconds is worth more than any amount of documentation. The office is in a lovely spot next to a small park, with windows and close to coffee and food.

We often get together for a yarn over a cup in the cafe - and we run our interviews this way too.

Why this role is unusual

Most teams are still arguing about whether to let AI write code. We already do. Our engineering runs on orchestrated Claude Code agents that plan, build, review and test against our React + TypeScript front-end and PHP backend. Typing was never the slow part, and now it isn't a part at all. What's left is harder: working out what to build, and telling whether what came back is any good. That's the job. We want someone a few years in who can hold the user's problem in their head, shape the work, and say no to a screen that isn't good enough yet. Our agentic pipeline is one-of-a-kind in Perth - we built it ourselves! We have been shipping this way for over 6 months now. We want someone who is open to this current way of working.

You should already be using an AI coding tool daily on real work, and ideally have written a spec or project rules before letting it loose. We'll teach the orchestration and more as part of this role.

Do you have front-end chops, grounded in product?

- The engineering half. You can build it properly yourself. Agents accelerate you; they don't cover for you.
- Real competence in React + TypeScript: components, state, and CSS you're not scared of. You can debug an issue from the browser all the way through the stack and point agents at the right thing. (some of it is still JavaScript - we are rapidly moving to TypeScript)
- Turning designs into components that hold up: states, edge cases, responsive, accessible.
- The front end is where you'll live, but the door to the API is open. Ours is Laravel/PHP. You'll read it from day one and chase bugs into it. How much you write or get involved in is up to you.
- Reading beats writing here. Agents produce a lot of code you didn't write, and most of it looks right. The job is telling correct from merely plausible: does this actually do what the ticket needed,



and is the test proving it or just agreeing with it? That takes experience and reading skills, and it's what the whole pipeline rests on.
- Git fundamentals: branches, sensible commits, reviewing a diff properly.
- Daily use of an AI coding tool on something real, not a tutorial.

- The product half. Not all engineers have got this. It's what we need.

- You can look at a flow and say this won't work for the person using it - then say what would work better, and why.
- You ask who the user is and what they're actually trying to finish, before you ask what the component should look like.
- You'll push back on a ticket that solves the wrong problem, with a better option in hand rather than just an objection.
- You can cut scope deliberately: what ships this week, what's a v2, what isn't worth building at all.
- You notice bad spacing, missing empty states and unhandled errors - and you won't ship a screen just because an agent produced it.
- Clear writing. Briefs, specs and PR descriptions are most of how product intent survives contact with an agent.

Not required: a CS degree, a product title, a lead title, or knowing our stack already. Bootcamp, self-taught and career-change backgrounds are all welcome. We're paying for judgement; the years are just where it usually comes from. Bring evidence that you build things, and that you had a say in what got built.

What you'd actually work on

- Customer-facing UI in a React + TypeScript app that procurement teams across several industries use to run real tenders. Front-end is where you'll spend most of your time, but a bug rarely respects the boundary, so you'll trace things into the API and help support the app when it needs it.
- A public tender portal in Next.js, built on a proper design-token system.
- Prototyping with our cofounder. We run our own prototyping agent skill that spins up high-fidelity options from a spec, then we sit down and pull them apart together before any production code gets written. You'd be in that conversation early, arguing for the version that's genuinely better for the user rather than the one that was easiest to generate.
- Writing the specs the agents run against. Scoping a feature, deciding the edge cases, and defining what "done" means - then supervising a pipeline that builds it.
- Visual and Playwright testing, so we can trust what the agents build.
- Improving the AI system itself. Skills, standards, and the captured learnings that make the next run better.





About us

Procuracon is an early-stage scale-up, which means the product is proven and the pressure now is keeping up with it. We move fast and priorities change. Some weeks are properly chaotic and others are calm, and we won't pretend otherwise in an interview. What stays constant is how we treat each other: open, honest, and always learning. Nobody here is expected to already know the answer. People say "I got that wrong" and "I have no idea what this does" out loud, including the founders, because that's the only way a team keeps up with tooling that changes month to month. If you want a fixed roadmap and a tidy queue of tickets, this isn't the place. If you want a say in what's on the roadmap, it is.

Benefits

- Real influence over the product - you will be working directly with the tech lead and cofounder, not through three layers of management. If you're right, it ships and is in front of customers quickly
- Second engineering hire - you are at ground zero with us - you will have an environment to rapidly learn and grow alongside our CTO
- Tooling most engineers won't touch for years - you'll be orchestrating multi-agent pipelines within three months, using a unique purpose-built pipeline
- A team that would rather you asked than guessed. Saying "I don't understand this yet" is the fastest thing you can do here.
- $115k–$130k + super

How the process works

- 1 · Intro screen. A short conversation about your background and how you work (with our CTO)
- 2 · Getting to know each other. An hour-long yarn with our CTO and cofounder to get to know you. It goes both ways, so ask us the hard questions.
- 3 · Technical interview + product conversation. An hour and a quarter in our codebase: reading code, debugging together, and using our AI CLI wrapper. No whiteboard, no algorithm trivia. Then we put a real screen from our app in front of you and ask what's wrong with it and what you'd do instead.
- 4 · Offer or follow-up, with honest feedback either way.

You're allowed to use AI, ask questions, and say "I don't know". That's how we work every day, so that's what we're looking at. Procuracon is committed to a diverse workforce and an equitable and inclusive workplace. We are committed to fostering a safe environment for all, including Aboriginal and Torres Strait Islander people, women, those from culturally and linguistically diverse backgrounds, the LGBTIQA+ community, and people living with disability. If you require any reasonable adjustments, we encourage you to advise us at the time of application.

Feel you aren't a match, or unsure? Get in touch anyway.

We'd be happy to have a quick chat, and we can point you in the right direction on how to level up too.

📌 AI-Native Product Engineer (West Perth)
🏢 Procuracon
📍 West Perth