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 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.