Ebay Business Analyst interview typically runs 3 rounds: recruiter screen, hiring manager, final panel. It usually takes about 2-4 weeks and can feel inconsistent with role expectations.
$169K
Avg. Base Comp
$220K
Avg. Total Comp
3-5
Typical Rounds
3-5 weeks
Process Length
Our candidates report that eBay’s Business Analyst loop can look straightforward on paper, but the real filter is whether you can operate like a translator between business needs and technical delivery. In one experience, the hiring manager conversation quickly shifted away from classic BA work and toward working with engineers, Salesforce architects, and user stories. That’s a strong signal that the team may value solution design and implementation fluency as much as, or more than, traditional requirements gathering.
A recurring theme is misalignment between the posted title and the day-to-day expectations. The candidate described the role as feeling closer to a solutions architect function, and that mismatch mattered more than any single question. We’ve seen that eBay can probe across a wide surface area for this role — marketplace problem-solving, analytics, SQL, stakeholder management, and even basic experimentation concepts like p-values and power. The non-obvious takeaway is that they seem to care less about polished BA jargon and more about whether you can connect business context to technical execution without losing the thread.
What makes or breaks candidates here is often not one perfect answer, but whether they can show they understand the operating model behind the role. If the team is Salesforce-heavy, expect them to test for comfort in technical conversations and cross-functional delivery. Our candidates report that clarifying scope early is essential, because eBay appears to reward people who can adapt to the actual team need rather than the title alone.
Synthetized from 1 candidates 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.
The process started normally enough with a recruiter screen, then moved into a hiring manager conversation, and after that I was told to expect a final panel with four separate 45-minute interviews. What stood out most to me was that the actual hiring manager round felt pretty off from the job description. The interviewer was a Program Manager who seemed unprepared from the start — he missed the first scheduled interview, showed up late to the rescheduled one, and even spent part of the Zoom call looking up my LinkedIn because he couldn’t find me right away. That already made the round feel disorganized, but the bigger issue was that the role turned out to be much more like a solutions architect position than a business analyst role. He was looking for someone who could work closely with Salesforce architects and engineers, which was not what the posting had suggested.
The main question I got was about my experience working with engineers and writing user stories, so the conversation was very focused on cross-functional delivery rather than classic BA work. Based on the broader process, I was also expecting the later panel to cover SQL, business case scenarios, analytics, marketplace problem-solving, and behavioral questions around stakeholder management, which is a pretty wide spread for a BA interview. Overall, the process felt inconsistent and a bit unfair because the expectations were not aligned with the advertised title. I didn’t move forward, and my main takeaway is to clarify early whether the team wants a true business analyst or someone with more technical solutioning experience, especially if Salesforce is involved.
Prep tip from this candidate
Be ready to explain how you work with engineers and translate requirements into user stories, and clarify whether the team expects Salesforce solution-architect style work. If you get to the panel, expect SQL plus business-case and stakeholder-management questions, not just BA fundamentals.
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.
| Question | |
|---|---|
| P-value to a Layman | |
| Google Maps Improvement | |
| Target Indices | |
| Testing Price Increase | |
| Walking Robot | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| A/B Test Power Size | |
| Marketing Dollar Efficiency | |
| Statistically Significant Test | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Customer Orders | |
| 500 Cards | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Jars and Coins | |
| Comments Histogram | |
| Bagging vs Boosting | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Subscription Overlap | |
| Month Over Month | |
| Paired Products | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Average Quantity | |
| Longest Streak Users | |
| Fair Coin |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with a recruiter to review your background, interest in the Business Analyst role, and basic fit for the team. This is typically the first step before moving on to interviews with the hiring team.
A conversation with the hiring manager or a program manager acting in that role to discuss your experience working with engineers, writing user stories, and supporting cross-functional delivery. In this case, the discussion felt more aligned with a solutions-architect style profile than a traditional business analyst role.
A final panel was expected with four separate 45-minute interviews. The panel was described as likely covering SQL, business case scenarios, analytics, marketplace problem-solving, and behavioral questions around stakeholder management.