Candidate reports on Nike software engineer interviews show resume deep dives, whiteboard discussion, Node.js, React, Java and SQL fundamentals, system design, and behavioral or culture questions. Formats vary by team and location.
$140K
Avg. Base Comp
$170K
Avg. Total Comp
2-4 rounds
Typical Rounds
3-8 weeks
Process Length
Candidates describe Nike software engineer interviews as varied, so prepare for the stack on your own resume before anything else. One Bangalore candidate said interviewers spent much of a 45-50 minute whiteboard round on the resume and job description, asking about Node.js, JavaScript and TypeScript. Later questions included reversing letters in strings without built-in methods and building a React timer.
The technical bar looks different by level. A Graduate Engineer Trainee reported SQL, OOP and Java fundamentals across two technical rounds, then an HR round, and received an offer. A Shanghai candidate reported very basic questions on HTTPS ports, Git branching, CSS positioning and SQL experience. A senior candidate reported a key-value cache design and word-frequency problem, plus conceptual questions on how they would resolve technical problems the team was facing.
Behavioral and culture questions also appear. An intern reported teamwork, conflict resolution and Nike values questions across two Zoom interviews, and an SDE-2 candidate reported a client-escalation question in the managerial round. Several candidates also reported no offer, and one described HR going silent after positive feedback, so keep other options open and follow up on status. Only one report here covered a given level, so treat the level-specific details as individual accounts.
Synthesized from 7 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.
Round 1 – 1 hr Basic Node.js concepts Authentication-related questions (e.g., OAuth 1.0 vs OAuth 2.0 vs OIDC) Project-related discussion (why I selected a certain strategy and the trade-offs involved) DSA question: A variation of Longest Consecutive Sequence (I was able to answer it quickly, so pseudocode explanation was sufficient for the interviewer) One small design question related to my project Round 2 – 1 hr (System Design Round) Design a cloud file storage system with a sync feature
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.
Candidates report different entry points. An intern described an untimed HireVue coding question at LeetCode-easy level, and a Shanghai candidate passed an online assessment first. An SDE-2 candidate began with HR. Expect some form of screen, though the format may vary by role and location.
Candidates report technical rounds that probe the resume and job description closely. Topics mentioned include Node.js, JavaScript, TypeScript, React, AWS, Java, OOP, SQL, Git and CSS basics. Some of these were whiteboard discussions rather than live laptop coding. Be ready to explain every technology you list.
Reported coding tasks were fairly approachable: JavaScript string and array manipulation without built-ins, a React timer, and unique-word counting. A senior candidate also reported designing an in-memory key-value cache. Explaining your reasoning aloud seems to matter as much as the answer.
Some candidates reported architecture discussion instead of algorithm-heavy rounds. One was asked about architectures used before and CI/CD. A Bangalore candidate described designing an Excel-like UI with row and column copying, plus Node.js and AWS questions. This round may depend on seniority and team.
Final conversations were reported as more conversational. Candidates mentioned client escalation, company policies, teamwork, conflict resolution, career goals and Nike values or culture fit. One candidate met a director in a casual final round. Outcomes and communication after this stage varied across reports.
