← Nordstrom Interview Insights

Nordstrom·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
May 2026

Summary

Nordstrom software engineer screen, basically just a technical background walkthrough plus a project deep-dive. Pretty standard opener round, nothing too wild.

Questions Asked (1)

Q1

Walk us through your technical background and describe a project you worked on, including the problem, your specific contribution, the approach you took, and what the outcome was.

Technical Trade-offsAdaptability & Ambiguity
Author's notes

They gave a pretty clear structure for this: years of experience, strongest languages and tools, then one project in detail.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start with a concise overview of your technical background, then dive into one project using the STAR method (Situation, Task, Action, Result). Focus on your specific contribution, the technical decisions you made, and the measurable outcome, while highlighting trade-offs and how you handled ambiguity.

Pro tip: Choose a project that aligns with Nordstrom's focus on scalable, customer-facing systems and emphasize how your technical decisions impacted business metrics or user experience. Quantify results whenever possible to demonstrate impact.

1. Set the Context

Briefly summarize your technical background and the project's context, including the problem and why it mattered to the business or users.

2. Define Your Role

Clearly state your specific role and responsibilities in the project, distinguishing your contributions from the team's.

3. Explain Your Approach

Describe the technical approach you took, including key decisions, trade-offs, and how you navigated ambiguity or constraints.

4. Highlight the Outcome

Share the results of your work, using metrics or concrete outcomes to demonstrate impact, and reflect on what you learned.

Key Points to Mention

  • Specific technologies and tools used, and why you chose them
  • Trade-offs made between different technical solutions (e.g., performance vs. maintainability)
  • How you handled ambiguity or changing requirements
  • Your individual contribution and collaboration with the team
  • Measurable outcomes (e.g., performance improvements, cost savings, user engagement)
  • Lessons learned and how you applied them to future projects

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