I ended up doing a pretty compact, three-step loop at Nike. After the initial recruiter call, about a week later I had a technical screen where I went through technical details with a couple of hiring managers in a roughly 60-minute segment. It didn’t feel like a gotcha; the conversation stayed tied to specifics of what I’d built and how I approached problems.
After that, I had a final wrap-up call with a director that lasted about 30 minutes. Overall it felt straightforward in structure—no long gauntlet—but the bar still felt real since the technical discussion carried the process. I didn’t receive an offer, and the whole thing left me feeling like I’d put in solid effort, even though it still didn’t land.
2 months ago
Easy Negative Bengaluru
My process was odd and frustrating from the start. I got a virtual interview call only after multiple follow-ups with HR, and it happened even though I wasn’t invited to an ongoing face-to-face hiring drive.
After the interview, I reached out to HR for an update, expecting some normal status message. The only response I received was essentially a demand to stop texting. That experience completely soured the process for me—no clear closure, just hostility—so even though I made it to the interview stage, there was no offer and the whole journey felt disrespectful.
2 months ago
Easy Positive Domlur
My interview ended up being a long, somewhat tedious day, but it was also useful in the sense that I got to know the people and the setting pretty wel…
3 months ago
Average Positive United States
After a recruiter screen, I went straight into a technical interview that felt very “LeetCode-style.” Then I had an engineering expertise conversation…
4 months ago
Difficult Positive Bengaluru
My Nike process started with a HireVue that combined behavioral prompts with a technical coding portion. A short time later, I had two back-to-back in…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically consists of a recruiter call followed by one or more technical interviews, often including coding challenges and behavioral discussions. The timeline can vary, with some candidates experiencing a quick progression while others report delays and lack of communication.
Technical interviews often emphasize coding skills with a mix of DSA-style problems and practical application questions related to the candidate's past projects and technologies like AWS, Node.js, and React. Candidates should be prepared for both algorithmic challenges and system design discussions.
DSASystem designAWS
Behavioral Interviewing
Behavioral interviews are integral to the process, focusing on candidates' experiences, problem-solving approaches, and cultural fit with Nike. Candidates should be ready to articulate their motivations for applying and how they align with Nike's values.
Cultural fitMotivationSTAR method
Candidate Experience & Communication
While many candidates report a generally positive and respectful interview atmosphere, frustrations arise from poor communication post-interview, with some candidates feeling ghosted after promising interactions. Clear feedback and closure are often lacking.
Candidate experienceCommunicationFeedback
Interview Difficulty & Expectations
The overall difficulty of interviews is described as average, but candidates should expect a mix of straightforward and challenging questions, particularly in technical assessments. Preparation should include both foundational knowledge and practical application skills.
Average difficultyPreparationFoundational knowledge
What Candidates Wish They'd Done
Candidates often reflect on the importance of articulating their thought processes clearly and anchoring discussions to their resume and project experiences. Practicing communication skills and being prepared for technical discussions can enhance performance.