Nubank Interview Guide 2026: Process, Questions, and How to Land an Offer

What Makes Nubank Different

Nubank is not a typical fintech startup, and candidates who prepare for it as if it were a generic tech company make a costly mistake. Founded in 2013 by David Velez, Cristina Junqueira, and Edward Wible, Nubank has grown into the largest digital bank outside Asia, serving more than 100 million customers across Brazil, Mexico, and Colombia. The company trades on the New York Stock Exchange (NYSE: NU), has a market capitalisation exceeding $60 billion, and has fundamentally reshaped how Latin Americans interact with financial services — all without a single physical branch.

Several characteristics define Nubank and directly influence what interviewers evaluate:

• Customer obsession as a founding principle. Nubank was born from frustration with the bureaucratic, fee-laden Brazilian banking system. Every product decision, every engineering trade-off, and every hiring decision filters through a single question: “Does this make the customer’s life simpler?” This is not corporate lip service — Nubank’s entire operating model depends on eliminating the friction that traditional banks impose. Interviewers probe whether you genuinely think from the customer’s perspective or merely claim to.
• Clojure and functional programming. This is the single most distinctive aspect of Nubank’s engineering culture. While nearly every major tech company runs on Java, Python, or Go, Nubank built its entire core banking platform on Clojure — a functional programming language running on the JVM. The decision reflects a deep belief that immutability, pure functions, and data-oriented programming produce more reliable financial systems. If you are applying for an engineering role, you must understand what this choice means and why it matters, even if you have never written Clojure.
• No legacy systems. Unlike traditional banks that carry decades of COBOL and mainframe debt, Nubank was built from scratch on modern infrastructure. Its microservices architecture runs on Kubernetes, with Kafka for event streaming, Datomic as the primary database (an immutable, append-only database that aligns with functional programming principles), and extensive use of data pipelines for real-time decision-making. This means engineers work without the baggage of legacy migration — but also without the safety net of established patterns. You are expected to design systems from first principles.
• Low ego, strong ownership. Nubank’s culture explicitly rejects hierarchy-driven decision-making. The best idea wins regardless of who proposes it. Engineers are expected to challenge product decisions, PMs are expected to understand technical constraints, and everyone is expected to take ownership of outcomes rather than deflect blame. Interviewers look for genuine intellectual humility combined with a willingness to own your work completely.
• Latin American scale and complexity. Serving 100 million customers across three countries with different regulatory frameworks, currencies, and cultural norms creates engineering and product challenges that are distinct from those at US-centric companies. Real-time credit decisions for populations with limited credit history, fraud detection in markets with unique attack vectors, and payment processing across PIX (Brazil’s instant payment system), SPEI (Mexico), and traditional card networks all require domain-specific thinking.

Nubank’s interview difficulty is hard. The bar is comparable to top-tier US tech companies for engineering roles, with the added complexity of functional programming evaluation and fintech domain knowledge.

Interview Process Overview

Nubank’s hiring process follows a structured pipeline that is consistent across engineering, product, data, and business roles, though the content of each stage varies by position.

Stage	Format	Duration	Timeline
Recruiter screen	Video call	30 minutes	Week 1
Online coding challenge	Asynchronous	60-90 minutes	Week 1-2
Technical interviews	Video (2-3 rounds)	45-60 minutes each	Week 3-5
Case study / product round	Video call	60 minutes	Week 4-5
Culture fit round	Video call with hiring manager	45-60 minutes	Week 5-6
Offer	Written	—	Week 6-7

Recruiter Screen

The recruiter call covers your background, motivation for joining Nubank, and role alignment. Nubank recruiters are well-prepared and will ask specifically why you want to work at a digital bank in Latin America. “I am interested in fintech” is not enough — articulate what draws you to Nubank’s mission of fighting complexity to empower people. Demonstrate that you understand the Brazilian banking landscape and why Nubank’s approach matters to 100 million customers.

Online Coding Challenge

An asynchronous coding assessment, typically conducted on HackerRank or a similar platform. For engineering roles, expect algorithmic problems with a practical flavour — data transformation, concurrency, or problems that reward clean functional-style solutions. The challenge is language-agnostic (you can use Python, Java, or any supported language), but writing solutions in a functional style signals alignment with Nubank’s engineering values. Time limits are generous compared to competitive programming, reflecting Nubank’s emphasis on code quality over raw speed.

Technical Interviews

Two to three video rounds with Nubank engineers. These cover live coding, system design (for mid-level and above), and a deep dive into your past technical work. The tone is collaborative — interviewers want to see how you think through problems, not whether you have memorised solutions. Expect questions that touch on data modelling, distributed systems, and financial domain logic.

Case Study / Product Round

