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 Carson Gross, creator of HTMX, principal at Big Sky Software, and computer science professor at Montana State University. Carson has been programming for more than 30 years, from HyperCard on a family Mac to Excel macros for an industrial engineering firm, a JVM language called Gosu, a Rails startup, and the 2012 library Intercooler.js that he rewrote without jQuery during COVID and released as HTMX. His argument is that the web was built as a hypermedia system, that links and forms are control logic living inside the document, and that most of what we call REST today fails the one constraint Roy Fielding cared about. He also covers which apps HTMX is wrong for, what changed in HTMX 4 and why 3 was skipped, and why his students now sit pencil and paper exams. It is a conversation about using the browser as the hypermedia client it was built to be.
Señors @ Scale host Neciu Dan sits down with Ryan Townsend, Principal Product Manager for Performance at Cloudflare, where he owns real user monitoring and the wider performance measurement remit. Ryan has over 20 years in web technology and a decade as a CTO: he co-founded Shift Commerce, the first enterprise scale headless SaaS, and was CTO of Matalan Direct after the business he built came second in Shopify's Build a Business competition with only three months of trading. We cover why the 'Rails doesn't scale' story was always a myth, the resume driven development he kept finding as a fractional CTO, the personalization script that claimed zero performance impact and cost seconds at P90, and how Shift ran over 99% cache hit ratios by splitting the anonymous page from the basket.
Señors @ Scale host Neciu Dan sits down with Szymon Chudy, Software Engineer at Netflix on the Hawkins team, which builds the design system behind thousands of internal applications used to produce the shows you watch. Before Netflix, Szymon spent two and a half years at Lokalise, growing from senior to staff frontend engineer and leading frontend direction across teams, and before that he toured Poland as a reggae guitarist while freelancing as a web developer in the off season. From why the source of truth for a design system lives in code, to Hawkins Consumer versus Hawkins Professional, to the UI paved road that changes what freedom and responsibility mean at Netflix, to measuring the team on adoption rate and shipping codemods and agent skills for every breaking change, to what being an informed captain who farms for dissent means in practice, this is the design system conversation for anyone maintaining a platform other engineers have to choose to use.
Señors @ Scale host Neciu Dan sits down with Vilva Athiban, Lead AI Engineer at Omio, one of Europe's leading travel platforms, where he architects and ships agentic AI systems in production. Vilva designed and delivered Omio AI, along with the MCP integrations that connect AI agents to the company's systems. He never set out to switch from JavaScript to AI: in June 2024 Omio picked two people to start an AI team reporting to the CEO and CTO, and he learned on the job, from his first API call to an LLM up to a consumer-facing agent whose backend runs on nothing but MCP. From why a bigger model with medium thinking came out cheaper than the mini, to capping tool calls because LLMs are built for token maxing, to the whale hunting request that showed his team guardrails are subjective, this is a conversation about what production agentic systems look like once the tutorials run out.
📻 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.