What Is the Nubank Interview Process Like? (Round by Round)

Candidates report that the Nubank engineering interview has five to six stages. It starts with a recruiter screen of about 30 minutes and an online coding challenge. Then come a live coding round, a system design round, and a pair programming session. A behavioral interview of about 30 to 45 minutes closes the loop. The process rewards a functional programming mindset and clear communication. Plan for several weeks from application to decision.

Quick Overview

Recruiter Screen

A recruiter reviews your background, your interest in fintech, and your expectations. Prepare a short answer to the motivation question. How to answer "Why do you want to work at Nubank?" covers it in detail. Also prepare a two-minute summary of your strongest project. Recruiters pass notes to later interviewers, so specifics here help you twice.

Online Coding Challenge

Candidates report an asynchronous assessment with two to four algorithmic tasks on a platform such as CodeSignal. Asynchronous means you complete it alone, on your own schedule, within a deadline. Correctness matters more than speed tricks. Test your solution against edge cases before submitting. Empty inputs, single elements, and repeated values are the usual traps. Some versions of the assessment are proctored by software, so prepare a quiet room and a working camera.

Live Coding

This round is collaborative problem solving in a shared editor, usually at medium difficulty. Candidates report that interviewers notice a functional style even in Python or Java. That means avoiding mutable state (data that changes in place) and using functions such as map and reduce. Narrate your plan before typing, and keep functions small.

System Design

The design round uses an online whiteboard such as Miro or Excalidraw. The scenarios come from Nubank's own domain: ledger systems, payments, and fraud detection. Expect questions about consistency models, idempotency, and event-driven architecture. What to expect in the Nubank system design interview explains these topics and one worked example.

Pair Programming

This is the most distinctive stage. You work with a senior engineer on a real codebase: fixing a bug, adding a feature, or refactoring a module. The evaluation is how you work, not just what you produce. Ask clarifying questions, say your reasoning out loud, and write tests as you go. Silence is the most common failure here.

Treat the engineer as a colleague, not an examiner. It is fine to ask where a function lives or what a name means. A real teammate would ask. Reading unfamiliar code calmly, out loud, is exactly the skill being measured.

Behavioral Interview

The final conversation runs about 30 to 45 minutes with competency questions. Competency questions ask for real past examples, not opinions. The themes are ownership, accountability, teamwork, and challenging the status quo. Top Nubank behavioral interview questions lists the questions with a worked outline.

Note that behavioral evidence is collected everywhere, not only here. The pair programming session shows your teamwork directly. The design round shows how you handle disagreement. Consistency across rounds is part of the score.

How to Prepare

• Practice medium-level problems in a clean style. Grokking the Coding Interview teaches the patterns the challenge and live round test.
• Study fintech design blocks. Ledgers, idempotency, and event streams repeat across the loop. Grokking the System Design Interview builds that base.
• Practice pairing out loud. Do one mock session where you narrate every decision. The pair programming round scores exactly that habit.
• Try a small functional exercise. Write one solution without mutating any data. You do not need Clojure, but the mindset must show. Nubank hires from every language background and teaches the stack internally.