← Nordstrom Interview Insights

Nordstrom·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
Apr 2026

Summary

Nordstrom software engineer screen, basically just the classic 'walk me through your background and a project' opener. Pretty standard stuff, nothing that threw me off.

Questions Asked (1)

Q1

Walk me through your technical background and describe a project you worked on, including the problem, your specific contribution, the approach you took, and the result.

Technical Trade-offsAdaptability & Ambiguity
Author's notes

I'd done this a hundred times but still rambled a bit on the project part.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start with a brief chronological overview of your technical background, then dive into one project using the STAR method (Situation, Task, Action, Result). Emphasize your specific contribution, the technical trade-offs you considered, and how you adapted to ambiguity or changing requirements.

Pro tip: Quantify the impact of your project (e.g., reduced latency by 30%, increased sales by 15%) and explicitly connect your technical decisions to business outcomes, which resonates strongly at a retail-focused company like Nordstrom.

1. Summarize Your Technical Background

Provide a concise overview of your education, key technologies, and roles, highlighting experiences most relevant to the job. Keep it to 1-2 minutes.

2. Describe the Project Context

Explain the problem the project aimed to solve, the team structure, and any constraints or ambiguities you faced. Set the stage for your contribution.

3. Detail Your Specific Contribution

Clearly state your role and the actions you took, focusing on technical decisions, trade-offs, and how you navigated uncertainty. Use 'I' statements to highlight ownership.

4. Explain the Approach and Trade-offs

Walk through your technical approach, including alternatives considered and why you chose your solution. Mention any challenges and how you adapted.

5. Share the Result and Learnings

Quantify the outcome (e.g., performance improvements, cost savings) and reflect on what you learned or would do differently. Connect to the role's requirements.

Key Points to Mention

  • Specific technologies and tools used (e.g., Java, Python, AWS, microservices)
  • Your individual contribution and ownership of tasks
  • Technical trade-offs considered (e.g., scalability vs. simplicity, build vs. buy)
  • How you handled ambiguity or changing requirements
  • Quantifiable results and business impact
  • Lessons learned and how they apply to future work

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.