← Back to Directory

StubHub

Large Enterprises

Screna has 16 StubHub interview write-ups. The most reported round is the technical phone screen (7).

16 interview notes · updated Jun 2026

StubHub·Software Engineer·Hiring Manager Screen

Jun 2026
Standard hiring manager behavioral round at StubHub for a software engineer role. Pretty much what you'd expect: project walkthroughs, classic behavioral questions, and the usual 'why this team' conversation. Nothing too surprising but you need to actually have your stories ready.
  • Walk me through one or two projects from your resume in detail, including the problem, your role, the technical decisions you made, and what the outcome was.
  • Tell me about a project you're most proud of.
  • Describe a time you had a disagreement with a teammate or manager. How did you handle it?
  • Tell me about a time you failed and what you took away from it.
  • How do you handle situations where requirements are unclear or keep changing?
  • How do you prioritize when you're under a tight deadline and have more work than time?
  • Why are you interested in this role and this team specifically?

“This is where you either sink or swim.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineering role at StubHub and got asked about production incident handling. Pretty standard behavioral-technical hybrid question but it caught me more off guard than I expected.
  • Walk me through a time you dealt with an incident in a production environment.

“I had a story ready but fumbled the structure a bit.”

View Post

StubHub·Software Engineer·Onsite - Coding / Algorithms

May 2026
StubHub coding round for a Software Engineer role, centered entirely on building an Event Recommendation System in Java. The core challenge was designing it without hardcoding any logic, which sounds straightforward until you're staring at a blank screen trying to figure out how to make filters composable.
  • Design an Event Recommendation System in Java where different campaign types can reuse and compose filtering behaviors (by distance, price, time, etc.) without hardcoding any conditional logic.
  • How would you support showing users events near them, using either coordinates or city as the location signal?
  • How do you ensure users always get recommendations even when there's limited or missing signal about their preferences?

“This is the whole interview basically.”

View Post

StubHub·Backend Engineer·Technical Phone Screen

May 2026
StubHub backend interview focused on a single design problem: building a filterable event recommendation engine from scratch. Pretty interesting problem for a ticketing company, made sense contextually. The discussion went deep into data structures and composability.
  • Design a simple event recommendation engine where events have a location, date, and price. Implement filter primitives for distance, date/date range, radius, and price range, and support combining them into a single query. Walk through your data structures, how filters compose, and the time complexity of each.

“This took me a minute to fully parse.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
StubHub coding round for a software engineer role, one meaty design-your-own-feature problem that took up the whole session. The problem sounded manageable at first but the efficiency discussion at the end is where things got real.
  • You're extending a MarketingEngine class that holds a collection of events and supports per-customer notification campaigns. Add a campaign that finds the single event whose date is closest to a given customer's next upcoming birthday, handles ties deterministically, and explain how to do this efficiently.

“The core logic wasn't too bad.”

View Post

StubHub·Software Engineer·Hiring Manager Screen

May 2026
60-minute hiring manager screen at StubHub for a full-stack role. The manager made it clear early on that this isn't a heads-down engineering job, you'll be talking to PMs and stakeholders constantly, and he seemed pretty proud of how big their scope is. Questions were all behavioral, nothing technical.
  • Can you walk me through your background and introduce yourself?
  • What's the most impactful project you've worked on recently?
  • What's the most challenging thing you've faced in your work?

“Standard opener.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

May 2026
StubHub interview for a software engineer role, one round that was essentially a design-and-code session disguised as a product problem. The prompt was meaty: build an event recommendation system that's flexible enough for multiple campaign types without hardcoding any logic. Felt more like a senior-level architecture conversation than a typical coding screen.
  • Design and implement an event recommendation system for a ticketing platform where different campaigns can compose behaviors like filtering by distance, price, and time without hardcoding any logic.
  • How would you ensure users always receive some event recommendation even when there's limited signal available about their preferences?
  • Walk through how a new campaign type could be built by combining existing filtering and scoring behaviors without modifying any existing code.

“This is the whole interview basically.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at StubHub for a software engineering role. The main question was a full chat system design with a pretty specific twist around emailing inactive users, which made it more interesting than the usual messaging app prompt.
  • Design an internal chat system for StubHub that supports real-time messaging and sends email notifications to users who haven't logged in for 10 or more days but have unread messages.

“This question has two distinct parts and I spent way too long on the WebSocket layer before the interviewer nudged me toward the email pipeline.”

View Post

StubHub·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round for a software engineer role at StubHub. One question, but it had some real teeth to it.
  • Pick a meaningful past project. If you could rebuild it from scratch, what would you change across architecture, tech choices, process, and team execution, and what did you actually learn that drives each of those changes?

“This question is sneakier than it looks.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

Apr 2026
StubHub system design round focused on a MarketingEngine for event notifications. The open-ended discussion about improving recommendation logic beyond basic rules was the whole thing, no coding, just a long back-and-forth about ML and ranking systems.
  • You've built a MarketingEngine that sends rule-based event notifications to customers (notify when an event is in their city, closest to their birthday, or the 5 geographically nearest). How would you improve the recommendation logic beyond these simple rules?

“This question sprawled in ways I wasn't fully ready for.”

View Post