Wayfair · Primly Community

Wayfair coding interview and online assessment format and difficulty, 2026

backend_bekah · 5 replies

Did the Wayfair SWE loop earlier this year, writing this up because the OA format was different from what I'd seen described in older posts.

The OA (online assessment). Two coding problems on HackerRank, 90 minutes total. When I did it in January 2026 it was unproctored. Problems were: One graph/BFS problem (medium difficulty, standard stuff) One string/simulation problem (also medium, a bit tricky with the edge cases)

Neither was a LeetCode Hard. I prepped mostly LC medium and that was sufficient. The OA is pass/fail; the recruiter told me they look at correctness and time complexity, not time used.

The coding rounds in the onsite. There are two of these in the full loop. Format is 45 minutes each on CoderPad, live with an interviewer.

My two rounds: First: a tree traversal problem that escalated into a follow-up about handling a very large tree that doesn't fit in memory. So it's not just solve the problem, it's also think about the production constraints. Second: a design-ish coding problem. They gave me a schema and asked me to write the data access layer for part of a catalog service. More like a simplified OOP design than pure algorithms.

Difficulty overall. Honestly medium. Not LC Hard. If you're prepped on trees, graphs, hash maps, and can explain complexity clearly, you're in good shape. The bigger signal they're looking for is communication: narrate what you're doing, flag tradeoffs, ask clarifying questions before diving in.

One thing that caught me off guard. The interviewer asked: "if this code was going to production tomorrow, what would you add?" Classic but I wasn't warmed up for it in a coding round. Talked about input validation, error handling, logging, monitoring. That seemed to be the right category of answer.

Total process from OA to offer was about 5 weeks. Seems pretty consistent with what others have posted.

5 replies

jordan_pm

The "what would you add before production" question is one of those deceptively simple things. Did they want a specific answer or just want to see that you think about production concerns at all?

quietquit_quincy

Mostly the latter I think. The interviewer nodded at everything I listed. I don't think there was a magic specific answer. It's more of a "are you just a leetcode machine or do you think about code in context" check.

pivot_pat

Good to know the OA is still HackerRank and not some proprietary platform. I've bombed on Codility before just because the IDE is so bad, HackerRank is at least tolerable.

ops_omar

For what it's worth from the other side: companies at Wayfair's scale that use two coding rounds plus an OA are usually actually reading all three. Some places treat the OA as checkbox and only look at onsite. Wayfair is not one of those, at least not on the teams I know about. Do the OA seriously.

qa_quinn

Curious if there was any testing angle in the onsite or if it was pure implementation. I've heard some companies have started baking basic test-writing into coding rounds.