Summary
✨ AI‑Generated
Lead frontend engineering for a client-facing platform used by businesses in a specialized services sector. You will set architecture direction across multiple teams, determine when to use independently deployable micro-frontends, influence rendering and composition strategies, and shape a design system for a live, revenue-critical environment.
Highlights
Lead frontend architecture for a revenue-critical platform, influence major technical decisions, work closely with clients, and shape a multi-team engineering environment with significant architectural ownership.
Description
Lead Frontend Engineer
Melbourne or Sydney, hybrid |Full-time | Lead level| Package: competitive, open to discuss
The company
A well-established financial services group is rebuilding a client-facing software platform used by businesses in a niche services vertical to run their day-to-day operations.
The work is being shaped closely with those clients, and the architecture calls made now will shape how the platform scales for years.
The group has a long-standing global presence and is continuing to modernise its technology, running a mix of newer cloud platforms alongside long-standing home-grown systems.
Engineers here need to be comfortable owning architecture in a live, revenue-critical estate, not just greenfield builds.
The role
You will own architecture direction for a multi-team frontend, deciding when a domain becomes an independently deployable micro-frontend versus staying in the core app.
Expect real influence over composition strategy, rendering approach and design system governance, not just ticket delivery.
Day to day you will split time between hands-on development and setting technical direction, across design, testing and peer review.
You will mentor engineers, drive AI-assisted engineering adoption, and have the autonomy to make hard technical calls and defend them.
Core competencies
Deep expertise in TypeScript and modern Angular, including standalone components and signals, (or equivalent frameworks - React is fine), used to ground architecture decisions in a live production estate.Proven ownership of frontend architecture calls: when to split into micro-frontends versus keep a monolith, and the judgement to push back on unnecessary fragmentation.Experience setting composition strategy for multi-team frontends, such as module federation versus build-time integration, weighed against operational and performance cost.Track record choosing rendering strategy (SPA, SSR, static, edge) based on real constraints like SEO, time-to-interactive and device conditions, not framework defaults.Hands-on performance work: diagnosing jank through the rendering pipeline and moving Core Web Vitals (LCP, INP, CLS) in production, validated against real user monitoring.Sound judgement on state management, including treating the URL as a first-class store for shareable, bookmarkable views.History building and governing design systems adopted across multiple squads.Demonstrated success embedding AI-assisted engineering practices to lift team productivity and delivery.Mentoring track record with evidence of measurable skill uplift across a team, not just occasional pairing.
Why it's worth a look
Genuine architecture ownership in a large, revenue-critical estate, not a greenfield toy project.Hybrid working, with flexibility built into the role.Generous paid parental leave for both primary and secondary carers.Paid volunteer leave and support for charitable giving.Additional leave for wellbeing and long service.Learning and development support, including reimbursement for professional memberships.Reimbursement for work from home equipment.
If this sounds like the kind of architecture ownership you have been looking for, get in touch for a confidential conversation.