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.
Synthesized from 3 candidate 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.
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 | |
|---|---|
| Relational Migration | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Monthly Customer Report | |
| Customer Orders | |
| Random SQL Sample | |
| Top 3 Users | |
| Over-Budget Projects | |
| Cumulative Distribution | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Delivery Estimate Model | |
| Average Order Value | |
| Normalize Grades | |
| Valid Anagram | |
| Monthly Product Sales | |
| Success Measurement | |
| Cumulative Reset | |
| Black Friday Shopping Spree | |
| Max Quantity | |
| Common Prefix | |
| Loan Model | |
| Seller Type Modeling | |
| Sharding vs Partitioning | |
| String Palindromes | |
| Client Solution Pushback | |
| International e-Commerce Warehouse | |
| Sales Leaderboard |
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.
