Nike · Primly Community

Nike engineering manager interview loop: what to expect across all rounds

firsttime_mgr · 4 replies

Going to write this out because I couldn't find a detailed Nike EM loop breakdown anywhere before mine, and I spent an embarrassing amount of time searching.

Context: applied for a senior engineering manager role on the Digital Consumer Experience team. Based in Beaverton. I have four years of management experience, manage a team of eight, and came in as a relatively strong candidate on paper. The process took about seven weeks.

Recruiter screen. Pretty standard. They wanted to know team size, how I approach performance management, and whether I was open to Beaverton relocation. (I was.)

Hiring manager call. This was a real conversation, not a checklist. He asked about a specific time I had to make a hard call on a low performer. I think this round is where a lot of candidates drop out without realizing it. They want to see you've actually managed performance, not just had difficult conversations that resolved themselves.

Technical breadth interview. One hour with a senior IC from the team. I expected system design or architecture whiteboarding but it was more of a calibration: can you hold a technical conversation with your engineers, do you understand what makes a good data architecture vs a bad one, do you know how to evaluate a PR without writing the code yourself. I talked about a migration we did from a monolith to microservices and what tradeoffs drove that decision. They weren't checking if I could code; they were checking if I could guide.

Panel behavioral. Three interviewers, maybe 15 minutes each, classic Amazon-style leadership principle questions. Nike doesn't use the LP framework explicitly but the questions felt like close cousins. "Tell me about a time you had competing priorities from different stakeholders" and "describe a time you had to give feedback that changed someone's trajectory." I prepared 8-10 STAR stories and used five of them.

Cross-functional interview. This one surprised me. Thirty minutes with a design director and a product lead. They wanted to know how I run eng-design-PM rituals, how I handle friction between eng and design, and whether I'd shipped something ambiguous successfully.

Bar raiser. Senior director from a different org. Asked about org design, how I think about headcount allocation, and what I look for when hiring senior ICs vs leads. This felt like an executive presence check more than anything.

Base came in at 195k. Total comp offer was around 255k with bonus. RSUs vested over four years. I thought it was fair for Beaverton but probably 10-15% below equivalent at a pure-tech company.

Biggest prep advice: have stories about managing humans, not just delivering projects. The technical stuff mattered less than I expected.

4 replies

sdr_sky

this is a really clean breakdown. the cross-functional panel with design+PM is something i wish i'd been told about going in. most EM preps only cover the technical and behavioral sides, not 'can you work across functions without being the source of friction.'

director_dee

the bar raiser asking about org design and headcount allocation is very typical. they're testing whether you think one level up. if you're an EM who still talks mostly about execution, that round will trip you. you need to be able to zoom out to 'here's how I'd think about building this team over 18 months.'

firsttime_mgr

exactly. and the headcount question caught me slightly off guard because they framed it as 'if you could add two engineers right now, where would you put them and why?' i answered it in terms of team topology and capacity but i'd been expecting something about budget process.

recruiter_rita

seven weeks is on the longer end but not unusual for senior IC/manager roles at consumer brands. they move slower than pure tech shops. if you're actively talking to other companies, be upfront with the nike recruiter -- most will try to accelerate if there's a competing offer.