Wayfair System Design Interview Questions

Wayfair's design section is where candidates who "did LeetCode" still fall down, because it is two design rounds, and the first is the kind almost nobody drills. After the coding rounds, the onsite runs a low-level design (LLD) round and a separate high-level design (HLD) round. The LLD round asks you to design an object model for a concrete product: a parking garage, a bike-rental shop, a ticket or hotel reservation system. You hand over classes with methods and attributes, a normalized database schema, API specs with sample requests and responses, and the SQL queries that answer the requirements. The HLD round is the more familiar scale-and-diagram exercise, on prompts like a Shazam-style song identifier or a multi-provider hotel reservation platform.

That two-round split shapes your prep. Most system-design prep is aimed squarely at the HLD half, and Wayfair candidates who prepare only that way walk into the LLD round with no muscle for it. LLD rewards a different skill. It wants clean class boundaries, a schema in a sensible normal form, and an API you would be willing to ship. It also wants the judgment to extend the model when the interviewer raises the scale. Both rounds run largely on HackerRank's pair-programming portal, and some, like the hotel reservation prompt, involve whiteboarding the design as you talk.

The Wayfair angle

Wayfair is an e-commerce company, and its design rounds are product-shaped. The LLD round in particular is a Wayfair signature. Reports describe designing a parking garage, a bike-rental shop, or a reservation system down to the DB schema and SQL. Then you defend normalization and extensibility when the interviewer pushes on scale. That is a data-modeling and API-design interview wearing a system-design label. It most reliably separates offers from rejects because so few candidates train for it. The HLD round leans on the fundamentals: caching, load balancing, consistency, and observability. If those feel shaky, the free System Design 101 course drills them, and these lessons stay on what makes Wayfair Wayfair.

The two rounds, plus the Karat concept screen

In Wayfair's India offices the full loop puts both an LLD round and an HLD round on the onsite, with senior loops layering deeper follow-ups on scaling, peak cost, and observability. Before the onsite, some screens run through Karat rather than a Wayfair engineer, and the Karat screen front-loads a rapid-fire system-design-concepts block, roughly twenty minutes, before its coding half. US loops are reported as leaner (recruiter, a technical screen, a phone round, then an onsite panel). Treat the two-round design split as the India-documented shape, and confirm your own loop with the recruiter.

• Low-Level Design (LLD): Classes, schema, API, SQL. A concrete product, recurring prompts are an automated parking garage, a bike-rental shop, or a ticket/hotel reservation system. Deliverables are classes with methods and attributes, a normalized DB schema, API specs with sample request and response bodies, and SQL that satisfies the requirements. Follow-ups push on normalization and how the model extends as scale grows.
• High-Level Design (HLD): Scale, data flows, observability. The familiar box-and-arrow round. Recurring prompts are a Shazam-style song identifier, a multi-provider hotel reservation platform, Google Photos with its own blob storage, and a mobile check-in system with analytics. Deep-dives cover scaling to high QPS, cost at peak traffic, and which metrics matter.
• Karat concept screen: ~20 min, rapid-fire, time-boxed. Some screens go through Karat, whose design block quizzes concepts rather than a full design: eventual versus strong consistency, denormalization trade-offs, load-balancing choices, and finding the bottleneck in a staged pipeline. Time does not roll over into the coding half, so finishing early buys you nothing.
• What is scored: Judgment, not buzzwords. In LLD, a clean object model and a schema you can defend. In HLD, a coherent data flow, sane scaling, and naming the metrics that prove the system is healthy. Interviewers push on trade-offs and extensibility rather than counting components.

The prompts that recur

The prompts cluster into a short, recognizable list, and the paid lessons build the recurring ones end to end. For LLD, the anchors are the automated parking garage and the bike-rental shop, with ticket and reservation variants close behind. All are worked the same way: model the classes, normalize the schema, specify the API, write the SQL, then extend for scale. For HLD, the standout is the Shazam-style song identifier, reported across independent loops. Song matching is treated as a black box. The interview lives in the ingestion pipeline, scaling to high QPS, handling weekend traffic peaks with cost in mind, matching trending music, and defining the observability metrics. The multi-provider hotel reservation platform is the other recurring HLD anchor.

There is one more Wayfair-specific artifact worth flagging here even though it is scored as a coding round, not a design round: the coupon / category problem. Coupons apply to nodes in a category hierarchy and cascade to child categories, and the interviewer layers on a validity date, then pushes for O(1) lookups. It shows up so consistently that it reads as Wayfair's house problem, and it lives in the coding section as The Coupon / Category Round. For the design rounds proper, the worked LLD lesson and the Shazam and hotel reservation HLD designs build each prompt with its real requirements and follow-ups.

Common questions

What system design questions does Wayfair ask?

Wayfair splits design into a low-level design round and a high-level design round. The LLD round uses concrete-product prompts: an automated parking garage, a bike-rental shop, or a ticket/hotel reservation system. It asks for classes, a normalized database schema, API specs with sample requests and responses, and SQL queries. The HLD round uses prompts like a Shazam-style song identifier, a multi-provider hotel reservation platform, Google Photos with its own blob storage, and a mobile check-in system with analytics. Its deep-dives cover scaling to high QPS, cost at peak, and observability. A Karat screen adds a rapid-fire concepts block on consistency, denormalization, load balancing, and finding a pipeline's bottleneck.

How many system design rounds does Wayfair have?

In the fully documented (largely India-based) loop, there are two: a low-level design round and a separate high-level design round. They sit alongside the coding rounds, a hiring-manager round, and a culture-fit round, and senior loops add a director round. Some pre-onsite screens run through Karat and include a short system-design-concepts block on top. US loops are reported as leaner, closer to a technical screen plus an onsite panel. Confirm the exact count with your recruiter, and prepare for both a low-level and a high-level design round to be safe.

What is the difference between the LLD and HLD rounds at Wayfair?

The low-level design round is an object-modeling and data-modeling exercise. You design classes with methods and attributes, a normalized relational schema, API endpoints with concrete request and response bodies, and the SQL to satisfy the requirements. Then you extend the model as the interviewer raises the scale. The high-level design round is the familiar architecture exercise: components, data flows, how the system scales to high QPS, how it stays available and consistent, and which metrics you would watch. LLD tests whether you can build a clean, extensible model of one product; HLD tests whether you can scale a system and reason about its trade-offs. Wayfair grades both, so train both.

Is the Wayfair system design interview hard?

It is hard in a way that catches strong algorithm candidates off guard. The HLD round is a standard scale-and-trade-offs interview, demanding but familiar. The LLD round is the one that surprises people: designing a normalized schema, clean class boundaries, and a real API under time pressure is a distinct skill that generic LeetCode practice does not build. The interviewers are reported as collaborative and focused on trade-offs, normalization, and extensibility over trivia. The difficulty is breadth: being ready for both a data-modeling round and a scaling round in the same loop.

How should I prepare for Wayfair system design?

Split your prep to match the two rounds. For LLD, practice turning a product into classes, a normalized schema, an API with sample payloads, and SQL. Use the recurring prompts (parking garage, bike-rental shop, reservation system) as your reps, and rehearse the extensibility follow-up out loud. For HLD, work a scaling-heavy prompt like the Shazam song identifier end to end, including the peak-traffic cost question and the observability metrics. Also drill the Karat concept block: eventual versus strong consistency, when to denormalize, load-balancing choices, and spotting a pipeline bottleneck. Ground the fundamentals in the free System Design 101 course, then work the Wayfair worked designs for the company-specific prompts and follow-ups.