Ebay Software Engineer candidates report recruiter or manager conversations, coding and debugging exercises, system design, and behavioral interviews. Prepare to explain tradeoffs, clarify ambiguous prompts, and communicate your reasoning aloud.
$145K
Avg. Base Comp
$247K
Avg. Total Comp
4-7 rounds
Typical Rounds
2 weeks
Process Length
Ebay Software Engineer interviews in these reports often start with a recruiter or hiring-manager conversation before technical evaluation. Early discussions can cover background, projects, API work, and role fit. One candidate encountered situational questions rather than coding in a manager conversation, so prepare clear examples of decisions, collaboration, setbacks, and project ownership alongside your technical experience.
Technical formats vary by team. Candidates describe standard data-structures-and-algorithms problem solving, including graph questions and several-round coding loops. Others worked in an existing codebase, debugging issues, completing missing functions, or writing tests. Practice reading unfamiliar code, stating the bug or requirement you identify, proposing a safe fix, and explaining complexity and tradeoffs as you work. CodeSignal appears in several reports, but it is not universal, and one candidate encountered a platform problem that prevented code execution.
System design is also reported as either a dedicated interview or a discussion within a wider loop. Establish scope early, confirm assumptions, and restate the design if requirements change. Later interviews may combine coding, design, and behavioral evaluation, so connect technical choices to user impact and teamwork. The supplied reports support four- or five-stage structures, but the exact sequence varies by role and team, and a reliable end-to-end duration was not reported.
Synthesized from 16 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ebay process.
Phone screening, 30 min hiring manager interview, and then panel interviews of three one hour sessions. Coding problem solving data structures, system design, and then team fit/culture. They use CodeSignal for technical rounds.
Questions asked: The hiring manager was interested in a lot of my API work. For the technical interview i was given a code base and had to debug, fix missing functions, and write tests.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ebay
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Rolling Bank Transactions | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Longest Streak Users | |
| Hurdles In Data Projects | |
| Target Indices | |
| Matrix Rotation | |
| Walking Robot | |
| Max Width | |
| The Longest Journey | |
| Seller Type Modeling | |
| String Palindromes | |
| Listing Bookings Aggregation | |
| Impossibly Iterative Fibonacci | |
| Azure Kubernetes Infrastructure | |
| Relational Migration | |
| Decreasing Tech Debt | |
| Processing Large CSV | |
| LRU Cache 1 | |
| Fast Food Database | |
| Statistically Significant Test | |
| Scaling Up Recommender | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Reported early conversations cover candidate background, recent projects, API work, and role expectations. A hiring-manager interview may also use situational questions instead of coding, so prepare concise examples of project ownership, collaboration, difficult work situations, and decisions you made.
Candidates report data-structures-and-algorithms problems, including graph work and two-question sessions, as well as debugging in CodeSignal or an existing application. Be ready to inspect code, identify likely defects, complete missing functionality, write tests when asked, and explain your reasoning, complexity, and tradeoffs aloud.
System design appears as a dedicated round in several reports and as a discussion in others. Clarify functional scope before proposing an architecture, state assumptions explicitly, and revisit them if the interviewer changes direction. Connect components and data flow to the constraints you have confirmed.
Later-stage loops can include several interviews spanning coding, system design, behavioral questions, and team fit. Candidates describe panels with multiple one-hour sessions, though the composition varies. Use specific project examples to show how you communicate, handle ambiguity, and justify technical choices.
