Real, anonymous reports from people who interviewed for Software Engineer at nCino, newest first and distilled into what to expect across the loop.
After a recruiter screen, I ended up in a panel-style interview where the overall vibe felt very positive and not intimidating. The structure was a mix of behavioral and situational questions, and the panel took turns asking things rather than firing rapid-fire follow-ups. It felt more like a back-and-forth conversation than a checklist.
My process started with an OA that focused on a pretty straightforward coding idea—counting occurrences of words in a string. A little later I had a phone screening that was mostly about the company and why I wanted the role.
The interview process is structured with a mix of behavioral and technical assessments, often conducted in a panel format that emphasizes conversation over interrogation, creating a friendly and relaxed atmosphere.
Candidates typically encounter a technical assessment early in the process, which may include coding challenges and system design questions, with an emphasis on problem-solving approach rather than just correct answers.
Interviews heavily focus on behavioral questions and cultural fit, with prompts designed to understand candidates' thought processes, communication styles, and how they handle various situations.
The interview process can involve multiple rounds and lengthy discussions, often lasting several hours, which allows for in-depth exploration of candidates' experiences and skills.
While the interviews are generally perceived as fair and respectful, candidates report mixed outcomes, with some experiencing delays in feedback or unexpected rejections, impacting their overall impression of the company.
Candidates are advised to prepare for a range of technical skills, including programming fundamentals and debugging, as well as specific technologies relevant to the role, such as Salesforce or Angular.
