Bruno Paulino
Tech Lead at N26
Señors @ Scale host Neciu Dan sits down with Bruno Paulino, Tech Lead at N26, to explore what reliability really means in FinTech. From server-driven UIs and CI/CD pipelines to AI-assisted customer support and strict compliance, Bruno shares how N26 balances speed, safety, and developer experience to keep millions of users online.
🎧 New Señors @ Scale Episode
This week, I sat down with Bruno Paulino, Tech Lead at N26, to talk about what reliability at scale really means when every deploy touches millions of bank customers.
It’s a conversation about trust, resilience, and trade-offs — from building CI/CD pipelines that deploy in minutes, to server-driven UIs that let N26 roll out features instantly, to scaling customer support using LLMs and Retrieval-Augmented Generation.
⚙️ Main Takeaways
1. Reliability isn’t just uptime — it’s trust.
When your app handles real money, every minute of downtime has a financial cost. N26 designs reliability as a core product feature, not an afterthought.
2. CI/CD transformed how fast teams ship.
Pipeline time dropped from one hour to five minutes. With GitHub Actions, Argo CD, and Kubernetes, deployments are now predictable, testable, and safer.
3. Server-driven UI changes the game.
The backend defines what users see — from banners to buttons — across mobile, web, and desktop. Features can roll out in five minutes instead of waiting for app store approvals.
4. AI is reshaping customer support.
Bruno’s team built an AI Assistant using LLMs and RAG pipelines to make support faster, more contextual, and scalable — all while keeping reliability and compliance intact.
5. Safe experimentation with Statsig.
Every major feature at N26 goes through type-safe A/B testing using Statsig. Teams can ship to 5% of users, observe performance, and ramp up safely.
6. Reliability vs. Speed: the trade-off.
At N26, reliability always wins. “If your bank is down, someone might miss a mortgage payment.” The culture encourages testing, redundancy, and resilience at every level.
7. Security is everyone’s job.
Every team has a security champion responsible for audits and best practices. Vendor integrations go through a formal security assessment to protect customer data.
8. Lessons from outages.
A misconfigured CDN once broke CSS for every customer. That post-mortem led to stronger Terraform practices and better guardrails around infrastructure changes.
9. Accessibility and compliance are non-negotiable.
The team uses React Axe, Playwright, and Radix UI to ensure accessibility testing happens in CI — not as an afterthought.
10. Culture matters more than code.
From mentorship to lightweight RFCs, Bruno highlights how strong culture and communication make large systems — and teams — more resilient.
🧠 What I Learned
- Reliability isn’t about perfection — it’s about predictability under stress.
- Developer experience is a direct multiplier for reliability.
- Automation and experimentation make teams faster and safer.
- The best platform engineers think in trade-offs, not absolutes.
💬 Favorite Quotes
“If your bank is down, it’s not just a bug — someone might miss their mortgage payment.”
“We cut deploy time from one hour to five minutes — and people started shipping again.”
“Server-driven UI means we can change what users see in minutes, not days.”
“The goal isn’t to move fast — it’s to move safely, repeatedly, and confidently.”
🎯 Also in this Episode
- How N26 organizes its platform and assistance teams
- The hidden cost of slow pipelines and flaky tests
- Why CI/CD ownership belongs to everyone
- How accessibility became part of the release checklist
- The difference between reliability and availability
🎧 Listen Now
🎧 Spotify
📺 YouTube
🍏 Apple Podcasts
Episode Length: 1h 7m on reliability, platform culture, and CI/CD at scale.
If you care about reliability, developer velocity, or building systems people can trust — this one’s worth your time.
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.