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