Office | Stapylton, QLD | 3 days office, 2 days WFH

The Prospect:

Most delivery roles ask you to run other people's decisions. In this one, the CTO is handing you the keys to the castle.

You'll join one of Australia's most successful manufacturing businesses, engineering physical, mechanical products that hold real structures and machinery together, built here and exported worldwide.

The team is building its first cloud-native product, a customer-facing platform on React, Postgres and AWS ECS, with a small team already writing code against it.

The CTO has been running it personally on top of two other engineering functions and needs it off his desk, handed to someone who can run it properly rather than leave it as an unofficial second job.

What we need:

- This is a hands-on, technical player-coach role for someone who has actually built production software, not a career project manager who has only managed other people's builds, and not a deep technical specialist who has never run a team or owned a delivery timeline.
- The right person has done both, in that order, and still speaks fluent engineering even though their day is now mostly spent leading rather than building.

Here's what that ownership covers:

- Reporting to the CTO, you'll take over the architecture calls, sprint planning and day-to-day technical guidance for a team of three developers and two technical analysts, with a second team being onboarded to the same three-week sprint cadence
- Own how the architecture and migration strategy evolve, backed by business case and cost analysis, not rubber-stamped, yours to shape
- Steer the strangler pattern migration off the legacy platform, replacing it one slice at a time rather than a rip-and-replace
- Spend most of your time on requirements decomposition, sprint planning and guiding mid-tier and junior developers through delivery,



expect roughly a fifth of your time hands-on
- Work alongside a dedicated security specialist already on the team. You're not expected to own security end to end, but you need to be someone they can work with without a translation problem

What You Bring:

- A career trajectory that's gone from hands-on engineering or security-focused first, then pivoted into project or delivery management, not someone who has managed delivery from a distance without ever building production software
- Production experience with React on the front end and Node.js/TypeScript on the back end, working against a PostgreSQL database
- Real world AWS experience, ideally with ECS specifically, running containerised services rather than a handful of Lambda functions
- Comfort working inside a microservices architecture: you understand how a change to one interface ripples through everything downstream of it, and you plan for that rather than find out the hard way
- Experience migrating a legacy or on-premise application to the cloud, ideally using a strangler pattern rather than a rip-and-replace approach
- You've been in the room for a real production outage. You know what the first twenty minutes of an incident looks like and what good recovery discipline actually involves, not just what the postmortem template says
- Strong requirements decomposition and sprint delivery skills: you can take a rough brief and turn it into something a team can actually build
- Strong confidence coaching and mentoring less experienced developers, rather than just directing them
- Azure or GCP experience is fine in place of AWS, if the underlying cloud fundamentals are strong
- Prior exposure to a legacy monolith-to-microservices transition at a similar scale
- Background in a manufacturing, industrial or similarly complex domain-driven environment

#J-18808-Ljbffr

📌 Technical Delivery Manager (City of Gold Coast)
🏢 Latitude IT
📍 City of Gold Coast