Depending on the role, this round presents a product or business scenario for you to analyse. Engineers may face a system design case with product trade-offs. PMs receive a product strategy challenge. Data scientists analyse a dataset and present findings. The common thread is that every scenario connects to Nubank’s actual business — credit risk, customer engagement, or operational efficiency.

Culture Fit Round

A conversation with a hiring manager or senior leader focused on alignment with Nubank’s values. This is not a soft conversation — interviewers ask pointed questions about how you handle conflict, give feedback, make decisions under uncertainty, and prioritise customer impact. Nubank takes cultural alignment seriously as a hiring criterion.

Role-Specific Breakdowns

Software Engineer

Engineering interviews at Nubank are shaped by the company’s functional programming philosophy. Even if you will not write Clojure on day one, interviewers evaluate your affinity for functional thinking.

Live coding rounds present practical problems. You may implement a transaction processing pipeline, a credit scoring function, or a data transformation utility. Interviewers pay attention to whether you reach for mutable state and side effects or naturally gravitate toward pure functions, immutable data structures, and composability. Writing in Python or Java is fine, but structuring your solution functionally — small pure functions, data pipelines, avoiding shared mutable state — earns strong positive signals.

System design (mid-level and above) focuses on fintech-scale problems: designing a real-time credit decision engine, a fraud detection pipeline, or an event-driven architecture for transaction processing. Nubank’s actual architecture is event-driven with Kafka, and understanding event sourcing and CQRS patterns is valuable. For more on preparing for these rounds, review our technical interview preparation guide.

Past work deep dive is a conversation about systems you have built. Interviewers want to understand your design decisions, trade-offs you made, and how you handled failures. They probe for intellectual honesty — did you own the mistakes, or do you blame external factors?

Product Manager

PM interviews at Nubank emphasise customer empathy, data fluency, and the ability to navigate regulatory constraints.

Round	Focus
Product sense	Designing for underbanked populations, financial inclusion, reducing friction
Analytical	Defining KPIs for credit products, A/B testing in regulated environments, cohort analysis
Technical depth	Understanding microservices, event-driven architectures, API design
Strategy	Latin American fintech market dynamics, competitive positioning against traditional banks
Culture	Customer obsession, low-ego collaboration, ownership

A common PM question involves improving an existing Nubank product — the interviewer evaluates whether you think about regulatory constraints, customer trust, and measurable outcomes, not just feature lists.

Data Scientist

Data science at Nubank is central to credit risk, fraud detection, and customer personalisation. Interviews test statistical reasoning, machine learning fundamentals, and SQL proficiency. Expect a take-home or live analysis of a dataset related to credit scoring or customer segmentation. The unique challenge is building models for populations with thin credit files — traditional FICO-style approaches do not work for millions of Nubank’s customers who had no prior banking relationship.

Business and Operations

Operations roles test analytical thinking, process design, and understanding of financial regulation in Latin America. Case studies often involve designing a customer onboarding flow compliant with Brazilian Central Bank (BCB) requirements, or optimising a collections process across multiple geographies. Quantify everything — Nubank’s culture demands measurable impact.

Clojure and Functional Programming

Nubank’s commitment to Clojure is not a quirky technology choice — it is a core architectural decision that shapes the entire engineering culture. Understanding why Nubank chose Clojure, and what functional programming means in practice, is critical for any engineering candidate.

Why Clojure?

Nubank’s founders chose Clojure because financial systems benefit enormously from immutability and referential transparency. When every piece of data is immutable and every function is pure, it becomes dramatically easier to reason about what happened in a transaction pipeline, reproduce bugs, and audit system behaviour — all critical requirements for a bank. Combined with Datomic (an immutable database where every state change is preserved as a fact), Nubank can reconstruct the exact state of any customer’s account at any point in time.

What Candidates Need to Know

You do not need to be a Clojure expert to pass the interview, but you must demonstrate:

• Understanding of immutability. Why is immutable data safer in concurrent financial systems? How does it simplify debugging and auditing?
• Pure functions and side-effect management. Can you separate business logic (pure) from I/O and state changes (side effects)? This is the core discipline of functional programming at Nubank.
• Data-oriented programming. Clojure treats data as plain maps and vectors rather than objects with methods. Can you model a problem using simple data structures and transformations rather than class hierarchies?
• REPL-driven development. Clojure’s development workflow centres on the REPL (Read-Eval-Print Loop) for rapid experimentation. Demonstrating familiarity with interactive development is a positive signal.

If you have experience with Haskell, Scala, Elixir, or even heavy use of functional patterns in Python or JavaScript, highlight it. The transferable skill is the mindset, not the specific syntax.

System Design at Nubank Scale

System design questions at Nubank are grounded in the realities of operating a bank serving 100 million customers across Latin America.

Common System Design Topics

