Real, anonymous reports from people who interviewed for Software Engineer at Curefit, newest first and distilled into what to expect across the loop.
I went through a DSA-heavy interview where there were two medium-hard questions. The first one was based on arrays, and the second one was centered on a heap. I remember feeling like the interviewer wasn’t very helpful during the process—there weren’t enough hints when I got stuck, and the explanations I did get ended up confusing me rather than clarifying things.
My process started with a technical interview focused on DSA, and it stayed pretty consistent in difficulty—medium-hard problems throughout. I worked through two questions, one rooted in array-style reasoning and the other tied to something like binary search style problem-solving. One question asked me to find a seat in a row where the distance to the nearest person is maximized, and the other involved manipulating a sorted array of gems to remove K gems while minimizing the largest gap between neighbors.
The interview process heavily emphasizes Data Structures and Algorithms (DSA), with candidates typically facing medium to hard problems across multiple rounds. Expect questions that require problem-solving skills in areas like arrays, heaps, trees, and dynamic programming.
Candidates generally experience a structured interview process that includes an initial online coding assessment followed by several technical rounds, often culminating in an HR discussion. The timeline can be tight, with quick scheduling between rounds, which may feel intense.
The overall vibe of the interviews tends to be collaborative and supportive, with interviewers often providing guidance and encouragement during coding sessions. This can help alleviate stress and keep candidates engaged in problem-solving.
In addition to DSA questions, candidates may encounter system design discussions, particularly in later rounds, where they are asked to design real-world applications or systems. This round focuses on understanding architecture and design trade-offs.
Candidates should prepare for behavioral questions that explore their past experiences and how they align with the company's culture. These discussions often occur in later rounds and focus on project experiences and personal fit.
While many candidates report a positive interview experience, the outcome can vary, with some not receiving offers despite feeling well-prepared. Reflecting on the process, candidates often wish they had focused more on depth of understanding rather than just solving problems.
