Qubit logo

Qubit Interview Questions
& Process

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

Based on 49 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
53.1% Positive experience

Which role are you interviewing for?

22 roles · 49 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Qubit.

Showing 4 of 49
Qubit logo
Qubit

Industrial Placement

Other · more than a year ago

Intern Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

The interview process started with a telephone interview, followed by a video interview with managers. Then, there was a video interview with a specialist, and finally, a video interview with the director. Although I had a good experience during the interviews themselves, the debriefing process after the final interview was awful. A company that promises you feedback and then leaves you waiting for a video call and never shows up is not one you want to work for. I have never experienced this before with any other company. I urge the Talent team to improve their candidate feedback procedures and to not promise things they cannot deliver.

Confirmed questions3 questions
  • Why are you interested in Qubit? And why this specific role?
  • Can you tell me about a time when... (situational question)?
  • Situational questions asked.
Qubit logo
Qubit

Manager

Other · more than a year ago

Manager Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite
Interview formats
Behavioral Technical

I went through a few calls and then some in-person interviews. It was a bit weird because the job content seemed different depending on who I talked to. The senior people were great, really inspiring and knew their stuff. But the others were confusing, some didn't seem engaged, and honestly, a bit inexperienced with interviews. Like, one lady started by saying she was super busy and had hardly any time for me. Another interviewer really disagreed with the company's direction. HR's part was all over the place too, both in how they managed things and what they asked. They just seemed to look at resumes and do a basic chat that had nothing to do with the actual job.

Confirmed questions3 questions
  • What is your understanding of our company?
  • Can you tell us who you are?
  • Basic open-ended questions without specific framing.
Qubit logo
Qubit

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Decline offer 6 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral

Recruiter reached out via email, shared details about the company and the role. After a brief phone conversation, I accepted the interview invitation. The interview process involved three technical Skype calls (one focused on architecture/design and two on coding), followed by an onsite interview day that included two technical interviews and one soft skills interview. The recruiter was responsive and accommodating to my schedule, making the process smooth. It took about a month overall, but could have been shorter if my schedule wasn't so demanding.

Confirmed questions6 questions
  • Can you tell me about your past work experience and projects?
  • How did you tackle problems encountered in your previous roles?
  • Do you have a good grasp of fundamental algorithms?
Qubit logo
Qubit

Client Services Engineer

Engineering

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Onsite Offer
Interview formats
Behavioral Technical Coding

It was a really fast process. First, I had a quick chat with HR, which was super casual, more of a 'get to know you' kind of thing. Then, I got to do a fun coding challenge. After that, I met some senior folks from the London team. This part had two sections: a chat with a senior strategist and then technical questions from two senior developers, covering theory, coding on a laptop, and practical scenarios. They promised an update in a couple of business days, and they delivered – I got an informal offer the next day and the formal one three days later. Oh, and everyone was really nice and the offices looked awesome.

Confirmed questions1 question
  • Can you explain the difference between synchronous and asynchronous JavaScript?

Qubit Interview Questions

Quoted word for word from Qubit interview reports.

What was the number of roses sold on Valentine's day in the UK?

Read reports

Could you implement a debounced currying function using vanilla JavaScript?

Read reports

How can you ensure that two asynchronous functions have finished executing?

Read reports

Given two unbiased dice and a maximum of three rolls, where each new roll overwrites the previous result, and you get a prize based on the dice sum, what strategy would you use to maximize your chances of winning a better prize?

Read reports

How would you figure out the conversion rate from SQL views?

Read report

Can you explain the difference between synchronous and asynchronous JavaScript?

Read report

If someone asked you for data that they could retrieve themselves using SQL, how would you explain SQL to them in two sentences?

Read report

If you had a $1 million budget, how would you improve a product that doesn't use electricity?

Read report

Formats, difficulty and experience

Across all 49 Qubit interview reports.

Interview formats

Behavioral 45.5%
Technical 29.7%
Coding 8.9%
Presentation 6.9%
Case 3%

Interview difficulty

Easy 12.2%
Average 83.7%
Difficult 4.1%

Candidate experience

Positive 53.1%
Negative 36.7%
Neutral 10.2%

Reports by job function

Engineering 11
Sales 10
Operations 7
Analytics 5
Other 4
Product 3