← Back to Directory

StubHub interview notes, page 1 of 3

Large Enterprises

Most of these StubHub write-ups come from Software Engineers (20), then Backend Engineers (1). The most reported rounds are the system design round (9), the technical phone screen (9), the onsite coding round (2) and the hiring manager screen (1).

21 interview notes · updated Jul 2026

StubHub·Software Engineer·Onsite - System Design / Architecture

Apr 2026
StubHub software engineer interview with a retrospective design question that pushed me to think critically about past decisions. Not a typical coding round, more of an open-ended architecture and process conversation.
  • Pick a project you've worked on and walk through how you'd rebuild it from scratch. What would you change across the architecture, tech stack, process, and how the team worked together, and what specifically did you learn that led you to each of those changes?

“This one took me a second to settle into.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at StubHub for a software engineering role. The whole thing was one big design question about building a marketing email platform at scale, which sounds straightforward until you're actually in it trying to juggle time zones, A/B testing, and tracking all at once.
  • Design a large-scale marketing email system that supports per-user time zone scheduling, A/B testing, and end-to-end delivery tracking.
  • How would you handle sending 2-3 emails per user within a 15-minute window without hammering the email provider or creating huge send bursts?
  • How would you design the tracking pipeline to capture sent, delivered, opened, and clicked events, and then attribute them to conversions like purchases or signups?

“This question has a lot of surface area and I didn't pace myself well.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

Apr 2026
StubHub system design round focused on a MarketingEngine I'd supposedly already built, then pivoted into an open-ended discussion about how to make the recommendation logic smarter. The open discussion portion was way more involved than I expected.
  • You've built a MarketingEngine with rule-based event notification campaigns. How would you improve the recommendation logic beyond simple rules like city matching, birthday proximity, and nearest events?

“This is the kind of question where you can ramble forever and still feel like you said nothing useful.”

View Post

StubHub·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
StubHub coding round for a Software Engineer role. The whole thing was a design exercise around an Event Recommendation System, and the main constraint was no hardcoded logic. Interesting problem but it pushed you to think in composable patterns pretty fast.
  • Design an Event Recommendation System that supports composable filtering behaviors (by distance, price, time, etc.) across different campaign types, without hardcoding any conditional logic.
  • How would you ensure users always receive event recommendations even when there's limited signal or data available about them?

“They gave you starter code with Event, Customer, Inventory, and Coordinates classes plus a few services, and the whole point was to not reach for if-else chains.”

View Post

StubHub·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
StubHub coding round for a Software Engineer role, 60 minutes, OOD problem centered around a strategy-based event recommendation engine. The interviewer was a British guy and I noticed all my interviewers across the process had been European/white, which stuck with me a bit. Problem itself was pretty well-scoped and I knew the pattern from grinding forums beforehand.
  • Design a Strategy Recommending Engine for a ticketing platform that selects relevant events for users and sends them emails. Start with simple filtering rules (same city, price under $50) and extend to support multiple composable strategies.

“Knew this one from a forum post so I wasn't starting from zero.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
StubHub software engineer interview with a design-focused coding question. Pretty much one meaty problem about building a notification system, and the real conversation was about the data structure choices underneath it.
  • Design a MarketingEngine class with a method that notifies a given customer of all events happening in their city. Walk through the domain models, your choice of internal data structure, and the complexity of each customer query.

“I went straight for a city-to-events dictionary built at init time, which felt right.”

View Post

StubHub·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at StubHub for a software engineer role. The main problem was designing a chat system from scratch, and it had more moving parts than I expected going in.
  • Design an internal chat system for StubHub that supports real-time 1:1 messaging, optional group chat, message history, and an email notification pipeline for users who haven't logged in for 10 or more days but have unread messages.

“This one sprawled fast.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
StubHub software engineer interview, one question deep into technical project work. The prompt was laser-focused on engineering substance, no fluff allowed.
  • Walk me through the most technically challenging project you've worked on. Focus specifically on the coding-level problems, why they were hard, the architectural or algorithmic decisions you made, and how you implemented and validated your solution.

“They cut me off pretty fast when I started drifting toward team coordination stuff.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at StubHub. Single behavioral/technical question about production incidents. Pretty standard stuff but it got specific fast.
  • Walk me through a time you dealt with an incident in a production environment.

“I went straight into a war story about an outage we had, talked through how we diagnosed it and what we rolled back.”

View Post

StubHub·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineer role at StubHub, one round focused on digging into past technical work. Pretty standard behavioral-technical hybrid but the depth they wanted on the complexity side caught me a bit off guard.
  • Walk me through a technically complex problem you've worked on in a previous role.

“I picked a distributed caching issue I'd dealt with before, but I kind of rambled through the setup and didn't get to the actual tricky part until they nudged me.”

View Post