Angular Tech Lead & Systems Architect · @BMW TechWorks Romania
Eight years of front-end work, the last of them leading Angular at BMW TechWorks Romania and setting the standards a community of ~100 Angular engineers builds against. I care about the unglamorous part: architecture and test coverage that hold up years after the demo — plus what changes when agents start writing and running the code with you.
I'm an Angular enthusiast focused on building robust, scalable and maintainable front-end applications. Today that's as Angular Tech Lead & Systems Architect at BMW TechWorks Romania, where I own the Angular technical standards and sit on the board of our JavaScript community — around 100 Angular engineers.
The path here: junior front-end at ArtSoft Consult in 2018, Angular at Nagarro through 2024, then BMW — first as a senior developer, now leading. Signals, RxJS, TypeScript, Cypress and Playwright are the tools I reach for most, and I'm spending the rest of my curiosity on agentic AI and what it does to how we build.
The other half of the job is people: I run our mentorship programme, currently a seven-month track with twelve students. No corporate voice, no vendor pitch — just what I built, what broke, and what I'd do differently.
Signals promise surgical, DOM-level updates instead of tree-wide change detection. Angular's dynamic dependency tracking has a sharp edge: reactive context leaks inside effects.
The prompt engineering gets all the attention. The actual hard problem in agentic AI products is the interface between a nondeterministic backend and a deterministic UI.
Wrapping three internal Angular libraries as MCP servers turned out to matter more than the AI tooling itself. Here's what changed on the team.
A breakdown of the architecture behind a 4-agent workflow running inside an Angular app — orchestration, state, and the failure modes nobody warns you about.
An Angular review, mentoring, a second opinion on an agentic system, or a conference talk — send a message and I'll reply from my own inbox.