Interview practice plan

N

Lead Software Engineer, ITC

Nike

EngineeringLead / Manager12 practice questions

Practice content written by LYDJ for interview preparation. These are common questions for this kind of role, not this employer's actual interview questions.

What this role asks for

The description doesn't name specific tools, so this plan focuses on the engineering function and behavioural rounds.

Sign in to see your gap areas first. We compare this role with the skills on your profile.

0 of 12 questions practised

Answer each one out loud, then tick it. Progress is saved in this browser only.

01Fundamentals0/2

Core programming

Engineering loops usually include a coding round. Practise talking through your approach before writing code.

  • How would you find and fix a memory leak in a long-running service?

    What good looks like

    Confirm with memory metrics over time, take and compare heap snapshots, look for unbounded caches, listeners and global collections, then add a regression check.

  • What makes code testable? Show how you would refactor a function to make it easier to test.

    What good looks like

    Separate pure logic from I/O, inject dependencies instead of constructing them inside, and keep functions small with clear inputs and outputs.

02Design round0/3

System design

Lead / Manager engineering roles almost always include a design round. State requirements and rough numbers first, then walk through trade-offs.

  • Design the home feed for a professional networking app.

    What good looks like

    Discuss fan-out on write versus read, very large accounts, ranking, pagination and cache invalidation, and state your trade-offs explicitly.

  • How would you break a monolith into microservices? Where would you start?

    What good looks like

    Start from domain boundaries and the parts that change most, use a strangler approach, plan for shared data and distributed transactions, and invest in observability first.

  • Design a distributed cache. How do you handle node failures and hot keys?

    What good looks like

    Consistent hashing, replication, eviction policy, protection against cache stampedes, and the consistency guarantees callers can actually live with.

03Every loop0/4

Behavioural

Every interview loop has a behavioural round. For lead and manager roles, the focus is on people decisions, prioritisation and leading through change. Use the STAR structure.

  • Describe a piece of feedback that changed how you work.

    What good looks like

    State the feedback, your honest first reaction and the concrete behaviour you changed. Close with evidence that the change stuck.

  • Tell me about a time you influenced an important decision without having formal authority.

    What good looks like

    Cover how you built the case (data, prototypes, allies), handled objections and what changed. Strong answers show patience and shared credit.

  • Tell me about a time a project you owned was at risk of missing its date.

    What good looks like

    Show early detection, honest escalation and the scope, sequencing or resourcing levers you pulled. Avoid stories that end with "we all worked weekends".

  • Why do you want this role, and why now?

    What good looks like

    Connect two or three specific requirements of the role to your experience and to a direction you are deliberately moving in. Generic praise of the company scores poorly.

04Leadership0/3

Leadership

The title marks this as a lead or manager role. Expect questions on hiring, developing people and setting priorities.

  • How do you decide what your team should not work on?

    What good looks like

    Show a prioritisation framework tied to business goals, and how you say no to stakeholders while keeping the relationship intact.

  • How do you balance delivery pressure against technical debt or quality?

    What good looks like

    Give a concrete mechanism (a capacity budget, a debt register, quality gates) and an example where you made the trade-off explicit to stakeholders.

  • Tell me about a time you led a team through a significant change, such as a re-org or new way of working.

    What good looks like

    Explain the why you communicated, how you handled resistance, and how you measured whether the change actually worked.

Company research brief: Nike

From the roles we track on LYDJ, refreshed daily from the official careers page.

19

open roles

9

added in 30 days

14

in Engineering

Retail, Travel & ConsumerGCC

Hiring most for

  • Engineering14
  • Other3
  • Security1
  • Data & AI1

Read before the interview

Questions to ask them

  • ›There are several open Engineering roles at Nike right now. How is the team growing, and where does this role fit?
  • ›What does success look like in this role after six months?
  • ›What is the biggest challenge the team is facing this year?
  • ›What are the next steps in the process, and when should I expect to hear back?

Preparation checklist

0/9 done

Saved in this browser only.

Interview prep: Lead Software Engineer, ITC at Nike | LYDJ