Interview experiences · NIO
NIO Software Engineer interview: coding, React timer, and offer declined
OfferTech screen → HR screen → Onsite → Other
After a recruiter call, I went through a short, fast technical process with a few behavioral touches. One version had four rounds split between coding and a manager conversation. Another was compressed into two rounds in one day, with a mentor or manager discussion and HR. When it was on-site, it took a few hours end to end, and HR was responsive about scheduling. The coding included easy-to-medi…
After a recruiter call, I went through a short, fast technical process with a few behavioral touches. One version had four rounds split between coding and a manager conversation. Another was compressed into two rounds in one day, with a mentor or manager discussion and HR. When it was on-site, it took a few hours end to end, and HR was responsive about scheduling.
The coding included easy-to-medium LeetCode-style questions and a live React timer countdown. A system-design discussion asked about something like TopK over a sliding window. Manager conversations covered my work and research from my resume, my career path, why NIO, OEM versus supplier preferences, and whether my English was sufficient.
I once received an offer quickly after the first interview but declined it. The process felt friendly and fair, and HR followed up quickly compared with the slow, frustrating processes I had heard about elsewhere.
Location: United States. Overall feedback: positive. Offer status: got offer.
Comments
Nothing here yet.
Join in on CSWork →