COMPANY_GUIDE

Nubank System Design Interview: Complete Preparation Guide

Master Nubank's system design interview with tips on Latin American neobanking, Clojure microservices, event-driven architecture, and scale design.

22 minUpdated Apr 25, 2026
nubanksystem-designinterviewfintechpreparation

Interview format

5 rounds total.

System Design50 min

Design a banking or financial product system. Nubank emphasizes event-driven architecture, functional programming principles, and serving underbanked populations.

Coding 150 min

Algorithm problem. Nubank famously uses Clojure, but interviews accept any language. Functional programming skills are a plus.

Coding 250 min

Second coding round, often involving data transformation, pipeline design, or a problem that benefits from functional thinking.

Technical Deep Dive45 min

Discussion of past experience or a deep dive into distributed systems, data engineering, or financial infrastructure.

Behavioral / Culture Fit45 min

Assesses alignment with Nubank's values: thinking like a customer, being data-driven, and challenging complexity.

Commonly asked systems

Design a credit card management system for 90+ million customersDesign a real-time fraud detection pipeline for Latin American marketsDesign a personal loan origination and servicing platformDesign an event-sourced financial ledger systemDesign a customer onboarding pipeline for underbanked populationsDesign a real-time notification and communication platformDesign a rewards and loyalty program at massive scaleDesign a PIX (instant payment) processing system

What they evaluate

Event-Driven ArchitectureHigh

Nubank is deeply event-sourced. Can you design systems using event streaming, CQRS, and immutable event logs?

Scale DesignHigh

Nubank serves 90+ million customers. Can you design systems that operate at this scale while maintaining reliability?

Financial CorrectnessHigh

Banking requires exact correctness. Nubank evaluates your approach to ledger design, transaction isolation, and reconciliation.

Functional ThinkingMedium-High

Nubank's Clojure culture values immutability, pure functions, and composability. Can you apply these principles to system design?

Customer EmpathyMedium

Many Nubank customers are new to banking. Can you design systems that are simple and accessible for underbanked populations?

Tips

  • Study Nubank's technology stack: Clojure, Datomic, Kafka, and their event-sourced architecture philosophy
  • Understand event sourcing deeply — Nubank stores events as the source of truth and derives state from them
  • Know how PIX (Brazil's instant payment system) works — it processes billions of transactions and is central to Nubank's offering
  • Study functional programming principles even if you don't know Clojure: immutability, pure functions, composition
  • Think about designing for underbanked populations: simple onboarding, minimal documentation requirements, mobile-first
  • Nubank uses Datomic — understand its immutable, time-based data model and how it differs from traditional databases
  • Be ready to discuss how to handle fraud detection at scale in a market with high fraud rates

Preparation roadmap

Week 1-2Nubank Tech & Domain Fundamentals
  • ·Study event sourcing and CQRS patterns in depth
  • ·Learn about Nubank's Clojure and Datomic technology choices and their rationale
  • ·Understand Brazilian banking: PIX, Boleto, credit card regulation, Central Bank requirements
  • ·Review Nubank's engineering blog for architecture and culture insights
Week 3-4Core Banking Systems
  • ·Design an event-sourced financial ledger system
  • ·Design a credit card management platform for 90+ million users
  • ·Design a PIX instant payment processing system
  • ·Study Kafka-based event streaming at scale: partitioning, ordering, exactly-once
Week 5-6Scale & Financial Products
  • ·Design a loan origination system with credit scoring for underbanked populations
  • ·Design a real-time fraud detection pipeline for Latin American markets
  • ·Design a rewards program that scales to tens of millions of users
  • ·Study database scaling: Datomic, Cassandra, and their trade-offs at Nubank scale
Week 7-8Mock Interviews & Review
  • ·Do at least 3 mock system design interviews with event-sourced architectures
  • ·Practice explaining event sourcing trade-offs: storage, rebuild time, complexity
  • ·Prepare behavioral stories about building for underserved populations
  • ·Review Nubank's engineering blog and conference talks for system design insights
PRO

Unlock with Pro

Unlock the full content and everything at this level.

Get Pro — $9/moAlready a member? Log in

GO DEEPER

Master this topic in our 12-week cohort

Our Advanced System Design cohort covers this and 11 other deep-dive topics with live sessions, assignments, and expert feedback.

FREE_COURSES
preview