Stefano Magni
Senior Front-End Engineer & Tech Lead at Preply
Señors @ Scale host Neciu Dan sits down with Stefano Magni, Senior Front-End Engineer and Tech Lead at Preply, to unpack what it takes to build and measure a design system for a global learning platform. From managing technical debt and accessibility to driving a culture of public work and data-driven engineering, Stefano shares lessons from 15+ years in frontend development.
🎧 New Señors @ Scale Episode
This week, I spoke with Stefano Magni, Senior Front-End Engineer & Tech Lead at Preply, about what it really takes to build and scale a design system that serves millions of learners worldwide.
We covered everything from rebrands and metrics to culture and collaboration — and why working in public can transform your career.
⚙️ Main Takeaways
1. Your career = skills + reputation + network.
Stefano’s core belief: if you ignore any of these three, you limit your growth. Working in public builds the reputation and network part most engineers neglect.
2. Design System Visual Coverage.
Preply measures the real impact of its design system by tracking what percentage of the UI comes from system components — a data-driven approach to adoption.
3. Building fast meant technical debt — intentionally.
During Preply’s massive rebrand, the team shipped quickly with Radix UI and accepted debt consciously to meet deadlines, planning future cleanups in advance.
4. Pragmatism over perfection.
Pixel-perfect is nice, but at scale, pragmatism wins. The key is knowing what matters and what can wait without compromising experience.
5. Managing large codebases without tests.
At WorkWave, Stefano learned how to maintain 250k+ LOC apps safely using strict TypeScript patterns and consistency — not tests — as the safety net.
6. Metrics drive everything at Preply.
Every initiative — from UI improvements to accessibility — ties back to measurable outcomes. “You don’t just build something; you build it to move a metric.”
7. Accessibility through measurement.
Accessibility violations are tracked directly from users’ devices, creating accountability and visibility company-wide.
8. Engineering Excellence is now cultural.
Preply evolved from a “hackers” culture to one of Keep Perfecting — prioritizing quality, accessibility, and speed without sacrificing long-term scalability.
9. Duplication beats bad abstraction.
Stefano argues that a few well-understood duplications are better than the wrong abstraction. Clean code isn’t always DRY — it’s maintainable.
10. Public work accelerates careers.
From Stack Overflow to conference talks, Stefano shows how sharing your process publicly compounds into reputation, opportunities, and impact.
🧠 What I Learned
- Metrics give direction — not judgment.
- Accessibility and performance should be tracked like business KPIs.
- Teaching is the best way to master your craft.
- Duplication done right can be an act of clarity.
- Public work is career leverage disguised as learning.
💬 Favorite Quotes
“Your career depends on three things — your skills, your reputation, your network.”
“Design is an approach, not a role.”
“We intentionally created technical debt — because we had to deliver.”
“Duplication isn’t the enemy. Wrong abstractions are.”
“It’s not about what you know or who you know. It’s about who knows you and what they know you can do.”
🎯 Also in this Episode
- How Preply rebranded 70% of its product in one cycle
- Why frontend engineers need to think socially
- The hidden value of data-driven experimentation
- Building for accessibility at scale
- Engineering culture shifts — from hacking to perfecting
🎧 Listen Now
🎧 Spotify
📺 YouTube
🍏 Apple Podcasts
Episode Length: 1h 4m on design systems, engineering culture, and public work at scale.
If you care about design systems, accessibility, or how engineering culture evolves with scale — you’ll enjoy this one.
Happy scaling,
Dan
💡 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.