Nubank logo

Nubank Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 199 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
51.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Nubank.

Showing 3 of 199
Nubank logo
Nubank

Senior Software Engineer

Engineering · half a year ago

Senior Average Positive experience No offer 3 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Coding Technical Behavioral

It started with an email, proposing a take-home coding challenge to build a calculation system. After I submitted it, there was a live session explaining the next steps. Then there was a long break of about a month and a half. I followed up a few times, and they said it was delayed but still moving forward. After that, I was invited for a technical interview, about 1.5 hours long. They asked me to extend the coding challenge, focusing on technical aspects and decision-making. Overall, the challenges were interesting and relevant, but the wait time between stages was longer than expected.

Confirmed questions6 questions
  • Could you walk me through the structure of your solution?
  • What technical decisions did you make and why?
  • How did you organize your code?
Nubank logo
Nubank

Software Engineer

Engineering · nearly a year ago

Mid Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Technical screen Background check
Interview formats
Technical Coding System Design Behavioral

It was quite a few steps, 5 in total. First, I talked with HR to go over the role and clarify things. Then, I had to submit some code based on a problem they gave me. After that, there was the classic whiteboard challenge where two architects presented a problem, and the goal was to come up with a working solution, not necessarily one perfect answer. Next, we did a code review of the code I'd previously submitted, and they asked me to make live modifications or additions to it, ensuring all tests passed. Finally, I had an interview with the manager to discuss cultural fit. I felt it was very long, and it's discouraging that if you do well in all but the last one, it seems like nothing counts.

Confirmed questions5 questions
  • With HR to align on the vacancy and explain it better.
  • Deliver code based on a problem.
  • The famous whiteboard, two architects put you in a problem and you need to get out on the other side. There's no right or wrong, the important thing is that the solution works.
Nubank logo
Nubank

Technical Lead

Engineering · a year ago

Lead Average Negative experience No offer 6 rounds
Interview process
Recruiter call Take home Technical screen Onsite Panel Group Presentation
Interview formats
Technical Coding System Design Presentation Behavioral

There are several stages: a chat with talent, a challenge project, an architecture discussion with two engineers (really cool), pair programming with two other engineers (they actually watch you code and ask questions), a chat with management, etc. Heads up: for the pair programming, they ask you to use the same project from the first stage, but they don't tell you this in the email instructions. Another important thing, even though they say the stages aren't elimination rounds, they actually are.

Confirmed questions1 question
  • Can you tell me about how you created the initial project, how you would develop it further, and the technologies involved?

Nubank Software Engineer Interview Questions

Quoted word for word from Nubank interview reports.

Design the architecture for a service that sends 4 files to an alleged Mastercard infrastructure.

Read reports

How would you process thousands of chargebacks sent in a maximum of 4 files per day?

Read reports

Wasn't the migration of entrepreneurs to the formality of an employment relationship a very big challenge?

Read reports

How does the company ensure that important technical decisions are made based on real impact, quality, and long-term product sustainability, rather than just deadline pressure?

Read reports

Why did you choose to use asynchronous communication for a part of your solution instead of synchronous calls?

Read report

Would you have an issue working hybrid while covering all the costs for in-person days in SP?

Read report

What would you do if you noticed your team was sidelining or excluding a team member in a hypothetical situation?

Read report

Would you be available to work 7 weeks remotely and 1 week in person?

Read report

Would you have an issue with learning a new language outside of the stack you are used to?

Read report

Formats, difficulty and experience

Across all 199 Nubank interview reports.

Interview formats

Behavioral 26.4%
Technical 24.8%
Coding 24.3%
System Design 11.9%
Presentation 7.3%

Interview difficulty

Easy 14.1%
Average 55.8%
Difficult 30.2%

Candidate experience

Positive 51.8%
Negative 36.2%
Neutral 12.1%