Nordstrom

Large Enterprises

Nordstrom is a leading American luxury department store retailer known for its high-end fashion, apparel, footwear, and accessories, as well as its strong emphasis on customer service. It operates both full-line stores and its off-price Nordstrom Rack chain, alongside a significant e-commerce presence.

4 interview notes · updated Jul 2026

Nordstrom·Software Engineer·Technical Phone Screen

Jun 2026

Nordstrom frontend interview that was basically a React/TypeScript coding session with a lot of follow-up questions layered on top. More conceptual depth than I expected for what sounded like a straightforward UI task.

Using React and TypeScript, build a small UI that supports adding, editing, removing, and filtering a list. Use useState, useCallback, onChange, onClick, and useRef where appropriate, and make sure list items have stable keys.
Explain the difference between controlled and uncontrolled inputs in React, and describe how asynchronous state updates affect your component logic.
How do you properly type event handler parameters in TypeScript when passing them as props in React?
What security concerns are relevant to a UI like this, and how would you address them?
If you had more time, how would you extend this solution and how would you test it?

“The scope sounds manageable until you realize they want you to justify every hook choice as you go.”

View Post

Nordstrom·Software Engineer·Onsite - System Design / Architecture

May 2026

System design interview at Nordstrom for a software engineering role. The whole session was basically one massive design question about a reservation system, but it kept branching into security, scaling, deployment, and general engineering philosophy. More ground to cover than I expected.

Design an online reservation system that supports creating, modifying, and canceling reservations without allowing double-bookings. Walk through your APIs, data model, consistency guarantees, idempotency, and concurrency control.
How would you handle capacity limits, waitlists, and reservation expiration or TTL in this system?
What are the trade-offs between optimistic and pessimistic locking, relational versus NoSQL storage, and centralized versus sharded inventory for this kind of system?
How would you scale this reservation system as traffic grows? Think about partitioning, caching, queues, rate limiting, backpressure, monitoring, and failure recovery.
What are the key security and privacy concerns for a reservation system and how would you mitigate them?
Which deployment strategy would you choose for this system, blue/green, canary, or rolling, and why?
When designing features or services in general, what principles and risks do you prioritize first?

“This was the anchor question and it ate up most of the time.”

View Post

Nordstrom·Software Engineer·Technical Phone Screen

Apr 2026

Went through a coding-focused round at Nordstrom where the main theme was showing your full thought process, not just getting to a working solution. They cared a lot about how you handle the messy real-world stuff around the code, not just the algorithm itself.

Walk through your full approach to a medium-difficulty coding problem: what edge cases do you consider, how do you choose your initial algorithm, and how do you analyze time and space complexity?
After getting a working solution, how would you improve it? What trade-offs are you making between your initial approach and a more optimized one?
How do you handle invalid or unexpected inputs in production code? What does good input validation actually look like end to end?
What test cases would you write to cover corner scenarios for this problem?

“This is where I spent most of my energy.”

View Post

Nordstrom·Software Engineer·Technical Phone Screen

Apr 2026

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.

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.

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

View Post