Internal Angular platform & developer experience

01 /Context

Across an enterprise consultancy, every new Angular project rebuilt the same foundation from scratch: components, project setup, design handoff, documentation. That meant days lost before any real work started and a different quality bar each time. I built the shared Angular platform and the developer-experience tooling that standardised it across every project.

02 /My role

I designed and built Bravent's shared Angular platform and the developer-experience tooling around it, and drove its adoption across teams. I owned the architecture, the standards, and the boundary between what teams reuse and what they customise per client.

03 /Technical highlights

• Angular component library adopted across 10+ client projects, cutting new-project startup from days (3–5) to hours (1–2).
• Design system built in Figma with code components generated automatically via AI tooling — adopted by every designer in the company, ~60% faster to build reusable components.
• Angular schematics / scaffolding that wires conventions automatically — an engineer new to Angular shipped a production project in one week.
• Unified lint and formatting rules plus an Obsidian-based documentation-generation system, so the team documents improvements as part of the workflow.

04 /Outcome

The Angular org stopped starting from zero. One shared base now powers Angular delivery across the consultancy and onboarding is measured in days, not weeks — frontend at Bravent became a reusable platform capability, with the standards enforced by tooling, not by review.