Angel Paredes
Engineering Manager at Datadog
In this episode of Señors @ Scale, host Neciu Dan sits down with Angel Paredes — Engineering Manager at Datadog, formerly Staff at Glovo and Tech Lead at PayPal — to explore test infra, AI's impact on interviewing, and how to lead without losing your technical edge.
Main Takeaways from my conversation with Angel:
🧪 Test infra will haunt you.
Angel promised himself he’d never build another test tooling platform after leading one at Glovo. He now leads Datadog’s test optimization team—handling framework injection, flakiness detection, and runtime rewrites.
📦 His monorepo takes 30 minutes to clone.
Yes, really. But they’ve structured it as a multi-package setup with strict boundaries, making TypeScript, builds, and linking tolerable—and even fast. “Best DX I’ve ever had.”
💥 Promotions felt like a zero-sum game.
Climbing to staff engineer meant stepping on other people’s scope. Becoming a manager, in contrast, gave him impact without stepping over others. “As a manager, you get a team for free.”
🧠 Senior engineers don’t need handholding, they need focus.
Most of his time goes to aligning the plan and handing out the right challenge. Especially for senior folks who’ve done the same thing for years.
🧠 He still codes—every week.
Angel writes frontend and backend code regularly, even as a manager. “I’m faster in frontend, so I ship there to unblock the team.”
🤖 AI is already changing interviews—and people are cheating.
From deepfakes to screen overlays to ChatGPT whispering the answers, Angel’s seen it all. But if a dev needs ChatGPT at work too? “That’s fine. Just don’t fake your identity.”
🔍 Interviewing is broken—and AI is forcing a reset.
Angel argues for code review-style interviews, real-time debugging sessions, and culture rounds that focus less on similarity and more on team fit. “Most rubrics are just recipes.”
💬 They inject into Jest… without plugins.
Datadog’s team reverse-engineers testing frameworks at the module level, bypassing plugins and altering runtime behaviors. It’s surgical, not superficial.
🧑🏫 Conference speaking changed how he shows up in meetings.
He was terrified of speaking on stage. Now he credits public talks with helping him communicate clearly under pressure, lead better, and fight impostor syndrome.
📚 Book recs:
- Engineering Management for the Rest of Us by Sarah Drasner
- Managing Humans by Michael Lopp
- The Burnout Society by Byung-Chul Han
- The Artist’s Way by Julia Cameron
- Plus: Terry Pratchett’s Guards, Guards! for a crash course in managing a team of weirdos
📖 We also talk about fantasy, reading 60+ Forgotten Realms books, and why Journey Before Destination is the right motto for scaling careers.
Episode Length: 1hour and 1 minute of raw insights, technical nerdery, and real management talk
💡 More Recent Takeaways
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.
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.
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.
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
Want More Insights Like This?
Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.