Nike Software Engineer interview typically runs 3-5 rounds: HR, technical lead, peers, manager, and sometimes a panel. Timeline is a few weeks to a couple months, and the process is often practical, whiteboard-based, and resume-driven.
$137K
Avg. Base Comp
$187K
Avg. Total Comp
4-6
Typical Rounds
2-8 weeks
Process Length
Our candidates consistently describe Nike as less interested in abstract algorithm performance and more focused on whether you can credibly defend the stack on your resume. Across experiences, interviewers kept pulling candidates back to Node.js, JavaScript, TypeScript, React, AWS, CI/CD, and the architecture choices behind past projects. That pattern shows up in both the whiteboard-heavy conversations and the more hands-on coding rounds: they want to hear how you’ve built things, why you made those tradeoffs, and whether you can explain them without drifting into buzzwords.
A recurring theme is that Nike seems to value practical engineering judgment over polished theory. Multiple candidates mentioned questions about deployment, delivery, client escalations, and even how a UI like an Excel sheet should behave when copying rows and columns. That tells us the bar is not just “can you code,” but “can you reason about real product behavior and operational edge cases.” When candidates struggled, it was often because their answers felt memorized or too shallow for the claims on their resume.
We also see a split in style by team or location: some loops felt conversational and architecture-oriented, while others were more rigid and fundamentals-driven, with quick checks on Git, HTTPS, CSS positioning, and SQL. The common thread is that Nike rewards candidates who can move comfortably between foundational knowledge and applied product thinking. If your experience is real, specific, and easy to unpack, that tends to land better here than generic technical fluency.
Synthetized from 3 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Nike process.
I went through a fairly complete interview loop at Nike, but it felt a lot more compact than the usual drawn-out process. It started with HR, then I spoke with a technical lead and a few peers, and finished with a manager conversation. What stood out right away was that they didn’t do live coding; instead, the technical challenge was on a whiteboard, which made the whole thing feel more discussion-based than execution-heavy. The main technical question I got was about the architectures I had used before, so they were clearly trying to understand my hands-on experience and how I think about system design rather than just whether I could grind through an algorithm under pressure.
The rest of the interview was pretty straightforward and centered on my current work. I was asked to walk through what I do day to day and what I know about CI/CD, so it was important to be able to explain my projects clearly and speak comfortably about deployment and delivery practices. The managerial portion also touched on company policies and client-related situations, including how I would handle a client escalation, which made that round feel more practical than behavioral in the abstract. Overall, the process was not especially technical in the classic coding-interview sense, but it did require solid communication and enough depth to discuss architecture, project experience, and operational judgment. I ended up not getting an offer, and the main takeaway for me was to prepare for whiteboard-style architecture discussion and be ready to talk through real examples from past work, especially around CI/CD and handling difficult client situations.
Prep tip from this candidate
Be ready for a whiteboard architecture discussion instead of live coding, and practice explaining the architectures you’ve used in past projects. Also prepare a clear example of how you’d handle a client escalation, since that came up in the managerial round.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Nike
Calculate the 3-day rolling average of steps for each user.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Customer Orders | |
| Random SQL Sample | |
| Monthly Customer Report | |
| Delivery Estimate Model | |
| Average Order Value | |
| Hurdles In Data Projects | |
| Total Spent on Products | |
| Cumulative Sales Since Last Restocking | |
| Valid Anagram | |
| Black Friday Shopping Spree | |
| Max Quantity | |
| Total Transactions | |
| Common Prefix | |
| Monthly Product Sales | |
| Sharding vs Partitioning | |
| String Palindromes | |
| Why Do You Want to Work With Us | |
| Sales Leaderboard | |
| Find Mismatched Words | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| Client Solution Pushback | |
| Simple Explanations | |
| Presentations and Insights | |
| Weighted Average Sales | |
| Statistically Significant Test | |
| Delivery Online | |
| Slow OLAP Aggregations |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates first complete an online assessment before moving to live interviews. The assessment appears to screen for basic technical fundamentals and readiness for the role.
The process often begins with HR or recruiter contact. This stage is used to review the candidate’s background and set up the rest of the loop.
Candidates then meet with a technical lead and sometimes peers for one or more technical rounds. These interviews are often whiteboard-based and focus on resume deep-dives, architecture discussion, CI/CD, Node.js, JavaScript, TypeScript, React, AWS, and a few coding or DSA questions.
At least one round can be more design-oriented, such as discussing how to build a UI like an Excel sheet or how copying rows and columns should work. The emphasis is on practical implementation thinking rather than live coding.
The final conversation is typically with a manager or director and is described as more casual. It may cover company policies, client escalation scenarios, and broader judgment around how the candidate would handle real workplace situations.
In some cases, the final stage is a panel interview with multiple interviewers. This round can include foundational questions on networking, Git, front-end basics, and SQL, especially for candidates interviewing in Shanghai.