Skip to main content

How eBay Interviews in 2026: Process, Questions & What They Score

The complete process, reported questions, and what interviewers score.

eBay / Interview snapshot

8

stages from
application to offer

41

reported questions

27

public sources

Last verifiedOct 2026
HOW TO READ THIS PLAYBOOK

Independent: SupaCV is not affiliated with or endorsed by eBay. This is one well-documented shape of eBay's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.

Medium confidenceSources
On this page

01 / For every eBay candidate

The process, start to finish.

This playbook covers eBay's software engineering track (MTS / Software Engineer levels), the role family with the most public candidate reports. eBay hires for other tracks that are not covered here. eBay's official How We Hire page describes four phases, labeled Apply, Interview, Decision (the section is headed 'How we evaluate') and Offer. Interviews are mostly virtual over Zoom, and candidates will likely meet a recruiter, the hiring manager and potential future teammates.

Engineering roles may include a coding assessment, and some roles add a technical screen, case study or skills-based exercise. eBay expects candidates to keep their camera on, says AI may be used to prepare but not to generate answers during interviews or assessments, and says some interviews are recorded and transcribed with BrightHire (candidates can opt out, and eBay says this does not affect their evaluation).

After the interviews, eBay says it reviews structured, job-related feedback from each interviewer against the role requirements, and some roles use a hiring panel or debrief. Candidate reports and prep guides describe this engineering sequence: a short recruiter screen, a CodeSignal online assessment, a live technical or debugging screen, then a virtual onsite of 3 to 5 rounds covering coding, low-level or system design, and a behavioral round with the hiring manager.

One prep guide counts seven rounds in total, but the order, the number of steps and the format vary by team, level and location. eBay publishes five culture values (its 'DNA') on its careers site, and two prep guides say the behavioral round focuses on eBay's values, but nothing official says interviewers score candidates against them, so this playbook lists no evaluation framework.

The candidate evidence comes from smaller sources (Taro, Blind, Codingkaro) and prep sites rather than Glassdoor, LeetCode Discuss, Indeed, Interview Query, 1Point3Acres or Naukri.

Stage 1:

Application (optional questionnaire or assessment)

varies

Candidates apply through the careers site, a job board, a recruiter or a referral, and in some regions or programs through a partner platform. Some roles add a short questionnaire or assessment at this point. eBay says people make the application decisions and AI only helps organize application information. eBay gives no timeframe for this phase, so how long it takes varies by role.

Stage 2:

Recruiter screen

15 to 30 minutes

