Quid logo

Quid Software Engineer Interview Questions
& Process

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

Based on 12 interview experiences · FREE TO READ

3 Rounds average
Difficult Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Quid.

Showing 3 of 12
Quid logo
Quid

Software Engineer

Engineering · more than a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding

So I spoke with a recruiter who outlined the process: first a Hackerrank challenge, then an onsite interview. I actually skipped the initial recruiter phone screen since we'd already met in person. I took on the Hackerrank challenge but unfortunately couldn't finish it because the last question was kind of a trick. I sent the recruiter an email after that, but haven't heard back since.

Confirmed questions1 question
  • Imagine caterpillars eating leaves; each caterpillar jumps k_i leaves at a time. How many leaves are left?
Quid logo
Quid

Software Engineer

Engineering · more than a year ago

Senior Difficult Positive experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding System Design

I had a really good experience with Quid. Ouliana, the Director of Talent, was my main contact and she was super clear and kept me in the loop the whole time. I always knew where things stood and what was coming next. It felt like they really wanted to figure out what I was good at and what I liked. The engineers I met were all smart, driven, and seemed genuinely committed to the company's success, which was awesome to see. So, the process went like this: First, Ouliana called me to chat about my background and what I'm looking for. She then gave me the lowdown on Quid, the company, and the engineering team. She was surprisingly knowledgeable about tech for someone not in an engineering role, unlike most recruiters. I got a solid grasp of their tech stack, the technical hurdles they face, and what the engineers do day-to-day. Next up was a phone call with an engineer named John. He dug deeper into my recent work and the stuff I'd built. Then he described the daily routine for engineers, some cool projects his team's working on, and how the product is developing. He also gave me plenty of time for questions. After that, it was a tech screen using HackerRank, which is a platform I'm familiar with. It was pretty standard, and I enjoyed tackling the problems, which ranged in difficulty, with the last one being the most challenging. Ouliana got back to me about an hour after I finished and told me I'd done well enough to move on to the onsite interviews. For the onsite, I met with John again, along with some of his team members. I also had lunch with people from different departments, which I really appreciated as it gave me a chance to connect with more people at the company. Finally, I met with the VPE, who was energetic and seemed really invested in his teams, even though he was backfilling due to PTO.

Confirmed questions6 questions
  • Did you solve standard algorithm questions?
  • Did you solve standard design questions?
  • Did you solve standard coding questions?
Quid logo
Quid

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

It started with a phone screen to chat about my background and interests. Then, there was a remote software screen that was specific to the role. Finally, it ended with an onsite interview. The whole experience was genuinely great, and they gave me a good chance to show what I'm good at. I can't give specific prep tips, but if you're a solid software engineer who loves what you do, you should totally apply. You'll likely really enjoy how they run things.

Confirmed questions4 questions
  • Discuss system design concepts.
  • Talk about past projects you're proud of.
  • Solve algorithms and data structures problems.

Quid Software Engineer Interview Questions

Quoted word for word from Quid interview reports.

Imagine caterpillars eating leaves; each caterpillar jumps k_i leaves at a time. How many leaves are left?

Read reports

Could you use d3's force layout to visualize nested nodes?

Read reports

How would you approach designing distributed and scaling architectures?

Read report

What's your understanding of data structures and algorithms?

Read report

Formats, difficulty and experience

Across all 12 Quid interview reports.

Interview formats

Coding 33.3%
Technical 30.6%
Behavioral 13.9%
System Design 13.9%
Presentation 8.3%

Interview difficulty

Easy 0%
Average 41.7%
Difficult 58.3%

Candidate experience

Positive 66.7%
Neutral 25%
Negative 8.3%