Your eBay Prep Plan

eBay hires onto a specific team, and the loop that takes you there comes in two shapes by geography. In the US it is usually a virtual onsite of four or five rounds: two or three coding, one system design, one with a hiring manager. In India it opens with a CodeSignal assessment and funnels into a batched hiring-drive weekend at the Bengaluru office, often with a low-level design round added. A CodeSignal online assessment gates most paths. There are two versions of it, and they look nothing alike. Settle which loop and which assessment are yours before you spend an hour, because that answer decides where the hours go.

The eBay angle

The highest-leverage move before you drill anything is pinning down your own loop, and a short exchange with your recruiter does most of it. Ask which CodeSignal assessment you will get. The algorithmic one and the machine-coding one test completely different skills, and eBay sends either. Confirm whether you face a US virtual onsite or an India hiring drive, how many coding rounds to expect, and whether a low-level design round is in the mix. Ask what level you are being assessed at, since that answer moves your later phases and eBay is known to down-level. One more thing surfaces on that call. "Why eBay?" is a staple of it, so walk in with a real answer. Read the interview process and leveling and how decisions get made first, so the pipeline and the team-based reality are clear before you plan around them. If you are interviewing for an internship or a new-grad role, start with the internship and new-grad guide, where the loop is lighter and the assessment carries most of the weight.

The plan, phase by phase

Each phase below carries one focus and a checkpoint that tells you when you have earned the next. A phase is a share of your total prep time, not a fixed number of weeks, so the plan holds whether your runway is two months or one hard week. The proportions are the message. The CodeSignal gate and the broad band of medium DSA take the largest slices. Together they are what eBay filters on hardest, and what a diet of hard puzzles leaves you least ready for. Do not step past a checkpoint until you can clear it cold.

To make the proportions concrete, picture a six-week runway. The first days go to Phase 1 and settling your loop. Weeks one and two belong to the CodeSignal gate: drill it against the clock, and if the machine-coding version is yours, build that stateful object-modeling habit daily. Weeks three and four are the broad DSA band, a few fresh mediums a day across the recurring clusters. Work the autocomplete problem until it runs on reflex. Week five turns to marketplace design, plus the low-level design round if your loop has one. Week six is for behavioral stories, a full mock loop or two, and shoring up whatever felt shakiest. On a tighter runway you compress the same order. You never reorder it. The gate always comes before the onsite.

Why the phases are weighted this way

The weighting tracks where eBay departs from a generic loop. The CodeSignal gate leads because nothing downstream matters until you are through it. The broad DSA band takes the next largest slice, since the onsite rewards range across medium problems more than depth on a few hard ones. Marketplace design sits a notch lower only because it is level-gated, not because it goes easy at SE-3 and above. The machine-coding assessment and the low-level design round draw on one shared skill, so preparing either strengthens both. Behavioral comes last. It is sharpest written late, and a true reason for wanting eBay counts for more than a rehearsed rubric answer.

The eBay angle

The trap is preparing for eBay as if it were a generic algorithm loop. People grind hard puzzles, then meet a CodeSignal assessment that asks for a working banking system across four escalating levels. Or they hit an onsite that prizes breadth and clean tests over a clever one-liner. Spend your hours where eBay actually looks. Build the stateful object-modeling muscle that the machine-coding assessment and the low-level design round both reward. Get the price-drop notification design into your hands until it flows. Those pieces are what turn eBay from a curveball into home ground.

A second front needs preparing. It turns on logistics more than skill.

The eBay angle

Know your geography before the loop begins. In India the process runs through batched hiring-drive weekends at the Bengaluru office. The level is often decided by how the rounds go rather than fixed up front. A slow or silent reply afterward is a widely reported pattern, so line up other options and do not read quiet as a verdict. The US wrinkle is different. A debugging and refactoring round and a face-to-face round about working with AI are rolling out, neither with a tidy format to rehearse. Either way the fix is the same. Confirm what your loop holds up front, and prepare for the level above whenever the level is left open.

In the room

• Confirm which CodeSignal you get, then drill it against a timer. The algorithmic version rewards pace across four ramping tasks; the machine-coding version rewards clean, extensible classes that survive four stacked requirements.
• On the machine-coding build, design for the next level from your first method. One clear home for each piece of state is what lets a new requirement cost a few lines instead of a rewrite.
• In onsite coding, prize clean and tested over optimal. Land about two mediums with working code, unit tests, and a spoken tradeoff, and restate the long story back before you write.
• Treat marketplace design as the home question. Take the price-drop notification system end to end, and reason in real-time delivery, caching, and the tradeoffs of a company on its own infrastructure.
• Bring a real "Why eBay?" and stories for the mission, not a rubric. There is no numbered values list to recite, so anchor to competencies and the mission, and keep a project you can draw and defend.