Percolate Backend 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 Percolate.
Percolate
Backend Engineer
Mid Average Neutral experience No offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Coding Technical System Design
First up was a take-home coding challenge, which wasn't too tough. Then came the onsite interviews. The first one involved a review of my resume and a discussion about database design. The second onsite round focused on computer networks.
Confirmed questions1 question
- Can you explain foreign keys in the context of database design?
Percolate
Backend Engineer
Mid Average Positive experience No offer 3 rounds
Interview process
Take home Phone screen Technical screen Onsite Presentation
Interview formats
Coding Technical Behavioral
It started with a coding exercise that was pretty straightforward but took a good amount of time to complete. Then, there was a 30-minute phone interview, followed by an onsite where I had an hour for coding and technical questions with two Backend Engineers. I also had a 30-minute chat with the Director of Engineering. Scheduling was easy and the recruiter got back to me quickly. Everyone was really nice and welcoming, and I got a good vibe from Percolate. I know I could have used more experience, but I felt they evaluated me fairly.
Confirmed questions6 questions
- A round of short Python coding exercises involving basic datatypes.
- A few questions about databases.
- OOP and its application to real websites.
Percolate
Backend Engineer
Senior Average Positive experience Decline offer 6 rounds
Interview process
Recruiter call Take home Technical screen Onsite Background check Offer
Interview formats
Technical Coding Behavioral System Design
I was referred by someone who works here, so that was pretty cool. First I chatted with the hiring manager, they told me all about the job and what they're looking for. Then I got a coding challenge, which was pretty fair and they gave me some wiggle room on the deadline because I had other stuff going on. After they looked at my code, I had a video call with an engineer who checked it out. Next thing I knew, I was scheduled for an onsite. They sent me an email beforehand with who I'd be meeting and their roles. The first couple of interviews onsite were with engineers, two in each chat. They asked a few algorithm questions, but mostly they wanted to hear about how I tackled problems on past projects and how I'd handle some made-up but realistic scenarios. After that, I met with the hiring manager again, the VP of Engineering, and the internal recruiter. All in all, they were super communicative, got back to me fast, and paid attention to all the little things.
Confirmed questions2 questions
- Can you tell me about how you built the data pipeline for project X?
- What was your reasoning for choosing technology X when developing feature Y?
Percolate Backend Engineer Interview Questions
Quoted word for word from Percolate interview reports.
“A round of short Python coding exercises involving basic datatypes.”
Read reports →“Can you explain foreign keys in the context of database design?”
Read reports →“Asked about the Python standard library.”
Read reports →“OOP and its application to real websites.”
Read reports →“Asked about a quicksort variant.”
Read report →“How would you design a scoreboard?”
Read report →“Asked about Python data structures.”
Read report →“Talk with director was about goals.”
Read report →“A few questions about databases.”
Read report →Formats, difficulty and experience
Across all 6 Percolate interview reports.