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 Craig Abbott, Principal Accessibility Specialist at TetraLogical and the former Head of Accessibility at the UK's Department for Work and Pensions, one of the largest government departments in the country, where he built a dedicated accessibility practice from nothing and open sourced the DWP Accessibility Manual. Craig has over 15 years in user centred design and has led accessibility work across the public sector and at Elastic. From what sustainable accessibility actually means and why third party audits alone don't get you there, to the three C's of compliance, culture and capability, to running screen readers in VMs without expensive licences, to accessibility acceptance tests in CI with Playwright, Cucumber and Guidepup, to why compliance does not mean usable, this is the accessibility conversation for teams who want it to survive the person who cares about it.
Señors @ Scale host Neciu Dan sits down with Carmen Huidobro, CTO at Incredible Bee in Vienna, where she builds products and helps teams figure out what should be automated and what should stay in the hands of users. Carmen has spent 17 years in tech, almost all of it freelancing, working across Objective-C, Ruby on Rails, the web, mobile, hardware, and even ABAP inside an SAP consultancy, plus five years in developer relations and developer education. Her argument is that the generalist versus specialist debate misses the point: the durable skill is being an expert at adapting. From adding a local Mistral model to a twenty-year-old macOS app without betraying the people who use it, to the refugee hackathon project the City of Vienna still runs a decade later, to why she won't take money from junior developers, this is a conversation about the skills that survive the shift.
Señors @ Scale host Neciu Dan sits down with Marko Gaćeša, Head of Product at Semaphore, the agent-native CI/CD platform, and the first product guest on the show. Marko is a serial entrepreneur whose career spans developer tools, IoT, industrial automation and enterprise SaaS, including founding Dry Tools and serving as Chief Product Officer at Alchemy Cloud, with earlier work in domains like medical equipment where quality is non-negotiable. From why testing rather than coding is now the bottleneck, to what agent-native CI/CD actually means when developers live inside their coding agent, to how SemAI attacks flaky tests and automates migration off GitHub Actions, to pricing a platform where a minute of CI is not the same minute everywhere, this is the product side of developer tooling from someone shipping it.
Señors @ Scale host Neciu Dan sits down with Maxim Salnikov, AI Dev Tools Solution Engineer at Microsoft, where he leads AI native development enablement for over 100 enterprise customers of Microsoft and GitHub in Norway. Maxim has been building for the web since the late 90s and spends his days inside real enterprise dev teams across finance, energy, agriculture, and pure software companies, watching AI adoption succeed and fail. From why adoption is a change management problem rather than a technology one, to the anatomy of an AI harness and the external layer successful companies build on top of it, to the context engineer and agent ops roles now appearing in team topologies, to managing agent skills as versioned dependencies instead of letting them pollute the repo, this is the enterprise AI adoption conversation from someone who sees a hundred versions of it.
📻 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.