See Tickets logo

See Tickets Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 6 interview experiences · FREE TO READ

1.3 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

4 roles · 6 reports

Candidate interview experiences

First-hand accounts from people who interviewed at See Tickets.

Showing 4 of 6
See Tickets logo
See Tickets

Web Developer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 1 round
Interview process
Onsite
Interview formats
Technical Behavioral

I had a face-to-face interview at the Nottingham office. Two people interviewed me and they asked some technical questions, as well as questions about me and what I enjoy doing in my free time.

Confirmed questions5 questions
  • Do you have experience with SQL?
  • Do you have experience with jQuery?
  • Do you have experience with HTML?
See Tickets logo
See Tickets

Vice President of Business Development

Sales

Executive Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The executive was very nice and engaging during the interview. They seemed eager to move forward and explored next steps, but then I never heard back. Even after sending follow-up notes, they didn't have the courtesy to send a note back to say thanks, but no thanks or we're postponing the process, still searching, or we've hired someone else. If people take the time to meet with you or your team, it's not too much to ask to email back. In my experience, it's a great indication of what the company is really about. Steer clear of companies who treat people without any respect. The employee reviews may be accurate.

Confirmed questions1 question
  • Tell me about your Business Development experience.
See Tickets logo
See Tickets

Python Engineer

Engineering

Entry Easy Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

The whole thing took about a week. It started with a phone call with a recruiter. We talked about my past work, what I want to do in the future, and why I'm interested in this particular job. They also asked me what I knew about See Tickets and how I'd be a good fit as a Python Engineer.

Confirmed questions1 question
  • Tell me about what you know about our company.
See Tickets logo
See Tickets

Product Manager

Product

Mid Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Onsite
Interview formats
Behavioral Technical

So at See Tickets, first I chatted with the recruiter on the phone. Then, I had an offline interview with some of the senior leaders. Overall, it was a good experience, and everyone I met was pretty nice.

Confirmed questions3 questions
  • Could you start by telling us a bit about yourself?
  • What challenges have you encountered throughout your career?
  • Can you describe your typical processes?

See Tickets Interview Questions

Quoted word for word from See Tickets interview reports.

Can you explain the different types of SQL joins and give some examples?

Read reports

Formats, difficulty and experience

Across all 6 See Tickets interview reports.

Interview formats

Behavioral 54.5%
Technical 36.4%
Coding 9.1%

Interview difficulty

Easy 16.7%
Average 66.7%
Difficult 16.7%

Candidate experience

Negative 33.3%
Neutral 16.7%
Positive 50%

Reports by job function

Engineering 4
Product 1
Sales 1