Real, anonymous reports from people who interviewed for Software Engineer at NIO, newest first and distilled into what to expect across the loop.
After a recruiter call, I ended up doing a short, pretty structured loop that moved fast. The format that stuck out was mostly rounds on the technical side with a couple of behavioral touches: one setup I experienced was four rounds in total, split between coding and then a manager-style conversation. Another version I went through was even more compressed—two rounds in a single day, with a mentor/manager-style discussion plus an HR round. Across that whole arc, the on-site time felt manageable, roughly a few hours end to end when it was on-site, and HR seemed responsive about scheduling.
My process started with a technical interviewer who first wanted to hear about my working experience, largely by walking through what was already on my resume. That part felt normal, but the rest of the screen had real pressure: I then got asked three algorithm questions in a LeetCode format. I hadn’t prepared for that at the time, so I fumbled more than I expected and ended up failing. The questions themselves weren’t presented gently, and the whole thing felt like I was being tested on readiness, not just background.
The interview process typically starts with a recruiter call, followed by a series of technical and behavioral interviews, often spanning multiple rounds. Candidates have experienced both compressed loops with fewer rounds and longer processes with multiple interviewers, but communication about the timeline can be inconsistent.
Candidates should prepare for a strong emphasis on coding and algorithm questions, often in a LeetCode format, as well as system design discussions. The technical interviews may include practical coding tasks and theoretical questions related to machine learning or software architecture.
Behavioral interviews focus on candidates' backgrounds, career paths, and motivations for joining NIO, with an emphasis on understanding personal fit within the company culture. Questions may explore experiences in team environments and alignment with company values.
While the interview process is generally described as professional, many candidates report significant delays and lack of communication from HR following interviews, leading to feelings of uncertainty and frustration. Timely feedback is often highlighted as a crucial area for improvement.
The overall interview environment is often described as friendly and professional, with interviewers aiming to create a positive experience. However, some candidates have reported feeling pressure during technical assessments, which can impact their performance.
Candidates suggest focusing on algorithmic problem-solving and familiarizing themselves with the specific technologies mentioned in their resumes, as well as practicing behavioral responses to common questions. Being prepared for both technical and cultural fit discussions is essential.