Nike Data Engineer Interview Guide

Our candidates report that Nike cares less about surface-level data engineering buzzwords and more about whether you can justify the mechanics behind your choices. The strongest signal in the experience we saw was the amount of time spent defending SQL decisions: normalization, partitioning, indexing, and query behavior all came up alongside advanced SQL and Spark/ETL work. That tells us the team is looking for engineers who can reason about performance tradeoffs, not just produce a working pipeline.

A recurring theme is that the interview widens beyond the expected platform stack. One candidate was surprised by Python questions on decorators and generators, which suggests Nike wants enough breadth to trust how you think across the stack. We’ve also seen that project discussion matters, but only when it is concrete — the candidate was asked to explain prior work in detail, and the process felt challenging because the conversation kept shifting between theory and implementation. That mix rewards people who can move fluidly from design to code-level detail.

The non-obvious make-or-break factor here is communication under pressure. The same candidate noted a language barrier in the final conversation, which made an already technical discussion harder to navigate. Combined with the standard motivation question about wanting to work at Nike, we’d read this as a process that values clarity, precision, and the ability to stay grounded when the discussion gets dense.