Real, anonymous reports from people who interviewed for Software Engineer at nCino, newest first and distilled into what to expect across the loop.
My process ended up being much longer than I expected. It stretched across four rounds—starting with a phone screening, moving into a technical assessment, then an in-person panel interview, and finally an offer stage. The rounds themselves were a mix: some parts felt easy or average, and then there was at least one section that was clearly harder.
After connecting with a recruiter, I went straight into a technical assessment that set the tone for the rest of the process. A panel interview followed, and it ended up being surprisingly comfortable—more like an ongoing conversation than a rapid-fire Q&A.
The interview process typically consists of multiple rounds, starting with a recruiter screening, followed by a technical assessment, and culminating in an in-person or panel interview. Candidates noted that the overall timeline can feel lengthy and uncertain, with some experiencing delays in communication after the final stages.
Candidates undergo various technical assessments, including coding challenges and practical systems work, often focusing on Salesforce configurations and basic programming concepts. The assessments are generally perceived as fair, with an emphasis on reasoning and problem-solving rather than trick questions.
Interviews often include a strong focus on behavioral questions and cultural fit, with interviewers looking for candidates' past experiences and how they handle trade-offs and ambiguity. The conversational style of these interviews helps create a relaxed atmosphere, although the depth of evaluation can vary.
Panel interviews tend to be friendly and engaging, with interviewers genuinely interested in understanding candidates' thought processes and experiences. This supportive environment can help alleviate initial intimidation, allowing for a more open dialogue about technical and behavioral topics.
Many candidates reported not receiving offers despite feeling the interview process was fair and well-structured. Feedback on the outcome can sometimes be delayed, leading to frustration, especially when candidates felt they had performed well during the interviews.
Candidates suggested that focusing on foundational programming concepts and being prepared to discuss past experiences in detail would be beneficial. Understanding the role's responsibilities and being ready for both technical and behavioral questions can enhance performance during interviews.