The problem worth solving
Reapit is Australia's leading property technology platform. We're in the middle of a significant CRM modernisation — migrating a legacy front-end to a new React application, across multiple squads, on a real deadline.
The hard part isn't the React. It's everything that surrounds it: how the new app coexists with the legacy CRM during the transition, how you manage shared auth and session state across systems, how you set front-end standards that multiple teams can actually follow, and how you make the right architectural calls when the documentation doesn't give you the full picture.
The decisions made over the next 12 months will shape this platform for years. We need someone who has navigated exactly this kind of complexity before — and can be trusted to get the hard calls right the first time.
The team
Bright, humble, no egos.
These are engineers who debate the right way to solve a problem — not who gets credit for the answer. Long-term thinking wins over short-term shortcuts. If you've worked in teams where the loudest voice sets the architecture, this will feel different.
What you'll own
The front-end architecture for the CRM Modernisation effort — end to end, across squads
How the new React app coexists with and migrates away from the legacy CRM (iframe embedding, shared session/auth behaviour, migration sequencing)
Component architecture, state management, and testing standards that other engineers follow
API contract definition and integration standards with backend teams (REST and/or GraphQL)
The most complex, ambiguous front-end problems — the ones nobody has fully untangled yet
This is a hands-on role. You'll be in the codebase, in the design discussions, and in the room when trade-offs get made.
Two questions that matter more than your CV
Describe one front-end architecture decision you've made that had to account for a legacy system running alongside the new one, and the hardest part of it.
Name one instance where you influenced front-end technical direction across teams, and the outcome.
Specific answers to both — you're likely our person.
Technically, you'll bring:
12+ years in front-end development, with expert-level React and TypeScript in production at scale
Deep experience with state management (Redux, Zustand, React Query) and component design patterns
Strong hands-on experience with CI/CD, AWS, and front-end DevOps practices
Comfort defining API contracts and making backend changes where needed to unblock delivery
Advanced understanding of accessibility (WCAG) and web performance at scale
Confident use of AI-assisted development tooling to accelerate your own output and your team's
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
Owning a defined area of the front-end architecture end-to-end, with minimal need for onboarding support, and delivering measurable value against the engagement's priorities
Reading and reviewing code unsupported, with a working local environment, and raising informed technical questions that show you've already mapped the front-end and how it interacts with the legacy CRM
Within 3 months:
Strong command of the front-end architecture and how it coexists with the legacy CRM, identifying and flagging architectural or migration risks before they become blockers
Leading cross-squad design discussions and influencing front-end technical decisions beyond your immediate squad
Independently proposing and driving improvements to front-end architecture, tooling, or process, with clear rationale tied to business or delivery outcomes
Holding engineering standards consistently across the squads you work with, raising the bar on code quality, testing, and review practices through example and constructive challenge
Partnering directly with Product and Design on roadmap trade-offs, providing technical input that shapes scope and sequencing decisions
Within 6 months:
Recognised as the technical owner for the front-end architecture of the CRM Modernisation effort, with clear accountability for its quality and delivery
Making and owning high-impact technical decisions on complex, multi-squad initiatives, balancing trade-offs across performance, maintainability, 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 front-end engineering effectiveness across the CRM Modernisation effort — through reduced technical debt, improved reliability, or faster delivery cycles — with evidence you can point to
Mentoring engineers across squads and actively raising the technical bar through example, review, and design guidance — not just within your own squad
Ensuring a smooth handover of your work — with up-to-date documentation and knowledge sharing so the team can build confidently on what you've delivered after your contract ends
