Ebay Software Engineer candidates report recruiter and hiring-manager conversations, technical debugging or coding, and behavioral discussion. Prepare to explain decisions, diagnose existing code, and write targeted tests.
$157K
Avg. Base Comp
$243K
Avg. Total Comp
3-6 rounds
Typical Rounds
2 weeks
Process Length
Ebay Software Engineer interviews in the available reports vary by candidate and level, but several accounts describe a mix of recruiter or hiring-manager conversations, technical evaluation, and behavioral discussion. One recent candidate completed four rounds: a recruiter screen, a hiring-manager discussion of prior projects, a scenario requiring live reasoning, and a final conversation about teamwork, conflict, and pressure. Other Software Engineer candidates also describe coding, system-design, and team-fit components, so the exact sequence may differ.
The clearest technical signal is working effectively in an existing codebase rather than starting from a blank editor. A candidate was asked to reproduce an API bug involving duplicate records under combined filters, identify its cause, implement a fix, and add regression and edge-case coverage. The same report included unit tests for empty input, missing fields, and invalid values, plus discussion of production-only debugging and behavior-preserving refactoring. Practice narrating how you narrow a defect, what assumptions you need to validate, and why each test protects the change.
Coding-focused reports also describe DSA rounds, while another candidate encountered a system-design discussion. Prepare concise explanations of your project decisions for the manager conversation, then shift to structured problem solving in technical rounds. Evidence on one exact standard process is limited, so confirm the scheduled format with your recruiter.
Synthesized from 17 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 | |
| Inherited Model Evaluation | |
| 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 | |
| Top Three Salaries | |
| Closest SAT Scores |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation focused on background, experience, and interest in the role. Use it to give a clear account of your recent work and ask how the remaining evaluation is structured.
One candidate reported a hiring-manager round with deeper discussion of projects, decisions, and lessons learned; another reported situational questions at this stage. Prepare concrete examples of ownership, conflict, and work under pressure.
A candidate reported debugging an existing repository: reproducing duplicate API records under combined filters, explaining the cause, fixing it, and adding regression and edge-case tests. Be ready to reason aloud before changing unfamiliar code.
Other Software Engineer candidates report DSA coding and system-design discussions. Typically, explain your data-structure choice, complexity, assumptions, and trade-offs as you work; the specific problem format may vary.
One four-round account ended with a conversational discussion of teamwork, conflict, and handling pressure. Structure answers around a concrete situation, your actions, and the result rather than relying on general statements.
