The work that actually matters
Most migrations are a grind. Undocumented legacy code, competing priorities, stakeholders who want speed without understanding the cost of getting it wrong.
This one is different — not because it's easy, but because the people around you will make it worth doing.
Reapit is Australia's leading property technology platform, used by the country's top estate agencies. We've grown through acquisition, which means we're sitting on a collection of stacks with real complexity baked in. The mission for the next 12 months: migrate legacy PHP systems to a scalable, cloud-native .NET architecture — and do it in a way that doesn't compromise the platform's future for the sake of short-term velocity.
The technical decisions you make here will define this system for years. That's not marketing language. It's why we need someone who's been here before.
The team
Bright. Humble. No egos.
These are engineers who care about building the right thing long-term, not just shipping fast and hoping it holds. You'll have robust debates about the best way to solve a problem — and those debates are actually about the problem, not about who gets credit for the answer.
If you've spent time in teams where the loudest voice wins, this will feel like a different world.
What you'll own
Architectural direction across multiple squads on the PHP .NET migration
Cross-team design decisions — APIs, microservices, event-driven systems — with real authority to set the standard
Hands-on code: this is not a PowerPoint role. You'll be in the codebase
Technical risk management across a complex, multi-stack environment built through acquisition
Partnering directly with Product and Engineering leadership on roadmap trade-offs
Two questions that matter more than your CV
Name one legacy system migration or rewrite you've led, and the single biggest risk you had to manage.
Describe one specific architectural decision you drove across multiple teams, and how it was received.
Specific answers to both — you're probably who we're looking for.
On the technical side, you'll bring:
12+ years in software engineering, with expert-level .NET/C# (ASP.NET Core, Entity Framework, MySQL)
Deep experience with RESTful APIs, microservices, and event-driven architecture
Strong AWS and IaC hands-on experience (CloudFormation, CDK, Docker)
The ability to read legacy PHP well enough to understand undocumented business logic — you won't be writing it, but you need to trust what's already there
Experience with AI-assisted development tooling is a genuine plus here
What your impact and success looks like
We're looking for someone who can ramp quickly and deliver from early on.
Within 1 month:
Shipping production code independently and contributing to architectural or design discussions with credible, evidence-based input drawn from prior experience
Reading and reviewing code unsupported, with a working local environment, and raising informed technical questions that show you've already mapped the system
Owning a defined area of the architecture or codebase end-to-end, with minimal need for onboarding support, and delivering measurable value against the engagement's priorities
Within 3 months:
Strong command of the core architecture and technology stack, identifying and flagging architectural risks or technical debt before they become blockers
Leading cross-team design discussions and influencing technical decisions beyond your immediate squad
Independently proposing and driving improvements to architecture, tooling, or team processes, with clear rationale tied to business or delivery outcomes
Holding engineering standards consistently across the teams you work with, raising the bar on code quality, testing, and review practices through example and constructive challenge
Partnering directly with Product on roadmap trade-offs, providing technical input that shapes scope and sequencing decisions
Within 6 months:
Recognised as the technical owner for a defined domain, product line, or initiative, with clear accountability for its architecture and delivery quality
Making and owning high-impact technical decisions on complex, multi-team initiatives, balancing trade-offs across performance, cost, and delivery timelines
A trusted technical voice in planning and design conversations, sought out by Product and Engineering leadership for input on roadmap and architecture trade-offs
Measurably improved engineering effectiveness in your domain — through reduced technical debt, improved reliability, or faster delivery cycles — with evidence you can point to
Mentoring engineers across teams and actively raising the technical bar through example, review, and design guidance