Real-time credit decision engine. Design a system that evaluates a credit application and returns a decision in under two seconds. Address data sources (transaction history, bureau data, alternative signals), model serving architecture, feature computation pipelines, and how to handle the cold-start problem for customers with no credit history. Discuss regulatory requirements around explainability — Brazilian law requires that credit denials be accompanied by clear reasons.

Fraud detection at scale. Design a system that identifies fraudulent transactions in real time across PIX (instant payments), card transactions, and account transfers. Address the tension between false positives (blocking legitimate customers) and false negatives (letting fraud through). Discuss how attack patterns differ in Brazil compared to the US or Europe, and how the system adapts to new fraud vectors.

PIX payment processing. Design a system that processes Brazil’s instant payment system at scale. PIX transactions settle in seconds, 24/7, including weekends and holidays. Address high availability requirements, integration with the Brazilian Central Bank’s settlement system, idempotency for duplicate detection, and monitoring for anomalous transaction patterns.

Multi-country regulatory compliance. Design a system that enforces different regulatory rules across Brazil, Mexico, and Colombia. Address KYC requirements that differ by jurisdiction, transaction monitoring rules, and how to deploy regulatory changes without downtime. Discuss how Nubank’s microservices architecture allows country-specific logic without duplicating the entire platform.

Common Questions with Frameworks

1. “Implement a function that processes a batch of financial transactions and categorises them.” (Coding)

Approach: Clarify inputs and outputs. Implement using a functional pipeline: parse transactions, validate required fields, apply categorisation rules, and return results. Use pure functions for each step. Handle edge cases — malformed data, duplicate transactions, missing fields. Discuss how this approach makes the pipeline testable and composable. Avoid mutable accumulators; use map/filter/reduce patterns instead.

2. “Design a credit scoring system for customers with no traditional credit history.” (System Design)

Approach: Define alternative data sources: app usage patterns, bill payment history, transaction behaviour, geographic and demographic signals. Propose a feature engineering pipeline that computes signals from raw event data. Address model selection (logistic regression for interpretability vs. gradient boosting for accuracy), regulatory explainability requirements, and how to handle model drift over time. Discuss A/B testing credit policies safely — you cannot experiment recklessly with people’s credit access.

3. “Tell me about a time you challenged a decision made by someone more senior.” (Behavioural)

Approach: Use the STAR method. Choose an example where you respectfully disagreed based on data or customer impact. Emphasise how you presented your case — with evidence, not ego. Detail the outcome, whether you succeeded or not, and what you learned. Connect to Nubank’s low-ego culture — the company explicitly values people who challenge ideas constructively regardless of hierarchy.

4. “How would you improve Nubank’s customer onboarding conversion rate?” (Product/Case Study)

Approach: Start by mapping the current funnel: app download, registration, identity verification (KYC), credit assessment, first transaction. Identify where the largest drop-offs likely occur (identity verification is a common friction point in Brazil). Propose interventions with estimated impact: simplifying document capture, reducing verification wait times, providing clearer progress indicators. Define metrics and an experimentation plan. Address the trade-off between conversion speed and fraud risk — faster onboarding can increase fraud exposure.

For more question patterns and frameworks, see our guide to common interview questions and answers.

Culture: Nubank’s Purple DNA

Nubank’s culture — symbolised by its signature purple branding — is a deliberate rejection of traditional banking culture. Understanding these values is essential for the culture fit round.

Customer obsession. This is Nubank’s foundational value. Every decision, from product roadmaps to engineering architecture, is evaluated through customer impact. Interviewers expect concrete examples of when you prioritised the customer experience over internal convenience, speed, or technical elegance. Nubank’s famous customer service — where support agents have autonomy to solve problems creatively, sometimes sending handwritten notes or gifts — reflects a company-wide belief that customer love drives sustainable growth.

Low ego, high ownership. Nubank’s flat culture means ideas are evaluated on merit, not seniority. Engineers challenge PMs, junior analysts challenge VPs, and no one pulls rank. But low ego does not mean low accountability — everyone is expected to own their outcomes completely. Interviewers look for candidates who take responsibility for failures as readily as they claim successes.

Thinking big, acting fast. Nubank grew from zero to 100 million customers in roughly a decade. This required bold bets executed with speed and discipline. Interviewers evaluate whether you can think ambitiously while shipping incrementally. Perfectionism is not valued; pragmatic iteration is.

Fight complexity. Nubank’s internal motto reflects its external mission. Internally, this means resisting unnecessary process, bureaucracy, and over-engineering. In the interview, demonstrate that you simplify rather than complicate — in your code, your designs, your communication.

Compensation Overview (2026 Estimates, BRL)

