Skip to content
⚡ LIVE From Lizard to Wizard · Wednesday, August 5 · LIMITED SEATS Save my seat →
Episode 13 1 hour

Observability at Scale – With Erik Grijzen

Key Takeaways from our conversation with Erik Grijzen

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.

🏆 SOLD OUT IN SINGAPORE · ATHENS · LONDON

From Lizard to Wizard

4-hour remote system design intensive.
Chat apps, microfrontends, BFF, SDUI, event-driven, observability.

€299 4-HOUR INTENSIVE
Save your seat →

Spots are vanishing. Don't be the one who waited.

💡 More Recent Takeaways

Monorepos at Scale with Santosh Yadav
Episode 40

Señors @ Scale host Neciu Dan sits down with Santosh Yadav, principal developer advocate at CodeRabbit and one of only around 80 GitHub Stars in the world. Santosh started hating C in 2004, fell for C# by 2008, and turned a year of open source contributions to Angular and NgRx into a stack of community titles — Google Developer Expert, GitHub Star, Nx champion, and Microsoft MVP. As a staff engineer at Celonis he led the move of 20-plus apps to module federation and drove Nx adoption across 30-plus teams when the product grew from four apps to thirty. From the year-long incremental migration off a single deployable unit, to why polyrepos can't give AI tools the context they need, to how Nx's affected graph and build caching tame a 20-million-line monorepo, to running code review for free for open source at CodeRabbit, this is the monorepo conversation grounded in someone who actually shipped one at scale.

Routing at Scale with Nicolas Beaussart-Hatchuel
Episode 39

Señors @ Scale host Dan Neciu sits down with Nicolas Beaussart-Hatchuel, staff engineer at Payfit and one of the maintainers of TanStack Router. Nicolas's path started with C macros to auto-generate his student paper headers and frontend learned by building phishing login pages for practice, took him through an iframe-based AngularJS-to-Angular 2 micro frontend migration at a web radio platform, into open source contributions across NX, ESLint, Vite and Hasura, and finally to maintaining one of the most ambitious routers in the React ecosystem. From why TanStack Router exists, to migrating Payfit's 300-route, 1.5-million-line codebase off React Router v5 using the strangler pattern, to collapsing 25 polyrepos and five different micro frontend strategies into a single modular monolith, this is the routing conversation most engineers never get.

Redux at Scale with Mark Erikson
Episode 38

Señors @ Scale host Neciu Dan sits down with Mark Erikson, maintainer of Redux and senior front-end engineer at Replay.io, where he works on a time-traveling debugger. Mark's path started with a 286 he got at eight years old, ran through a computer science degree, four years teaching English in China, embedded software at Northrop Grumman emulating legacy CPUs in old aircraft, and a chain of projects — GWT, jQuery, Backbone — that led him to React and Redux. From the @deprecated backlash that had people insulting him on the internet, to why the Redux core hasn't meaningfully changed since 2016, to what RTK Query actually solves, the underused listener middleware, building source maps into React's own build pipeline, and how Replay's recordings now hand debugging over to AI agents — this is the Redux conversation grounded in two decades of shipping software.

TanStack Query at Scale with Dominik Dorfmeister
Episode 37

Señors @ Scale host Dan Neciu sits down with Dominik Dorfmeister — better known as TkDodo — the maintainer of TanStack Query and a software engineer at Sentry. Dominik's path started at a technical high school in Vienna, ran through JVM backend work in Java and Scala, and turned to frontend around the introduction of TypeScript. During the pandemic lockdowns in Austria he started answering questions in the TanStack Discord, got addicted to the instant gratification of helping people, and slowly turned that into a blog, a first code contribution six to eight months later, and eventually maintainership of TanStack Query. From tracked queries and the chaotic version-three-to-four rename, to the version-five mistake he still dreads, to ripping 28,000 lines of dead code out of Sentry with Knip and building Sentry's new design system, this is the open source maintenance conversation most developers never get to hear.

📻 Never Miss New Takeaways

Get notified when new episodes drop. Join our community of senior developers learning from real scaling stories.

💬 Share These Takeaways

Share:

Want More Insights Like This?

Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.