One of Australia's leading digital marketplace businesses is transforming its data intelligence SaaS tool.
The platform had a deep customer base prior to being acquired by the group but was never fully integrated into the wider group's technology ecosystem. Now that's changing.
A modernisation programme is underway: legacy Java and Tapestry giving way to React, TypeScript and Node, with the product increasingly plugging into shared services elsewhere in the business instead of duplicating them.
What You'd Own
- Two squads split across Sydney and Melbourne: one holding down the existing platform and pushing the migration forward, the other building the future product
- The technical judgement calls behind the modernisation: what moves, what's rebuilt, what's retired
- Enough hands‑on involvement to actually get underneath the legacy Java codebase, not just read the architecture diagrams
- Influence over the React/TypeScript/Node future state, including where AI‑enabled workflows fit down the line
- Working relationships across other engineering teams, since the future platform leans on services built outside your own squads
Experience that this role calls for
- Java or JVM background, even if it's not what you're writing today, followed by a move into React, TypeScript and Node
- Personally led a legacy‑to‑modern platform transformation, not just observed one from the delivery side
- You're a hands‑on player‑coach type EM who is still close enough to the code and architecture to challenge a design decision, review a pull request, or debug something gnarly, without needing to be the team's top committer
- Solid .NET backgrounds also welcome, provided you can read your way into an unfamiliar Java platform while credibly leading the team toward the future state
- Comfortable running two squads and managing the handoffs between a maintenance‑and‑migration team and a build‑the‑future team
- A real point of view on what should be migrated versus rebuilt versus retired, and the ability to defend it
- Modernised a product that was acquired or historically under‑invested in
- Shared API/platform integration work across multiple engineering teams
- Strangler‑pattern or incremental migration experience specifically
#J-18808-Ljbffr
📌 Engineering Manager (City of Sydney)
🏢 Latitude IT
📍 City of Sydney
Reply to this offer
Impress this employer describing Your skills and abilities, fill out the form below and leave Your personal touch in the presentation letter.