
Qubit Software Engineer 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
Candidate interview experiences
First-hand accounts from people who interviewed at Qubit.
Software Engineer
I applied online for the Junior Javascript Engineer role, which is part of their client services team. About two weeks later, a recruiter from London called me for a 30-minute phone screen. We talked about Qubit, the job, and what I was looking for. Then, we set up a video interview with two client services engineers, one from NYC and one from London. After that, I had to do a coding challenge that took me about 4-6 hours. Next, I went for an onsite interview and met two team members: one for technical skills and one for culture fit. Then, I had a final video interview with someone from London to go over the job expectations. After that, the recruiter emailed me saying an offer was likely. I then met with my potential manager to discuss how to prepare for the role. Two days later, the recruiter sent a short email saying things had changed and they couldn't make me an offer anymore. It was cool meeting the Qubit team, they were knowledgeable, but it was frustrating to spend so much time interviewing only for them to cancel the role without warning. It left a bad impression even though I liked the role and people. I hope they're more upfront with future candidates.
- What distinguishes you from other software engineers?
Software Engineer
I applied online and a recruiter reached out. The first round was a coding test on Codepad with two engineers, with progressively harder exercises. After that, I had a second interview with two more engineers. We had a short chat, and then I was asked to design a system with scalability and availability concerns, followed by a brief coding exercise on Codepad. The interviewers were great and the interviews went well. I was then invited for an on-site interview. However, the process suddenly stopped. I had already gotten my visa for London and asked the recruiter twice to confirm the interview date, and they said they'd get back to me but never did. Two months later, I followed up about reimbursement for my visa costs. The recruiter finally replied, just forwarding the request without any explanation, acting as if nothing had happened. Recruiters can sometimes get overloaded and forget things, but at least they usually apologize. It's hard to accept such unprofessional and rude behavior, especially after investing time in interviews and visa arrangements. This recruiter's attitude was really poor, essentially saying 'I forgot you, tough luck, no excuse.' The engineering team seems great, but they shouldn't be let down by an unreliable and rude recruiter.
- How would you implement some functionalities for building a test framework?
Software Engineer
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.
- 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 Software Engineer Interview Questions
Quoted word for word from Qubit interview reports.
“How can you ensure that two asynchronous functions have finished executing?”
Read reports →“How would you implement some functionalities for building a test framework?”
Read reports →“Are you familiar with functional programming concepts?”
Read reports →“Do you understand common data structures?”
Read reports →“Do you have a good grasp of fundamental algorithms?”
Read report →“Do you have proficiency in your primary programming language?”
Read report →“What is a project you have recently completed?”
Read report →“What distinguishes you from other software engineers?”
Read report →“Can you describe a project you've recently finished?”
Read report →Formats, difficulty and experience
Across all 6 Qubit interview reports.