Role	Base Salary (Annual, BRL)	Total Compensation (Base + Bonus + Equity)
Software Engineer (Mid-level)	R$180,000 - R$300,000	R$250,000 - R$450,000
Senior Software Engineer	R$300,000 - R$480,000	R$450,000 - R$750,000
Staff Engineer	R$480,000 - R$650,000	R$700,000 - R$1,200,000
Product Manager	R$200,000 - R$350,000	R$280,000 - R$500,000
Senior Product Manager	R$350,000 - R$500,000	R$500,000 - R$800,000
Data Scientist	R$180,000 - R$320,000	R$250,000 - R$480,000
Business/Operations Analyst	R$120,000 - R$220,000	R$150,000 - R$300,000

Nubank’s compensation is among the highest in Brazil’s tech market and competitive with international companies operating in Sao Paulo. The equity component is meaningful given the company’s NYSE listing — unlike private company equity, Nubank stock is liquid and publicly traded. Performance bonuses and equity refreshers reward sustained high performance. Some senior roles offer USD-denominated compensation, particularly for positions that support global functions.

Preparation Timeline: 5-7 Weeks

Week	Focus	Activities
1	Research and immersion	Download Nubank’s app (available in Brazil; research the experience if outside Brazil). Read Nubank’s engineering blog and tech talks on Clojure and Datomic. Study David Velez’s founding story and Nubank’s mission. Understand PIX, Brazilian banking regulation, and why traditional banks failed customers. Build your “why Nubank” narrative with specific, substantive reasons.
2-3	Coding with functional emphasis	Solve 50-70 coding problems focusing on data transformation, recursion, and pipeline patterns. Practice writing solutions using map/filter/reduce and immutable data structures even in Python or Java. Complete an introductory Clojure tutorial (Clojure for the Brave and True is free online) to understand the language’s philosophy. Review technical interview preparation strategies.
3-4	System design with fintech focus	Study event-driven architectures, event sourcing, and CQRS patterns. Learn payments-specific concepts: real-time credit decisioning, fraud detection pipelines, PIX settlement, and multi-country regulatory compliance. Practice designing 4-5 fintech systems end-to-end, emphasising the unique challenges of Latin American markets.
5	Product and case study preparation	Prepare for case study rounds: credit risk scenarios, onboarding optimisation, and product strategy for underbanked populations. Understand Nubank’s product portfolio (credit cards, personal loans, savings accounts, insurance, investment products) and competitive landscape.
6	Behavioural preparation	Draft 8-10 STAR stories emphasising customer obsession, low-ego collaboration, ownership, and simplifying complexity. Practice articulating your motivations for working in Latin American fintech specifically.
7	Integration and refinement	Run full mock interview loops: coding + system design + case study + behavioural. Refine weak areas. Light daily coding practice to maintain sharpness. Rest before interviews.

Common Mistakes

Ignoring Clojure and functional programming entirely. You do not need to be a Clojure expert, but walking into a Nubank engineering interview without understanding why functional programming matters for financial systems signals a lack of preparation. Spend time understanding immutability, pure functions, and data-oriented design — even if you demonstrate these concepts in Python or JavaScript.

Generic system design answers. Nubank operates in a distinct environment: PIX instead of ACH, CPF-based identity instead of SSN, credit scoring for thin-file populations, and regulatory compliance across three Latin American countries. Answers that assume a US-centric payments landscape will fall flat. Research the specific infrastructure of Brazilian fintech.

Not understanding the customer mission. Nubank exists because Brazilian banks charged excessive fees, imposed bureaucratic processes, and provided poor service to millions of people. If you cannot articulate why this matters and how it connects to the work you want to do, you will not pass the culture round. This is not a company where “I want to work at a top tech firm” is a sufficient answer.

Underestimating the culture evaluation. Low ego and strong ownership are not just nice-to-have qualities at Nubank — they are hard filters. Candidates who exhibit arrogance, blame others for failures, or cannot describe genuine collaboration will be rejected regardless of technical performance. Prepare specific examples that demonstrate humility and accountability.

Overlooking the Latin American context. Nubank’s challenges are unique to its markets. Financial inclusion for underbanked populations, real-time payments via PIX, currency volatility, and regulatory differences across Brazil, Mexico, and Colombia all shape the problems Nubank solves. Demonstrating awareness of this context — even at a surface level — differentiates you from candidates who treat Nubank as just another fintech company.

Prepare for Nubank with OphyAI

Nubank’s interview process tests a rare combination of functional programming aptitude, fintech domain knowledge, customer-centric product thinking, and cultural alignment with a company that redefined banking for over 100 million people. The functional programming emphasis alone requires preparation that most candidates overlook. For more on how Nubank hires in Brazil, visit our Nubank interview prep page.

Practice Nubank-style technical and product questions with instant AI feedback. Use OphyAI’s Interview Coach to practice Nubank interview formats, or Interview Copilot for real-time support during live Nubank interviews. Start practicing free →