Real, anonymous reports from people who interviewed for Software Engineer at Nones, newest first and distilled into what to expect across the loop.
After a recruiter-style first touch, I ended up doing a round that mixed real technical work with DSA and aptitude. The technical side leaned on problem-solving and a bit of puzzle-like thinking, and I remember having to handle some guesswork/guesstimates that felt tricky even though the DSA portion was still there. I also had to talk through my thinking rather than just compute an answer, which made the pacing feel tense.
My process started with a screening call where we covered my background, skills, and why I was interested in the role. That conversation set the tone for the rest of the sequence, and then I moved into a more interactive stage that included both technical and behavioral questions. The atmosphere felt professional and comfortable, and the interviewers were friendly enough that I could actually have an engaging discussion rather than just get interrogated.
The interview process typically starts with a screening call followed by a sequence of assessments, including technical exams and HR interviews, culminating in a final round that may involve both technical and behavioral evaluations.
Candidates should expect a mix of technical questions that assess problem-solving skills, coding abilities, and real-world scenarios, with an emphasis on backend/API engineering topics, error handling, and performance optimization.
Behavioral questions are integrated throughout the process, focusing on teamwork, communication, and past challenges, with an expectation that candidates articulate their thought processes clearly during technical discussions.
The overall atmosphere of the interviews is described as professional yet relaxed, allowing for engaging discussions rather than high-pressure interrogations, which can help candidates feel more comfortable.
Candidates noted that the pacing of the interviews felt manageable, with interviewers often providing hints or support during technical questions, fostering a collaborative rather than competitive environment.
After the interviews, candidates often reflect on their performance, considering how they could improve their answers or approach, particularly in the final stages of the process.