Wayfair · Primly Community

5 rounds at Wayfair SWE2, offer received. here's the rundown

finance_faye · 4 replies

went through the full Wayfair loop in April, SWE2 level, Boston HQ-aligned but remote role. sharing because I wish I'd had something like this before I started.

round 1: 30-min recruiter screen. nothing spicy, she wanted to know why Wayfair, timeline, TC expectations. I had a number ready and she didn't flinch, which was a good sign.

round 2: online assessment, 2 LC-medium problems, 90 minutes. I hit both but the second one I only got 4/5 test cases and still moved forward, so I don't think it's a hard cutoff.

round 3: technical coding interview. interviewer was solid, very conversational. we worked through a graph traversal problem tied loosely to a warehouse routing scenario. they like context, not pure LeetCode abstraction. narrate.

round 4: system design. I got asked to design a product recommendation service. I started with catalog indexing and search and pivoted to the rec layer. interviewer pushed a lot on how I'd handle cold start and I talked through a hybrid approach. she seemed pleased.

round 5: behavioral. heavy on operating principles. "tell me about a time you made a decision with incomplete data" and "describe a conflict you had with a PM." I had STAR stories prepared and it felt solid.

offer came in ~10 days. team seemed genuinely collaborative, not just interview-theater about it.

4 replies

newgrad_neil

this is incredibly helpful. did they tell you which principles they'd be testing before the behavioral round, or did you just prep all of them?

backend_bekah

no heads up. recruiter said 'behavioral round focused on leadership and collaboration' which is vague as heck. I just prepped 8-9 stories covering ownership, conflict, data-driven decisions, and customer impact. you'll be fine if you have that base.

careerveteran

the warehouse routing framing for a graph problem is very Wayfair. they try to make tech questions feel like real company problems. it sounds gimmicky but it actually filters for people who can think about business context, which matters at e-commerce scale. don't just solve the algo, say what it'd mean in production.

ds_dmitri

I had a similar experience, slightly different track (SDE on a data-adjacent team). system design was product catalog search for me. they asked how I'd handle filtering by hundreds of attributes at scale. went deep on inverted indexes. felt good.