
SeatGeek Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 31 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at SeatGeek.
Software Engineer
I interviewed at SeatGeek in February 2024. After getting a referral, the first stage was an initial phone call with an internal recruiter where they asked generic questions. The second stage was a timed coding challenge. I thought it was a really nice company with high standards. In hindsight, the role was too advanced for me, but it was a good learning experience. I agree with their decision to not move me forward, although it was upsetting. It would have been good if candidates could retake a test if they failed, but I understand why not. I had to follow up after two weeks without hearing any feedback, which was frustrating given the time I invested in the technical test. I might try again in the future.
- Create a banking application using Codesignal tests.
Software Engineer
The entire hiring process moved pretty quickly for me, taking less than a week because I had other offers. It started with a phone call with the VP of R&D, followed by another hour-long technical phone interview. After that, I had a full day of on-site interviews, which lasted about 6 hours. Overall, it's a pretty time-consuming process, so be prepared. What was frustrating is that they informed me they didn't have any suitable offers for me based on my preferences *after* I completed all these stages, even though I'd communicated my needs during the initial call. The questions asked were reasonable, and the interviewers seemed very pleasant.
- They asked me to solve the Fuzz buzz problem.
- I was asked about a reverse string algorithm.
- We discussed a system architecture problem.
Senior Software Engineer
Everyone I interacted with was super nice and friendly, which was great. I enjoyed my time working with them during the interview. What I found a bit confusing is they scheduled a phone call after my on-site interview just to tell me I didn't get the job. While I appreciated them wanting to give me feedback (even though it was minimal), I would have preferred an email to keep things asynchronous since they didn't need to talk to me. Thanks for the feedback, I appreciate it, but the overhead, even though it was light, of a phone call that won't lead anywhere and doesn't require my input is annoying.
- How would you design a social media site to accommodate a large number of users?
- What are your thoughts on parsing?
SeatGeek Software Engineer Interview Questions
Quoted word for word from SeatGeek interview reports.
“Implement API request throttling to limit requests to 500 per minute.”
Read reports →“How would you design an API rate limiter?”
Read reports →“Solve the question related to the "goto" method.”
Read reports →“Can you explain how you'd create an algorithm that finds pairs of integers in a list that add up to a specific target number?”
Read reports →“Implement a class containing business logic.”
Read report →“Solve 1-2 LeetCode medium data structures and algorithms problems.”
Read report →“How would you design a social media site to accommodate a large number of users?”
Read report →“Create a banking application using Codesignal tests.”
Read report →“Could you solve the ticket parser problem?”
Read report →Formats, difficulty and experience
Across all 31 SeatGeek interview reports.