Mambu Software Engineer Interview Questions
& Process

The interview process involved a 30-minute initial chat with HR, followed by a 1-hour meeting with the hiring manager. Then there was a 3-hour take-home coding assignment (Go), and finally, a 1-hour technical discussion. The process moved to the last stage even though there was a clear disconnect in how questions were asked and how answers were judged. Some technical questions lacked sufficient detail. When candidates tried to clarify assumptions or constraints, it was viewed negatively instead of being used to get on the same page about the problem. If answers didn't meet unstated expectations, the conversation turned argumentative instead of being helpful. The evaluation criteria seemed to prioritize experience with fintech integration patterns over critical thinking, problem definition, or open discussion of trade-offs. Candidates without extensive fintech integration background should make sure to clarify expectations upfront.

The interview process consisted of three main parts: first, a discussion with the hiring manager, followed by a technical assessment using Codility (which I found to be an excellent tool for technical interviews), and finally, an interview with a manager from a different team to confirm that my soft skills align with the company's needs.

Someone from mambu reached out about a job, I had an interview with them and then another with HR before the actual hiring process began. Both the HR person and the recruiter started trying to sell me on this "low code" role, which wasn't what we initially discussed (a Python dev job). The last interview I had was a phonescreen, and they mentioned one more interview would follow, but I never heard back. Even after I reached out, I got no feedback at all... I was also sent a link to one of their open-source projects, and the code standards were pretty disappointing: methods with 20 parameters, methods that were 200-300 lines long, and a lack of consistency (some parts were fully OOP and others fully procedural). My guess is they're looking for "low code" developers by initially luring candidates with a different job, and if you don't go for the pitch, you're ghosted.