Lead Frontend Engineer

Macquarie Group; Indonesia; On-site; IDR 500,000,000 - 800,000,000; Full time

Job summary

Macquarie Group in Indonesia seeks a senior frontend architect to own architecture direction for the frontend estate. You will decide when a domain should be carved into a micro-frontend and defend against fragmentation while maintaining core application integrity.

You will shape composition strategy across multi-team frontends, weigh SSR/CSR/edge rendering, optimize Core Web Vitals in production, and mentor engineers to lift skills and delivery.

Qualifications

• Experience leading frontend architecture decisions for large, multi-team systems.
• Proven ability to implement accessible, high-performance UIs across platforms.
• Experience mentoring engineers and driving AI-assisted development practices.

Responsibilities

• Define and govern architecture for the frontend estate, including micro-frontend strategy.
• Balance SSR/CSR/edge rendering and optimize Core Web Vitals in production.
• Lead and mentor squads to improve delivery quality and pace.

Skills

Frontend architecture

Design systems

Accessibility

Mentoring

AI in engineering

Performance optimization

Cross-team leadership

Tools

TypeScript

Angular

Module Federation

Webpack / build tooling

Job description

• You own architecture direction for the frontend estate: deciding when a domain should be carved out as an independently deployable unit (a micro-frontend) versus kept inside the core application and defending that call against both premature fragmentation and unchecked monolith growth.
• You set technical direction on composition strategy for a multi-team frontend (build-time integration versus runtime composition such as module federation), weighing deployment independence against operational, versioning and performance cost, and you can make the case against a micro-frontend split when the cost outweighs the benefit.
• You weigh SPA, server-side rendering, static generation and edge rendering against each other for a given page or flow, choosing based on real constraints (SEO, time-to-interactive, data freshness, device and network conditions) rather than defaulting to whatever the framework does out of the box.
• You can trace jank through the actual rendering pipeline (parse, style, layout, paint, composite), know which changes trigger a full reflow versus a cheap compositor update, and keep the main thread free for user input using scheduling techniques or web workers.
• You move Core Web Vitals (LCP, INP, CLS) in production, not just report on them, confirming every gain against real user monitoring rather than lab scores alone.
• Comprehensive design system experience, with a history of building and governing design systems used across multiple squads.
• Demonstrated success driving AI-assisted engineering as standard practice — identifying opportunities to improve developer productivity, quality, and delivery efficiency, and leading that adoption.
• Experience mentoring and upskilling engineers, with evidence of the outcome (skills lifted, delivery improved for a defined group) rather than occasional pairing sessions.
• You champion accessibility as a non-negotiable engineering standard and own frontend-specific risk more broadly: client-side data exposure, third-party script governance, and regulatory or security obligations, ensuring these are upheld across a team's output, not just your own code.
• You bring expertise in TypeScript and modern Angular (or similar frameworks) — including patterns like standalone components and signals — to ground these decisions in our actual frontend estate.
• You own architecture direction for the frontend estate: deciding when a domain should be carved out as an independently deployable unit (a micro-frontend) versus kept inside the core application and defending that call against both premature fragmentation and unchecked monolith growth.
• You set technical direction on composition strategy for a multi-team frontend (build-time integration versus runtime composition such as module federation), weighing deployment independence against operational, versioning and performance cost, and you can make the case against a micro-frontend split when the cost outweighs the benefit.
• You weigh SPA, server-side rendering, static generation and edge rendering against each other for a given page or flow, choosing based on real constraints (SEO, time-to-interactive, data freshness, device and network conditions) rather than defaulting to whatever the framework does out of the box.
• You can trace jank through the actual rendering pipeline (parse, style, layout, paint, composite), know which changes trigger a full reflow versus a cheap compositor update, and keep the main thread free for user input using scheduling techniques or web workers.
• You move Core Web Vitals (LCP, INP, CLS) in production, not just report on them, confirming every gain against real user monitoring rather than lab scores alone.
• Comprehensive design system experience, with a history of building and governing design systems used across multiple squads.
• Demonstrated success driving AI-assisted engineering as standard practice — identifying opportunities to improve developer productivity, quality, and delivery efficiency, and leading that adoption.
• Experience mentoring and upskilling engineers, with evidence of the outcome (skills lifted, delivery improved for a defined group) rather than occasional pairing sessions.
• You champion accessibility as a non-negotiable engineering standard and own frontend-specific risk more broadly: client-side data exposure, third-party script governance, and regulatory or security obligations, ensuring these are upheld across a team's output, not just your own code.
• You bring expertise in TypeScript and modern Angular (or similar frameworks) — including patterns like standalone components and signals — to ground these decisions in our actual frontend estate.