Ticketmaster Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 47 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Ticketmaster.
Ticketmaster
Software Engineer Intern
Intern Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral
The interview process was pretty chill, and the questions focused on OOP concepts rather than LeetCode-style problems. They asked directly about things like abstraction and recursion. During the interview, I asked a question that one of the interviewers had already covered. The other interviewer responded with 'Well, if you were listening...' which felt unnecessary, especially since it was one of my first interviews and I was already nervous.
Confirmed questions1 question
- Can you explain OOP concepts like abstraction and recursion?
Ticketmaster
Senior Software Engineer
Senior Easy Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Coding
Had a quick 30-minute intro chat with the software manager and an engineer. It was super positive and to the point, making me feel really comfortable. Then, I got a take-home assignment: build two API endpoints (list artists, show artist with events) from three JSON sources. It was pretty straightforward, mostly boilerplate with Spring Boot, about 100 lines of actual code. They mentioned a follow-up code review, but it never happened and I got zero feedback. The instructions said to use GitHub, but then they wanted a ZIP file. I had to download the ZIP from GitHub myself, which wouldn't send via Gmail, so I uploaded it to my personal website for them to get it. It felt like a lot of unnecessary steps.
Confirmed questions1 question
- Can you talk about some of your past career achievements?
Ticketmaster
Software Engineer
Senior Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Technical Coding System Design
Had a quick chat with HR first, then a tech phone screen. It was followed by an in-person interview with 4 separate 30-minute 1-on-1s. It was a great experience overall, the interviewers were really smart and asked interesting questions instead of the usual stuff you can find online. They gave feedback quickly and it was positive, and I got the offer the very next day.
Confirmed questions5 questions
- Be prepared to implement some string manipulation methods.
- As well as some OO design modelling such as an elevator system.
- As well as some OO design modelling such as a parking lot.
Ticketmaster Software Engineer Interview Questions
Quoted word for word from Ticketmaster interview reports.
“Create a function to calculate the change for a given amount in dollars.”
Read reports →“What is the maximum sum of a continuous subarray in an array of integers?”
Read reports →“Can you find the sublist with the largest sum from a given list of integers?”
Read reports →“Write a function that takes a paragraph of English words and returns the word that appears least frequently.”
Read reports →“Given an array and a target integer, can you determine if any pair within the array adds up to that integer?”
Read report →“What is the difference between Breadth First Search (BFS) and Depth First Search (DFS)?”
Read report →“Can you explain how to detect a cycle in a linked list?”
Read report →“How would you find the second highest salary in a Binary Search Tree (BST)?”
Read report →“Can you explain the difference between a POST and a GET request?”
Read report →Formats, difficulty and experience
Across all 47 Ticketmaster interview reports.