Nubank Interview Questions
& Process

The hiring process is quite long and demanding, with about eight stages, each lasting around an hour. In total, a candidate can easily spend over 8 hours throughout the process, including technical interviews, HR chats, values assessments, and manager interviews. Technical stages are heavily focused on real-time performance and solving specific programming problems. However, there's little emphasis on evaluating the candidate's history, previous experiences, or their potential to make a real impact on the company. Generally, the process seems to prioritize performance in specific interviews rather than a broader analysis of the candidate's skills and contributions throughout their career. Also, considering the technical demands and need for English fluency, the time investment might not be proportional to the perceived return, especially compared to international opportunities paid in dollars. Throughout the process, the length and format of the stages can be demotivating for many.

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.

So, the interview at Nubank was pretty structured, really focused on how I think about problems, business sense, and talking things through. It kicked off with a chat with a recruiter, just covering who I am, why I like Nubank, and if I seem like a good fit overall. Then came a case interview, which was the main event. I had to break down a business problem, explain my thinking super clearly, figure out what numbers mattered most, and then suggest some actual, doable solutions. They really cared about how I handled uncertainty, what I chose to assume, and how I backed up my ideas with data, not just the final answer. We also talked about my past jobs, how I deal with different people, my skills with SQL and analyzing data, and how I'd team up with others. It was tough, yeah, but felt fair, with a big emphasis on thinking logically and making a real business impact.

The interview process is pretty solid from a technical standpoint. Their scheduling system and candidate portal are straightforward and user-friendly. Early communication is usually prompt, and the team is generally responsive. The interviewers are engaged and ask good, detailed questions. On the downside, the whole thing can drag on for more than a month with several stages. What was a bit of a letdown was the final communication. After finishing all the interviews, the rejection came via an automated, AI-generated email with no personal feedback. After putting in a lot of time and effort to prepare, a more personal and helpful closing message would really make a difference.