NIO Software Engineer interview: coding, React timer, and offer declined

NIO·Software Engineer·Reported Jul 2026
Technical ScreenHR ScreenOnsiteOtherOfferMedium

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.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
NIO
Role
Software Engineer
Rounds
Technical Screen → HR Screen → Onsite → Other
Outcome
Offer
Difficulty
Medium
Date
Reported Jul 2026

Real NIO interview experiences

First-hand reports from NIO candidates — the rounds, the questions they were asked, and how it went.

All 6 NIO interview experiences