Erik Grijzen
Principal Software Engineer at New Relic
In this episode of Señors @ Scale, host Neciu Dan chats with Erik Grijzen — Principal Software Engineer at New Relic — about building one of the first large-scale micro-frontend architectures, the rise of observability, and what technical leadership looks like across dozens of teams.
Main Takeaways from my conversation with Erik:
🏗 Building micro-frontends before they had a name.
When New Relic unified over twenty SPAs into a single extensible platform, Erik led the architectural effort that enabled every team to deploy independently while maintaining shared consistency and performance.
⚙️ Runtime composition at scale.
From CLI tooling to runtime loading from CDNs, Erik explains how teams can push a micro-frontend to production within a day — and why polyrepo setups made extensibility possible.
🔍 Observability as a business layer.
Observability isn’t just about logs and metrics anymore. Erik describes how New Relic connects system telemetry with user behavior and business impact, making reliability a shared company goal, not just a developer metric.
🧠 Influence over authority.
As a principal engineer, Erik doesn’t manage people directly — he leads by influence. He shares how to align dozens of teams through shared vision, mentorship, and documented decision-making.
🧩 RFCs and decision docs make teams better.
Writing change documents improves ideas before they’re even reviewed. Erik shares how structured writing and technical documentation shape better solutions and build clarity across distributed teams.
🧰 POCs before roadmaps.
Instead of planning large initiatives upfront, Erik recommends writing documentation or running proof-of-concepts first — “If it’s hard to explain, it’s probably not right.”
💬 Observability for micro-frontends.
Since no tools existed when they began, New Relic built an internal SDK to give each micro-frontend its own scoped telemetry and error context — something now becoming an industry need.
🌿 Balancing scale and life.
Erik shares practical ways to manage stress: sports, routines, and structured shutdown rituals that separate deep work from personal time.
📚 Recommended Reads:
- A Philosophy of Software Design by John Ousterhout
- 4,000 Weeks by Oliver Burkeman
🎬 Also in this episode:
- How a trillion requests per minute backend powers New Relic’s frontend architecture
- The hidden trade-offs of iframes and module federation
- Why teams organized by domain scale better than feature-based ones
- How incident rollbacks and version pinning simplify on-call
- The mindset shift from shipping code to shaping culture
Episode Length: 1 hour of deep technical insights and leadership lessons for anyone scaling frontend platforms or engineering teams.
💡 More Recent Takeaways
Señors @ Scale host Neciu Dan sits down with Kadi Kraman, software developer at Expo working on the tools that make React Native development as smooth as possible. Kadi's path started with C++ in a university maths degree, took her through Angular 1, scientific programming for pharmaceutical and defense companies, five and a half years at Formidable, and finally to Expo itself. From the limitations of early React Native to development builds, EAS workflows, fingerprint-based repacks, and the right way to think about over-the-air updates, this is the React Native conversation most web developers never get.
Señors @ Scale host Neciu Dan sits down with Nico Martin — open source ML engineer at Hugging Face working on Transformers.js, and Google Developer Expert in AI and web technology — to go deep on running machine learning models directly in the browser. Nico breaks down architectures vs. weights, quantization, tokenizers, ONNX, WebGPU, and why on-device AI is the right answer for a huge class of problems. He also shares the road from ski instructor and self-taught web developer to landing what he calls his dream job at Hugging Face.
Señors @ Scale host Neciu Dan sits down with Giorgio Polvara, Staff Engineer at Perk (formerly TravelPerk), who joined when the company was 15 people in two flats with a hole knocked through the wall and helped build the frontend foundations that still hold up at unicorn scale. Giorgio covers the multi-year migration from a monolithic frontend to vertical micro-frontends, why their first attempt with single-spa didn't work, how they pulled off a full rebrand behind feature flags without leaking, and the staff engineer mindset of treating every feature as a system improvement.
Señors @ Scale host Neciu Dan sits down with Zack Chapple, CEO and co-founder of Zephyr Cloud, and Nestor, the platform engineer building it, to go deep on module federation, microfrontends, and what it actually takes to go from code to global scale in seconds. They unpack why module federation is Docker for the frontend, how Zephyr composes applications at the edge in 80 milliseconds, and why the real unlock for enterprise teams isn't deployment — it's composition.
📻 Never Miss New Takeaways
Get notified when new episodes drop. Join our community of senior developers learning from real scaling stories.
💬 Share These Takeaways
Want More Insights Like This?
Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.