nike logo
Nike· SDE-2

SDE-2 Nike Experience

Experience
3.8 years
Posted
15 Mar 2026
313 reads

Summary

I recently interviewed with Nike for an SDE-2 role and received an offer after a 4-week process that included technical, system design, and techno-managerial rounds. Despite the CTC being slightly lower than my expectations, I accepted the offer for the brand value.

How it went

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
  • CI/CD related questions

Round 3 – 1 hr (Techno-Managerial Round)

  • First 30 minutes: Resume deep dive
    • Focus on how I implemented things and possible alternative approaches
    • API design for a high-scale system
  • Next 30 minutes: Managerial and behavioral questions

Round 4 – 30 mins (HR Round)

This was mainly around:

  • CTC discussion
  • Company expectations
  • Why Nike?
  • Why I want to change my current company
  • General HR discussion

Final Verdict: Selected

I have accepted the offer. Although the CTC was slightly lower than my expectations, Nike is a strong brand to have on the resume for future opportunities, so overall I’m happy with the decision.

Questions asked (4)

  1. 01

    Authentication Concepts and Comparison

    Other

    Discuss basic Node.js concepts and authentication-related questions, specifically comparing OAuth 1.0 vs OAuth 2.0 vs OIDC.

  2. 02

    Longest Consecutive Sequence (Variation)

    Data Structures & Algorithms

    A variation of the Longest Consecutive Sequence DSA problem.

  3. 03

    Design a Cloud File Storage System with Sync

    System Design · Hard

    Design a cloud file storage system with a sync feature.

  4. 04

    API Design for a High-Scale System

    System Design

    Discuss API design considerations for a high-scale system.

How they prepared

Tip: Give real-life examples in the managerial round. Even if they’re slightly simplified, make sure they sound realistic and structured.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Nike recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!