i have a frontend SWE interview at eBay coming up in about 3 weeks, applying for their buyer experience team.
can anyone who's interviewed there in the last 6 months drop what the loop actually looked like? specifically curious about: how much JavaScript/DOM stuff vs. general algorithms? do they care about React specifically or is it more framework-agnostic? how brutal is the system design round for frontend?
dm or just reply here. trying to prep smart, not just grind leetcode for 3 weeks straight.
4 replies
mobile_mara
not frontend but i interviewed for a mobile role there in the spring. they were surprisingly framework-agnostic for mobile, cared more about fundamentals than "do you know SwiftUI vs UIKit perfectly." wouldn't be surprised if it's similar on frontend.
pivot_pat
i did a frontend screen at eBay about 4 months ago. the phone screen was a vanilla JS exercise, no framework at all. they had me implement a simple event emitter from scratch. general algorithms were medium difficulty but not the focus. system design for frontend was about component architecture and state management at scale, not distributed systems. way more approachable than i expected.
frontend_fran
this is exactly what i needed, thank you. event emitter is a classic, should've been practicing that already.
growth_gabe
the buyer experience team is pretty product-focused from what i know. wouldn't be surprised if the behavioral rounds lean into experimentation and a/b testing instincts, even for an SWE role. their buyer funnel is where a lot of their growth levers live.