Candidates report eBay software engineer loops that mix CodeSignal screens, DSA rounds, debugging or live app exercises, system design and hiring-manager conversations. Here is what they describe and how to prepare.
$146K
Avg. Base Comp
$197K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe eBay software engineer interviews as a mix of timed coding, practical code work and conversation, and the format varies by team and level. Some report a CodeSignal-style assessment or technical screen early on. One mobile candidate described a 70-minute CodeSignal test with four LeetCode-style questions, ranging from easy to hard and leaning on hashmaps and sliding-window thinking. An internship candidate had a similar online assessment with one easy and two medium-hard problems.
Later rounds often lean practical. Reports include debugging a simple test iOS app, modifying a to-do app live during an onsite, and finishing an Android project sent about an hour before the call. Others describe standard DSA rounds, including two problems in an hour, a DFS/BFS problem and longest substring without repeating characters. Java and Spring topics came up in a backend-focused loop. That loop covered Java 17 features, Spring versus Spring Boot, API layering, dependency injection, exception handling and environment profiles.
System design appears in some loops. One candidate described backend-leaning design coming up more than once in a five-interview virtual onsite, and another described a discussion-style round. Behavioral questions covered conflict, past challenges, why eBay and managing risk with a team. Most reports here ended without an offer, and several mention scheduling delays or disorganization. Confirm with your recruiter what each round covers, and keep practicing your explanations aloud.
Synthesized from 32 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.
Process: Recruiter screen (30 min): background, role fit, and logistics. Technical screen (60 min, Zoom, CodeSignal live IDE): a backend debug and refactor exercise in Java. I was given existing code and asked to find bugs, point out missing tests and documentation, and refactor for reliability, performance, and maintainability. I passed this round. Final loop (three 60-minute Zoom rounds, same day, no AI allowed): Coding and Problem Solving (CodeSignal, Java required): Two easy to medium questions. The first was a number manipulation problem where the main edge case was overflow. Some of the interviewer’s test cases didn’t match the expected output, which used up a lot of time. I reached the optimal solution with some hints. The second was a string array problem. I explained my approach but ran out of time before implementing it. System Design: A content-heavy, read-heavy system. I split read and write services and focused on caching strategy. In hindsight, I should have explained how the cache gets refreshed or invalidated when content changes. Team Fit: Standard behavioral questions, plus a short logic puzzle.
Tips for others: Expect LeetCode easy to medium questions in Java, and practice edge cases like integer overflow. Interviewers care about clean code and talking through your reasoning. For system design, it was pretty standard. Stay calm if the tools or test cases act up.
Questions asked: Reverse Integer Longest Common Prefix Design a content management system (CMS)
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 typically report an initial recruiter call about their background and expectations. Some describe it as relaxed, and one Android candidate's first call also included the hiring manager. Ask which rounds to expect.
Several candidates report CodeSignal-style assessments with multiple timed problems, while others moved straight to a live technical screen. One mobile candidate also mentioned a debugging exercise on a simple iOS app. Practice hashmaps, sliding window, strings and explaining your reasoning aloud.
Some candidates report a hiring manager interview, either as part of the final loop or alongside the first screen. Topics included background, current projects and the languages and libraries you use. Prepare concrete examples of conflict, risk and teamwork.
Candidates report multiple technical rounds. These may include DSA problems such as DFS/BFS or longest substring without repeating characters, code refactoring, or live changes to an existing app. One backend-focused loop probed Java and Spring Boot design. Round counts vary by candidate.
Some candidates report a system design round, described either as backend-leaning or as a discussion. Behavioral topics included conflict, challenges from a previous job and why eBay. Restate assumptions and talk through tradeoffs clearly.
