I applied online. The process took 2 months.
My process took 10 weeks. The interviews were in this order:
What I learned at the end of the experience is that you have to tell some lies to pass the interview with the hiring manager. If you say that there is something that you don't do much because it is the responsibility of another role, but that you are willing to improve that skill, they don't take it into account. The best thing is to say that you have the experience, even if you don't have it.
I think that there is not a deep analysis of each of the stages, since from my perspective the characteristic they requested (making architectural decisions as if you were an architect) should have been reflected in that stage (stage 3) and how my thinking was about solving problems. Maybe in my daily work I don't make these architectural decisions (I help, but I don't take the final decision). In stage 3, they saw how I solved and I proposed architectural decisions, but they need somebody that had taken these decisions (only you, not with a team or with the help of the architect). In other words, if you don't have previous experience taking final architectural decisions and applying them in a production environment (as if you were an architect), you are discarded by the hiring manager.
How do you teach to others?
The following metrics were computed from 65 interview experiences for the Nubank Senior Software Engineer role.
Nubank's interview process for their Senior Software Engineer roles is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for Nubank's Senior Software Engineer interview process.