Curebase Software Engineer Interview Questions
& Process

The recruiter interview was a bit confusing but the technical and culture interview was really nice. The people were friendly and approachable. There was one round of technical questions, and the process moved quickly after the initial interview.

The interview process was great and fun. It basically had three steps. First, an intro interview combined with a tech interview which was high-level, just a conversation. Second, a code exercise that was simple and related to the role, not complex algorithms, more like daily stuff. Third, other interviews, including an architecture interview and another code exercise. During this phase, you'll meet more team members, like Product People and Managers. The architecture interview involves discussing architectural questions and providing the best possible answers. The new code exercise is a bit bigger than the first one but also relates to real-world issues. Overall, the whole process is great and fun, offering a chance to meet people from the company and ask plenty of questions.

So first, I had this initial chat with the recruiter, just to get a feel for things. Then, I talked to the head of engineering. After that, there was a technical screening. The final part was the 'on-site,' which was virtual. This involved talking about architecture, chatting with someone from the product team, and doing a bigger engineering task. Honestly, Curebase's technical interview was one of the best I've done – it was like a real-time project that actually made sense, none of that LeetCode stuff. It was a really practical way to assess skills. I think the more fun a technical interview is, the better, and I really dug this one. Plus, I enjoyed talking to everyone on the team; they were all super positive and seemed genuinely interested in getting to know me and if it would be a good mutual fit.