Voodoo logo

Voodoo Backend Engineer 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

3.6 Rounds average
Average Typical difficulty
100% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Voodoo.

Showing 3 of 7
Voodoo logo
Voodoo

Backend Engineer

Engineering · a year ago

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Behavioral Technical

So the whole thing took about 3–4 weeks. It was three video calls and one coding test. First up was HR, then a coding challenge that mixed front-end and back-end stuff. After that, I had a chat with the tech lead about culture fit. The last part was a combined interview with the lead mobile dev and the CEO, mainly to see if I’d vibe with the team and the company’s values.

Confirmed questions1 question
  • Can you share your experiences working within a team and how you handle receiving feedback, considering their emphasis on communication and cultural fit?
Voodoo logo
Voodoo

Backend Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Behavioral Technical

It was a pretty standard process. First, we had a chat about the company and my background. Then, I did a technical test. After that, we debriefed the technical test. Lastly, there was a team fit interview.

Confirmed questions2 questions
  • What motivated you to apply to Voodoo?
  • Tell me about your interests and why they align with joining Voodoo.
Voodoo logo
Voodoo

Senior Backend Engineer

Engineering

Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Panel Offer
Interview formats
Behavioral Technical Coding

The interview had four parts. First, I talked with the Technical Recruiter, who was really great and made everything easy and clear. Then, I got a home technical test. It was tough but doable and felt like real work, which was cool, unlike those usual algorithm tests. After that, I went over the technical test with the CTO and Head of Backend. We talked through it and dug deeper. The questions were tough but interesting, and it was a good chat. The last part was a chat with the CEO. It was super helpful to get their vision for the company's products and business. Hearing their goals directly was inspiring and made me more excited. The whole process was well-thought-out and engaging, giving me a good vibe about the company and its people.

Confirmed questions1 question
  • Given that 99% of users are requesting the same data, how would you architect your cache to avoid a single key becoming a bottleneck and ensure improved scalability?

Voodoo Backend Engineer Interview Questions

Quoted word for word from Voodoo interview reports.

Given that 99% of users are requesting the same data, how would you architect your cache to avoid a single key becoming a bottleneck and ensure improved scalability?

Read reports

Tell me about architecting a backend API for a very large user base that experiences burst requests during specific times.

Read reports

Could you describe how you would implement a new feature for discovering posts within the app, and then detail your deployment strategy and how you'd handle potential issues post-deployment?

Read reports

Tell me about your interests and why they align with joining Voodoo.

Read report

What's one characteristic from your past or present employer that you'd want to see implemented here?

Read report

Can you share your experiences working within a team and how you handle receiving feedback, considering their emphasis on communication and cultural fit?

Read report

Formats, difficulty and experience

Across all 7 Voodoo interview reports.

Interview formats

Behavioral 33.3%
Coding 22.2%
Technical 22.2%
System Design 16.7%
Group 5.6%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 100%