
Tickets.com Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 7 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Tickets.com.
Customer Service Representative
after i applied on the website and everything went well, they will call you and send you the interview link for you to join with the HR and then the user for a video call using google team.
- Have you traveled before in your life?
- Do you know what a hotel lobby looks like?
- How does an airport look like?
Data Engineer
Got a ping from an HR recruiter, had a chill initial chat. Then scheduled a call with the data engineering team for an intro/tech assessment. The intro/tech assessment panel was kinda blunt, didn't even introduce themselves. Jumped right into a SQL test. After reading the problem, I started writing code, but before I could even run it, the lead guy said the syntax was off and they weren't proceeding (it wasn't even that complicated, the code worked in SQL Server but not Postgres - my bad?). Two weeks later, another HR recruiter reached out (both had internal emails, which shows they weren't even paying attention).
- A question related to SQL, the specifics escape me.
QA Engineer
The interview process was not great. First, I spoke with a Sr recruiter who seemed really checked out and asked me questions I'd already answered. It felt like it went badly. Then, a few days later, another recruiter called, and that call was good. I was told I'd have to speak to the same Sr recruiter again, which was confusing. They asked for references and did a background check, and then... nothing. No replies to my emails, no further information. Two months later, after I'd already started and worked at a new job for two months, they told me they had moved on to other candidates. It seems like they have no idea what they're doing, maybe interviewing just to say they did, and totally wasting people's time. Someone else I know had the exact same experience - interviewing in the wrong order, background checks, promises to follow up, and then silence. Honestly, I think I dodged a bullet here.
- Can you tell me where you're based?
- Are you aware that this is not a unionized environment?
- Given that we don't offer remote work, are you able to commute to the office?
Software Engineer
It's the standard process: first a phone screen, then an in-person interview. The questions were pretty specific and not that hard, but if you haven't worked with the specific modules they focus on, you might not have a good answer. Maybe it's unfair, and it's definitely a bad way to interview. They don't seem to care about your ability to think outside the box or make tough decisions when there's no clear path forward; they just want to see if you can jump into coding immediately without any prior training.
- Can you explain how to pre-populate command objects using a controller?
Tickets.com Interview Questions
Quoted word for word from Tickets.com interview reports.
“How does an airport look like?”
Read reports →“How would you calculate the median for each group in SQL, knowing that median is not a built-in aggregate function?”
Read reports →“Can you explain how to pre-populate command objects using a controller?”
Read reports →“Do you know what a hotel lobby looks like?”
Read reports →“Are you aware that this is not a unionized environment?”
Read report →“Have you traveled before in your life?”
Read report →“Given that we don't offer remote work, are you able to commute to the office?”
Read report →“Can you tell me where you're based?”
Read report →“Did you have any experience with data?”
Read report →Formats, difficulty and experience
Across all 7 Tickets.com interview reports.