How Nubank Interviews in 2026: Process, Questions & What They Score
The complete process, reported questions, and what interviewers score.
Nubank / Interview snapshot
10
stages from
application to offer
35
reported questions
37
public sources
Independent: SupaCV is not affiliated with or endorsed by Nubank. This is one well-documented shape of Nubank's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Nubank candidate
The process, start to finish.
Nubank (Nu) is the Latin American digital bank. This playbook covers its software engineer hiring track; Nubank's early-career guide describes a different general process (online test, live case study, leadership interview, recruitment team interview) that is not covered here. Nubank's engineering blog lists the software engineer stages as an application form, a take-home exercise, pair programming, an architecture round (senior candidates only), an engineering interview and a Talent Acquisition culture-fit interview, and the Nu Mexico blog gives a similar five-step outline.
Candidate reports from Brazil, Mexico, Argentina and Canada broadly match this: a recruiter or People screen, a take-home coding challenge (usually a command-line financial program such as a capital-gains tax calculator or a transaction authorizer), pair programming that extends your own take-home code, a whiteboard architecture round, then People and Culture (sometimes called a Nubank Values interview) and hiring manager conversations.
The order of the pair programming and architecture rounds differs between sources, and a 2026 Toronto senior candidate describes a CodeSignal assessment, system design, an AI-assisted pair programming interview and a hiring manager round. Prep sites also describe a CodeSignal online assessment and a CoderPad live coding round; Nubank's engineer process pages list neither by name. Prep sites say 5 to 6 stages and estimate 4 to 8 weeks end to end; Nubank publishes no overall timeline.
Nubank publishes five company values, and its early-career guide says the selection process is designed to find people who align with its values. There is no public stage-by-stage scoring rubric. Job postings say AI-enabled tools may be used for interview transcription and analysis, say AI is not used to make final hiring decisions, and say Nu does not give individualized technical feedback.
Stage 1: Application and resume screen
about one week
Apply through the careers page; you can import a LinkedIn profile or upload a CV and answer initial questions about your interest in Nu. Nubank's engineering blog puts this step at about a week and says it looks at who you are and how your experience connects to Nubank's impact.
Stage 2: Recruiter / People team screen
about 30 minutes
A remote conversation with the recruiting team. The Nu Mexico blog says it covers the technical and social challenges you have faced, the stack, architectures and practices you have used, your experience with diversity, and your motivations. Prep sites add interest in fintech and salary expectations and give about 30 minutes; a 2026 Toronto candidate also lists background, salary expectations and work model. The Nubank pages give no duration. This stage is not in the engineering blog's list.
Stage 3: Online coding assessment
60-90 minutes
Prep sites describe an asynchronous, timed assessment, typically on CodeSignal, with 2 to 4 algorithmic tasks; one says some versions are proctored by software and another says AI-proctored in 2026. A 2026 Toronto candidate describes CodeSignal's project-based Industry Coding Assessment, a 2021 Mexico City candidate describes an algorithm exercise done at home, and a 2026 Brazil candidate describes a logic test in any language. One prep site gives 60 to 90 minutes; the others give no duration. Nubank's engineering blog and the Nu Mexico blog do not list this stage for engineers and start the technical steps with the take-home exercise, so not every candidate gets it.
Not in Nubank's engineer process pages; reported by prep sites and a few candidates; duration from a single prep site
Stage 4: Take-home coding exercise
5 days to about 2 weeks
An untimed coding exercise that simulates part of the team's day-to-day work. Stated windows: 5 to 7 business days (Nu Mexico blog) and about two weeks (Nubank engineering blog); candidates report 5 days (Brazil, 2022 and 2025) and 7 days (Mexico City, 2021), and one prep site says several days. Nubank's engineering blog says it looks at structured thinking, trade-off reasoning and transparency about decisions, that finishing it is not required, and that asking questions and sharing ideas is valued. Candidate reports describe a command-line capital-gains tax calculator and a transaction authorizer that reads JSON from stdin, in a language of your choice. The code is reused in the pair programming round.
Stage 5: Pair programming / code review of your take-home
60-90 minutes
One or two Nubank engineers ask you to share your screen, walk through your take-home code, then extend it live with new requirements while keeping the tests passing. Some candidates get a new problem instead, prep sites describe working on an existing codebase with a senior engineer, and a 2026 Toronto candidate describes an AI-assisted pair programming interview. The Nu Mexico blog calls pairing an extension of the technical exercise and advises blocking at least 1.5 hours; one prep site says 60 to 90 minutes and calls it the most frequently failed stage; one Mexico City candidate reports 1 hour. Nubank's engineering blog says it assesses how you explain your reasoning, take feedback and adapt solutions in real time.
Order varies: Nubank's engineering blog lists pair programming before architecture, but most candidate reports and the prep sites that give an order put architecture first
Stage 6: Architecture / system design round
varies
An online whiteboard session in which you design a solution to a business problem at scale and discuss your reasoning with Nubank engineers. Nubank's engineering blog lists it for senior candidates only and describes it as focused on complex, scalable and resilient systems; prep sites and some candidate reports describe it without a seniority restriction. Prep sites list fintech prompts such as ledgers, fraud detection and credit limits, and name Miro or Excalidraw. Nubank and the prep sites state no duration; the only figure is one Mexico City candidate who reports 1 hour, so length is unconfirmed.
Senior-only per Nubank's engineering blog; order relative to pair programming varies, with most candidate reports placing it first
Stage 7: Engineering / live coding interview
about 60 minutes
Nubank's engineering blog lists an engineering interview covering algorithms, logic and system design and gives no duration. Prep sites describe a medium-difficulty collaborative live coding round, with CoderPad named by two of them, where interviewers look for functional thinking. One prep site gives about 60 minutes and also says some candidates skip this round depending on their CodeSignal score. Whether it is separate from pair programming varies by region and level.
Live coding format and the 60-minute figure come from prep sites; Nubank's blog names the round but gives no duration
Stage 8: Talent Acquisition / People and Culture (values) interview
30-45 minutes
A behavioral conversation with Talent Acquisition or People about your career, projects, and how you learn, collaborate and challenge the status quo. Nubank's engineering blog lists it last and the Nu Mexico blog groups People and Culture with the pairing and architecture interviews, so its position varies. Two prep sites give 30 to 45 minutes. One candidate calls it the 'Nubank Values' interview, and one 2021 candidate says it covered gender, inclusion and customer focus. Candidates also report rejections late in the loop after passing the technical rounds.
Stage 9: Hiring manager / engineering leadership interview
varies
A conversation with the hiring manager, an engineering manager or a head of engineering about your experience, projects, cultural fit and behavioral topics, plus how the teams work. One 2025 candidate had two manager interviews. No source gives a duration for engineers; one prep site estimates 45 to 60 minutes for a culture round with a hiring manager. Number and length differ between candidate reports.
Not in Nubank's published stage lists; reported by candidates and one prep site
Stage 10: Offer and onboarding
about 4 to 8 weeks for the whole process (prep-site estimate)
After expectations are aligned you get an offer, followed by start-date and onboarding steps; the Nu Mexico blog gives no duration for this step. Prep sites estimate 4 to 8 weeks (one guide) or 5 to 7 weeks (another) from first contact to decision; Nubank publishes no overall timeline. Some job postings say the offer is conditional on meeting regulatory eligibility requirements and completing background checks.
End-to-end figure comes from prep sites; Nubank publishes no overall timeline
Reported interview time, one scale in minutes
Where the minutes go
- Recruiter / People team screen~30 min
- Online coding assessment60 to 90 min
- Pair programming / code review of your take-home60 to 90 min
- Engineering / live coding interview~60 min
- Talent Acquisition / People and Culture interview30 to 45 min
Not drawn: Application and resume screen, Take-home coding exercise, Architecture / system design round, Hiring manager / engineering leadership interview and Offer and onboarding, whose durations are not given in minutes.
02 / What Nubank scores
Nubank values
01
We want our customers to love us fanatically
02
We are hungry and we challenge the status quo
03
We think and act like owners, not renters
04
We build strong and diverse teams
05
We pursue smart efficiency
The five value names are copied from the section headings on Nubank's official culture page (https://building.nu.com/nubank-culture-and-values/), which calls them core values and pillars. Its intro list words two of them slightly differently: "We are hungry and challenge the status quo" and "We think and act like owners".
Nubank's early-career careers blog (https://building.nu.com/5-tips-for-those-who-want-to-start-a-career-at-nu/) says the selection process is designed to identify people who align with its values and links to the culture page, but it is aimed at early-career candidates, describes a different stage list, and names its own pillars as innovation, customer obsession and inclusivity. The culture page itself does not mention interviews, and the careers page (https://nu.com/en/careers) has no formal values list. Nubank does not publish a rubric linking values to stages or a scoring scheme.
Read the rest of the framework notesShow less
The software engineer process post (https://building.nu.com/what-is-the-interview-process-like-for-software-engineers-at-nubank/) describes stage-level traits in looser wording, such as collaboration, constructive challenge of the status quo and adaptability. Treat the values as the culture lens for the People and Culture and hiring manager rounds, not as a formal scorecard.
03 / Coach's notes
Coach's tips.
01
Treat the take-home as the base for the later rounds. The Nu Mexico blog calls pairing an extension of the technical exercise and candidate reports say you extend your own submission live, so write small, tested, easy-to-extend code in the language you know best, and before the call, review which choices you would defend and which you would change.
02
Nubank's engineering blog says the take-home looks at structured thinking, trade-off reasoning and transparency about decisions, and that finishing it is not required, so ask questions and explain your choices. Keep it a plain command-line program unless the brief asks for more: reported tasks read JSON from stdin and write to stdout, and one older candidate report says adding a database counted against them.
03
Think out loud in pair programming and architecture. Nubank's engineering blog says pair programming assesses how you explain your reasoning, take feedback and adapt solutions in real time, and the Nu Mexico blog advises going beyond the solution and discussing it with the engineers on the other side in the architecture round. Prep sites name silence as the most common failure, and one candidate advises voicing your reasoning and edge cases, such as selling more shares than you hold. A 2026 Toronto candidate describes AI-assisted pair programming, so ask your recruiter what the format is for your team.
04
You do not need to know Clojure, but show functional habits such as avoiding mutable state and side effects, which prep sites say interviewers look for even outside Clojure. The Nu Mexico blog says candidates with little or no Clojure experience who complete the hiring process get free access to a specialized course.
05
Prepare fintech-specific design topics that prep sites and candidates report: ledgers, idempotency for payment APIs, fraud detection, credit limits, and distributed-system consistency and resilience trade-offs.
06
Prepare real stories for the People and Culture and manager rounds that map to Nubank's five values, especially owning outcomes, challenging the status quo and working in diverse teams. Candidates report rejections late in the loop after passing technical rounds, with no explanation, and Nubank's job postings say Nu does not give individualized technical feedback. If you need work authorization or visa support, ask early: a 2026 Toronto candidate reports an offer stalling over visa sponsorship, and some postings make offers conditional on regulatory eligibility and background checks.
04 / The research
Where this page comes from.
Compiled from public sources across 9 sites.
- sites
- 9
- candidate reports and forums
- 25
- coaching and prep guides
- 12
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Nubank's own domain, candidate forums, and everything else.
- Candidate reports and forums25
- Coaching and prep guides12
05 / The questions
Reported questions, by category.
Showing questions for
Roles are grouped by the category each question fits, not by the source.
Take-home and coding
7 questions
Take-home: implement a command-line program that calculates the tax owed on buying and selling stocks (capital gains), following a set of given requirements.
Stateful business-rule calculation over sequential buy and sell operations, built as a testable command-line program.
Take-home (Authorizer): implement an application that authorizes a transaction for a specific account following a set of predefined rules, reading account and transaction JSON lines from stdin and printing account state plus violations such as insufficient-limit.
Rule validation over a stream of JSON account and transaction events, with violation reporting through stdin and stdout.
Write a CLI project for a financial problem.
Modeling a financial problem as a command-line program: input handling, rule logic and clear output.
Write a job queue management algorithm with input and output through stdin/stdout, using JSON as the data format; then build a REST API on top of it in a second challenge.
Algorithm design over JSON on stdin and stdout, then extending it into a REST API in a functional style.
Learn basic Clojure and build a simple application.
Learning a functional language quickly and building a small working application in it.
Implement a transaction ledger validator that checks balance consistency across a sequence of events.
Validating balance consistency across an ordered sequence of events, a state-tracking and edge-case problem.
Implement a function that processes a batch of financial transactions and categorises them.
Batch processing and rule-based classification of transaction records with edge-case handling.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Architecture and system design
8 questions
Design a ledger system (for example a double-entry ledger).
Data model and consistency guarantees for a double-entry ledger of debits and credits.
Design a real-time fraud detection pipeline that processes millions of transactions daily with sub-100ms latency requirements.
Streaming architecture under a sub-100ms latency budget at millions of transactions per day.
Design a credit limit service.
Service design for credit limit decisions: data model, API boundaries and consistency.
Design the event sourcing architecture for a PIX payment system that requires an immutable audit trail.
Event sourcing with an immutable audit trail for payments: event model, replay and regulatory traceability.
Design a credit scoring system for customers with no traditional credit history.
Scoring system design without traditional credit history: alternative signals, model serving and risk trade-offs.
Design a high-throughput, resilient distributed system ensuring data consistency.
Distributed system trade-offs between throughput, resilience and data consistency.
Answer questions about the architectural decisions you proposed during the whiteboard design.
Justifying design choices and trade-offs from your own architecture under interviewer questioning.
Solve real problems the company faces involving concurrency, distributed systems and parallelism.
Concurrency, distributed systems and parallelism applied to real problems the company faces.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Pair programming
4 questions
Share your screen and present your take-home code, then extend it live: return an error if the user tries to sell more shares than they bought, and block the user after three consecutive errors.
Live extension of your own code with new rules (sell limit, block after three errors) while keeping tests green.
Extend your take-home solution with new features proposed by the interviewers, keeping all tests passing.
Extending existing code under new requirements live while keeping the test suite passing.
Answer questions about the project you submitted, including the decisions you made in the application and the improvements you would make.
Explaining design decisions and trade-offs in code you wrote, and where you would improve it.
Fix a bug, add a feature or refactor a module in an existing codebase with a senior engineer.
Debugging, feature work or refactoring in an unfamiliar codebase while narrating your reasoning.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Every role
Motivation and behavioral
7 questions
Why do you want to work at Nubank?
Why are you leaving your current company?
Walk me through your career and where you are today.
Tell me about tough situations you had in past work environments and how you overcame them.
What were the main challenges you faced in your most recent role?
Tell me about a relevant past experience at another company.
Tell me about a memorable bug you found.
Every role
Values and culture
9 questions
Tell me about a project you owned end to end.
Tell me about a time something you released broke in production.
Tell me about a time you challenged how your team did something.
Tell me about a time you challenged a decision made by someone more senior.
Describe a time you disagreed with a technical decision and how you handled it.
Tell me about a conflict inside your team and how it ended.
How do you approach working with engineers from different cultural and linguistic backgrounds?
Tell me about a time you had to deliver results with significant constraints.
Tell me about a time you made a decision with incomplete information.
Your next step
Interviewing at Nubank?
Make sure your resume gets you to the first round.
Practicing for Nubank against your resume is in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Nubank's interview process?
Nubank has 10 stages, set out in The process.
What framework does Nubank use to evaluate candidates?
Nubank evaluates candidates against Nubank values, set out in What Nubank scores.
What kinds of questions does Nubank ask?
Nubank's questions fall into 5 categories, grouped in The questions.
How reliable is this Nubank interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (37)
Every public source this page was compiled from. Links open in a new tab.
9 sites, by sources
- glassdoor.com25
- building.nu.com4
- designgurus.io2
- blog.nu.com.mx1
- nu.com1
- api.ashbyhq.com1
- techprep.app1
- finalroundai.com1
- ophyai.com1
- 01building.nu.com/what-is-the-interview-process-like-for-software-engine…
- 02blog.nu.com.mx/nu-mexico-una-financeira-solida-y-regulada-acerca-de-n…
- 03building.nu.com/nubank-culture-and-values
- 04building.nu.com/5-tips-for-those-who-want-to-start-a-career-at-nu
- 05building.nu.com/what-you-need-to-know-to-work-at-nubank
- 06nu.com/en/careers
- 07api.ashbyhq.com/posting-api/job-board/nubank
- 08techprep.app/blog/nubank-interview-process
- 09designgurus.io/answers/detail/what-is-the-nubank-interview-process-li…
- 10designgurus.io/answers/detail/top-nubank-behavioral-interview-questio…
- 11finalroundai.com/blog/nubank-interview-process
- 12ophyai.com/blog/company-guides/nubank-interview-guide
- 13glassdoor.com/Interview/Nubank-Interview-E827975-RVW95032939.htm
- 14glassdoor.com/Interview/Nubank-Interview-E827975-RVW99229726.htm
- 15glassdoor.com/Interview/Nubank-Interview-E827975-RVW101103232.htm
- 16glassdoor.com/Interview/Nubank-Interview-E827975-RVW95650271.htm
- 17glassdoor.com/Interview/Nubank-Interview-E827975-RVW44494502.htm
- 18glassdoor.com/Interview/Nubank-Interview-E827975-RVW49888365.htm
- 19glassdoor.com/Interview/Nubank-Interview-E827975-RVW66167686.htm
- 20glassdoor.com/Interview/Nubank-Interview-E827975-RVW67825756.htm
- 21glassdoor.com/Interview/Nubank-Interview-E827975-RVW29174347.htm
- 22glassdoor.com/Interview/Nubank-Interview-E827975-RVW89415789.htm
- 23glassdoor.com/Interview/Nubank-Interview-E827975-RVW103221639.htm
- 24glassdoor.com/Interview/Nubank-Interview-E827975-RVW101856471.htm
- 25glassdoor.com/Interview/Nubank-Interview-E827975-RVW102625727.htm
- 26glassdoor.com/Interview/Nubank-Interview-E827975-RVW91607386.htm
- 27glassdoor.com/Interview/Nubank-Interview-E827975-RVW70842803.htm
- 28glassdoor.com/Interview/Nubank-Interview-E827975-RVW48950535.htm
- 29glassdoor.com/Interview/Nubank-Interview-E827975-RVW34612866.htm
- 30glassdoor.com/Interview/Nubank-Interview-E827975-RVW32060759.htm
- 31glassdoor.com/Interview/Nubank-Interview-E827975-RVW27266770.htm
- 32glassdoor.com/Interview/Nubank-Interview-E827975-RVW25766603.htm
- 33glassdoor.com/Interview/Nubank-Interview-E827975-RVW19419770.htm
- 34glassdoor.com/Interview/Nubank-Interview-E827975-RVW105015763.htm
- 35glassdoor.com/Interview/Nubank-Interview-E827975-RVW105344678.htm
- 36glassdoor.com/Interview/Nubank-Interview-E827975-RVW105465141.htm
- 37glassdoor.com/Interview/Nubank-Interview-E827975-RVW105819060.htm
Related reading
- STAR, XYZ, or CAR: Which Resume Bullet Formula Actually Works?STAR, XYZ and CAR all collapse to the same bullet in practice, why "quantify everything" is more contested than it sounds, and the one modern use of STAR that actually earns its keep.
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
How similar companies interview
Compare Nubank's process with other Fintech & Payments companies in this playbook: