Wayfair
5 questions · 4 experiences · 1p3a (5) · LeetCode (1) · Other (3)
9 entries
Wayfair Backend Engineer Interview Experience 2026
Wayfair Technical Assessment Screening Fulltime PM Experience
Wayfair System Design Interview: Bike Rental Shop Service Design
Wayfair Back-End Developer Hackerrank OA Experience
#2380 Time Needed to Rearrange a Binary String
Wayfair Software Engineer Intern Interview
Wayfair online assessment
Wayfair rejected after asking salary slips
Wayfair Machine Learning Engineering Online Assessment Experience
Wayfair Backend Engineer Interview Experience 2026
Question Details
YOE: 3.5 Years Role: Backend Engineer ⸻ 🟢 Round 1: Online Assessment (HackerRank) • Received a HackerRank link. • There were 2 DSA questions (LeetCode Medium–Hard level). • I was able to solve both within the given time. Outcome: Cleared the round. After 2 days, I received a call from the recruiter confirming the next round. There was some delay in scheduling due to slot availability. ⸻ 🔴 Round 2: Machine Coding Round (40 mins) There was a technical issue on my system initially, and the first 10 minutes were spent resolving it. The interview started with some delay. Problem Statement: Given a list of packages with: • Weight • Height • Width • Length • Distance We had to calculate: • Transport Charges • Service Charges • Overall Cargo Cost Charges were based on package type: • Standard Transport: 0.5 × Volume Service: 0.5 × Weight + 0.5 × Distance • Hazardous Transport: 0.75 × Volume Service: 0.75 × Weight + 0.75 × Distance • Fragile Transport: 0.625 × Volume Service: 0.625 × Weight + 0.625 × Distance Volume = Height × Width × Length We were given interfaces for package and shipment, and asked to implement the calculation logic, insert/remove packages, and compute total costs for the cargo. The time limit was 40 minutes. ⸻ My Approach • Started by defining POJOs and basic structure. • Used Strategy Design Pattern to calculate charges based on package type. • Implemented core logic but could not complete the entire solution within the time limit. • Initial delay and spending extra time defining structure affected completion. I felt I could have coded it faster with better time management. ⸻ ❌ Verdict: Rejected ⸻ 📌 Key Learnings • Machine coding rounds require speed + clarity. • Avoid over-engineering; focus on working solution first. • Time management is critical. • Handle unexpected technical issues calmly and adjust quickly.