Covers background, level, interest in the role, and logistics such as compensation, location and notice period. The duration comes from prep guides (TechPrep says 15 to 30 minutes, CleverPrep's software engineer page says 30 minutes). The official page says only that candidates will likely meet a recruiter. In one 2020-2021 Taro report the recruiter call is listed after the CodeSignal round, so the order varies.

Stage 3:

Online coding assessment (CodeSignal)

60 to 90 minutes, depending on the source and format

TechPrep describes about 90 minutes with 4 progressive coding questions and says a score around 520 of 600 is generally needed to advance; that cutoff is one guide's claim and InterviewFox states no cutoff. InterviewFox describes the standard CodeSignal test as 4 tasks in 70 minutes, plus a project-style version with 4 sequential levels. Codingkaro lists a July 2025 candidate with a 90-minute multi-level banking-app assessment and two October 2025 project-style assessments. CleverPrep's software engineer page says 60 minutes with 2 to 3 problems. A 2020-2021 Software Engineer 3 candidate reported solving 4 LeetCode-style questions. eBay officially says only that engineering roles may include a coding assessment.

Sources disagree on length and format

Stage 4:

Live technical screen (coding or debugging)

45 to 90 minutes

TechPrep calls it a 'Code Jam' of 60 to 90 minutes: you work in a pre-built repository, debug failing code, add missing logic and get tests passing. CleverPrep's software engineer page describes a 45 to 60 minute live coding interview with 1 to 2 algorithmic problems. Blind posters describe a debugging tech screen on CodeSignal and being told 'no leetcode, but finding bugs'. A 2025 Portland MTS-2 candidate had a two-hour video session (one hour of coding on CodeSignal, then one hour of infrastructure design) and did not say where it fell in the loop. A 2020 Blind post refers to a first 45-minute phone interview, and a 2025 Shanghai Software Engineer 3 candidate was told of a 45-minute coding round.

Stage 5:

Hiring manager phone screen (some teams)

varies

One 2025 San Jose Software Engineer report lists an initial phone screen with the hiring manager as the first stage, followed directly by a three-round onsite (system design, coding, behavioral). No other report confirms a separate hiring manager screen, so treat it as a team-specific variant rather than a fixed stage. It may replace the earlier screens instead of following them, and its duration and place in the order vary by team. The official page says only that candidates will likely meet the hiring manager.

Single candidate report; not a fixed stage

Stage 6:

Virtual onsite loop

3 to 5 rounds of about 45 to 60 minutes each

Usually coding (data structures and algorithms), low-level or object-oriented design, system design, and a behavioral round with the hiring manager or a senior lead. TechPrep says 3 to 4 rounds of about 60 minutes. CleverPrep's software engineer page lists four onsite rounds of 45 to 60 minutes (two coding, one system design, one behavioral with the hiring manager). One 2020-2021 Taro report lists 5 rounds of 45 minutes; its process summary names 2 LeetCode-style, 1 system design, 1 OOP and 1 hiring manager round, but its question section lists a front-end round instead of system design, so the page is inconsistent. Codingkaro lists a November 2025 Bangalore Software Engineer III loop with 4 technical rounds plus a director round. Some loops add an API design or code debugging and refactoring round. In a 2021 Blind thread on MTS1, commenters estimated 3 to 4 coding rounds, 1 to 2 design rounds and 1 manager round, and one commenter's team used a solo coding assignment with panel review. The mix depends on team, level and location.

Stage 7:

Decision (evaluation and debrief)

varies

eBay's page, headed 'How we evaluate', says interviewers share structured feedback that is reviewed against the role requirements, and that for some roles a hiring panel or debrief is held to reach a decision. eBay gives no timeframe, says timelines can vary, and says that not having heard back yet does not mean the decision is final. Blind posters reported waiting weeks for feedback after the loop, including one for a January 2026 interview, and another described a recruiter who stopped responding.

Candidates report long or unclear waits after the onsite

Stage 8:

Offer

varies

The recruiter gives a verbal offer before the official offer letter. Compensation, benefits and start dates vary by role and region, notice periods may be longer in some regions, and some roles need background checks or verifications before onboarding. One prep guide (TechPrep) puts the whole pipeline at 2 to 4 weeks, which sits uneasily with the multi-week feedback delays Blind posters report.

Reported interview time, one scale in minutes

Where the minutes go

Virtual onsite loop is drawn as its total: 5 rounds of ~60 min each.

  • Recruiter screen30 min
  • Online coding assessment90 min
  • Live technical screen90 min
  • Virtual onsite loop~300 min in total

Not drawn: Application, Hiring manager phone screen, Decision and Offer, whose durations are not given in minutes.

02 / What eBay scores

No publicly documented framework

03 / Coach's notes

Coach's tips.

  1. 01

    Practice in CodeSignal before the screens. Candidates report that both the online assessment and the live screens run there, and Blind posters describe debugging rounds where they had to find bugs rather than solve LeetCode problems. Reports describe either a standard timed set of four coding tasks or a project-style, multi-level task (a banking-system example), so ask your recruiter which one to expect. Check early that you can run code in the environment, because one candidate could not execute code and had to give the bugs as comments.

  2. 02

    Treat code quality as part of the score. TechPrep says interviewers pay close attention to how you write code, not just whether it works, expects clean, readable code with unit tests, and describes the live screen as working in an existing repository and getting tests passing. Narrate your test cases and keep functions readable.

  3. 03

    Ground design answers in marketplace problems: flash-sale inventory, seller reputation, fraud and counterfeit detection, and recommendations. Be ready to defend SQL vs NoSQL, sharding and CAP choices, as TechPrep advises. TechPrep also suggests thinking through how a bidding system handles last-second bids, and CleverPrep lists a real-time bidding design prompt, but neither ties it to a named candidate.

  4. 04

    Follow eBay's published interview rules. Keep your camera on, use AI to practice or prepare but not to generate answers during interviews or assessments, and expect that the session may be recorded with BrightHire. You can opt out, and eBay says opting out does not affect your evaluation.

  5. 05

    Prepare real examples of how you approach challenges and collaborate with others, and link your work to eBay's mission. The How We Hire page recommends the first and says eBay loves it when candidates connect their work to its mission. Two prep guides add that the hiring manager round touches eBay's values, so review the culture page too, though eBay does not say interviewers score candidates against those values.

  6. 06

    Confirm the loop shape with your recruiter. Reports range from 3 to 5 onsite rounds, sometimes with API design, debugging and refactoring, a director round or a solo coding assignment, depending on team and level. Candidates also report waiting weeks for feedback, so ask for expected timing at each step. eBay says not having heard back does not mean the decision is final, and recommends staying in touch with your recruiter.

04 / The research

Where this page comes from.

Compiled from public sources across 14 sites.

sites
14
coaching and prep guides
21
candidate reports and forums
6

Source composition

Where the research comes from

Grouped by the kind of site that published each source: eBay's own domain, candidate forums, and everything else.

  • Coaching and prep guides21
  • Candidate reports and forums6

05 / The questions

Reported questions, by category.

Showing questions for

Roles are grouped by the category each question fits, not by the source.

Coding

(data structures and algorithms)

12 questions

  1. Number of Islands

    Tests grid DFS or BFS flood fill with visited-cell tracking.

  2. All Nodes Distance K in Binary Tree

    Tests tree traversal with a parent map, then BFS outward from the target node.

  3. 3Sum

    Tests sorting plus two-pointer scanning while skipping duplicate triplets.

  4. Merge Intervals

    Tests sorting by start time and merging overlapping ranges in a single pass.

  5. Reverse Pairs

    Tests counting inversions with merge sort or a Fenwick tree in O(n log n).

  6. Sudoku Solver

    Tests backtracking with row, column and box constraint checks and pruning.

  7. Parse an HTML or XML document into an n-ary tree.

    Tests stack-based tag parsing to build an n-ary tree; wording is paraphrased from the guide.

  8. Implement a recursive file listing.

    Tests recursion over nested directories; wording is paraphrased from the guide.

  9. Expression Add Operators (LeetCode 282)

    Tests backtracking over operator placement, tracking the last operand to handle multiplication precedence.

  10. Return the top K sellers with the highest frequency of transactions within any rolling 60-minute window.

    Tests a sliding time window with a hash map of counts and a heap to extract the top K.

  11. Merge overlapping inventory availability intervals for a product SKU across regional warehouses.

    Tests grouping by SKU, then sort-and-merge of overlapping availability intervals across warehouses.

  12. Find the shortest path between two categories, prioritizing paths that contain only verified sub-categories.

    Tests BFS or Dijkstra on a category graph, with weights or tie-breaks favoring verified sub-categories.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Debugging

1 question

  1. A shipping-cost service that calculates cost from weight and distance fails intermittently under high load. How would you identify the root cause?

    Tests root-cause reasoning for load-dependent failures such as races, timeouts and shared state.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

System and low-level design

11 questions

  1. Design a rate limiter.

    Tests token bucket or sliding window design, per-client state and concurrent access.

  2. Design a notification service.

    Tests queue-based fan-out, retries, idempotency and delivery channels.

  3. Design an online flash sale system that handles real-time inventory updates for high-demand items.

    Tests inventory consistency under contention: locking, atomic decrements and overselling prevention.

  4. Design a Dropbox-like file storage system.

    Tests chunked uploads, metadata storage, sync and conflict resolution at scale.

  5. Design a persistent storage layer for ad clicks.

    Tests high-write ingestion, partitioning, deduplication and storage engine choice for click events.

  6. Design eBay's real-time bidding system that handles millions of concurrent auctions.

    Tests concurrent bid ordering, last-second bid handling and consistency under high write load.

  7. How would you architect a personalized recommendation engine that updates from user clicks in near real time?

    Tests streaming click ingestion, feature updates, candidate retrieval and ranking latency.

  8. Design a recommendation system for eBay that handles cold-start for new users.

    Tests handling new users with popularity priors, content-based signals and exploration.

  9. Design a seller reputation system that is fair and resistant to manipulation.

    Tests score design, abuse resistance such as fake feedback, and fair aggregation of seller signals.

  10. How would you detect counterfeit products being sold on the marketplace?

    Tests combining ML classifiers, seller and listing signals and human review into a detection pipeline.

  11. Design a system to authenticate luxury watches submitted by sellers.

    Tests an authentication workflow covering item intake, expert review, evidence storage and fraud signals.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Every role

Online assessment

(project-style)

2 questions

  1. Build an in-memory database across several incremental levels in a CodeSignal project-style assessment.

    Tests incremental data-structure design where each level adds operations to an in-memory store.

  2. Build a banking system in levels: basic account operations, then top spenders ranking, scheduled payments and account merging.

    Tests incremental object-oriented design where each level adds features without breaking earlier ones.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Every role

Behavioral

7 questions

  1. How do you weigh a quick fix against a cleaner long-term solution when dealing with technical debt?

  2. Tell me about a time you identified a performance bottleneck in a system and fixed it.

  3. Describe a situation where you had to push back on a product feature request because it would have compromised stability or scalability.

  4. Tell me about a technical project where you had to make difficult trade-offs.

  5. Describe a time you innovated on an existing product or process.

  6. Can you give us examples of times where you failed and how you bounced back?

  7. Tell me about a time when you used data to make a decision.

Every role

Motivation and marketplace sense

5 questions

  1. Why eBay over other e-commerce or marketplace companies?

  2. What is one thing you would change about eBay?

  3. How do you see the role of engineering in maintaining trust between independent buyers and sellers?

  4. How would you improve buyer trust and reduce purchase anxiety on eBay?

  5. What issues does eBay face today?

Your next step

Interviewing at eBay?

Make sure your resume gets you to the first round.

Practicing for eBay against your resume is in Interview Prep on Career.

Common questions

Quick answers.

How many stages are in eBay's interview process?

eBay has 8 stages, set out in The process.

Does eBay have an official interview framework?

eBay has no publicly documented framework, as set out in What eBay scores.

What kinds of questions does eBay ask?

eBay's questions fall into 7 categories, grouped in The questions.

How reliable is this eBay interview playbook?

It is compiled from public sources, and the evidence is in The research.

Sources (27)

Every public source this page was compiled from. Links open in a new tab.

14 sites, by sources

  • jointaro.com6
  • teamblind.com4
  • careers.ebayinc.com3
  • techprep.app2
  • cleverprep.com2
  • glassdoor.com2
  • jobmentis.com1
  • climbtheladder.com1
  • hyring.com1
  • interviewfox.ai1
  • codingkaro.in1
  • prepfully.com1
  • aced.io1
  • ambitionbox.com1
  1. 01careers.ebayinc.com/how-we-hire
  2. 02careers.ebayinc.com/brighthire-faqs
  3. 03careers.ebayinc.com/our-culture
  4. 04techprep.app/blog/ebay-interview-process
  5. 05techprep.app/companies/ebay
  6. 06cleverprep.com/companies/ebay
  7. 07cleverprep.com/companies/ebay/software-engineer
  8. 08jobmentis.com/en/interviews/ebay/swe
  9. 09climbtheladder.com/ebay-interview-questions-2
  10. 10hyring.com/jobseeker-toolkit/interview-questions/company/ebay
  11. 11interviewfox.ai/interview-questions/ebay-codesignal-oa-guide
  12. 12codingkaro.in/jobs-internships/leetcode-interview-experience/Ebay
  13. 13jointaro.com/interviews/companies/ebay/experiences/software-enginee…
  14. 14jointaro.com/interviews/companies/ebay/experiences/mts-2-software-e…
  15. 15jointaro.com/interviews/companies/ebay/work-experiences/mts-2-softw…
  16. 16jointaro.com/interviews/companies/ebay/work-experiences/software-en…
  17. 17teamblind.com/company/eBay/posts/ebay interview
  18. 18teamblind.com/post/ebay-on-site-interview-mts1-vn3v3bdo
  19. 19teamblind.com/post/ebay-is-asking-lc-hard-problems-are-you-kidding-m…
  20. 20teamblind.com/post/ebay-virtual-onsite-interview-p2l1d3i7
  21. 21jointaro.com/interviews/companies/ebay/experiences/mts1-software-en…
  22. 22jointaro.com/interviews/companies/ebay/work-experiences/software-en…
  23. 23prepfully.com/answers/ebay-search
  24. 24aced.io/questions
  25. 25glassdoor.com/Interview/eBay-Interview-E7853-RVW1419701.htm
  26. 26glassdoor.com/Interview/eBay-Interview-E7853-RVW96640326.htm
  27. 27ambitionbox.com/interviews/ebay-interview-questions/product-manager