
Percolate Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 76 interview experiences · FREE TO READ
Which role are you interviewing for?
28 roles · 76 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Percolate.
Frontend Engineer
This was my first interview experience that felt really personal, not like the usual generic ones. After a chat with HR, the first step was an algorithm challenge. I liked how they gave me a small algorithm and then asked me to expand on it, which really tested my JavaScript abilities and was spot-on for the role. Then came the onsite interviews where I met the engineers I'd be collaborating with and some senior folks. The onsite included discussing my experience and a coding session using React. This was also very relevant to the job. Everyone I met was super friendly and made me feel welcome. I genuinely enjoyed the whole process and getting to know the team.
- Could you solve a JavaScript algorithm problem?
- Can you build a simple React component?
- Tell me about your background.
Support
So I had a phone interview first with the Recruiting lead, she was really nice and told me all about the job, pay, company and what they expect. Then I had two video interviews with the NY team. The first was with a team member I'd work with daily. We talked about my past experience and what a typical day in the role would be like. After that, I was invited to interview with the Director. This interview was over Zoom. The second video interview was with the Director of IT and Support. We really got into my experience with Percolate's systems and my overall technical background. We also discussed my time in tech startups and situations I've faced in similar roles. A big part of this interview was about culture fit, making sure I'd be a good addition to the support team's dynamic. Finally, I was invited to the San Francisco office for two in-person interviews. These were with long-term employees from different teams and were mostly about culture fit and how I'd vibe with the SF team.
- What have you done in the past to triage an issue or bug?
- Describe your past experience.
- Walk me through your day-to-day life in the role.
Customer Success Manager
I applied online and about a week later, the recruiter called me. It was a standard first call where she asked about my job history, went over the role details, and inquired about my salary expectations. She was nice to talk to. After our chat, she scheduled a second interview with the VP of Customer Success and also sent me an assessment to complete beforehand. This assessment had about 5 questions, each with multiple parts, asking how I would manage certain scenarios. I finished and sent it back in under a day. The second interview with the VP of CS was a video call. It wasn't super hard; they asked about my background again and some basic situational questions. The interviewer, though, seemed really disengaged the whole time, constantly looking away, fidgeting, and appearing rushed. My thoughtful questions seemed to pique his interest, but while I was answering his, his mind was clearly elsewhere. The next business day, I got an email saying they found other candidates whose skills were a better fit and I wouldn't be proceeding. It's frustrating because I have years of experience in this exact role. Plus, the job posting was over 30 days old when I applied, and I still see new postings for the same job in the same location, suggesting they're still looking.
- Can you describe some difficulties you encounter in your present position?
- Could you tell me about your previous work experiences?
- What are your salary requirements?
Product Manager
I applied online and the whole thing took over 3 weeks. First, a recruiter called me. He was really rude, basically saying I was incompetent but he was giving me a shot. Then I had to do a homework assignment with some general questions. After that, I had 3 video calls with people from product, design, and engineering. The last step was an onsite interview at the Percolate New York office. The vibe of the company felt really political, like they wanted someone who would just go along with things and not challenge them or make them look bad. I got the impression some folks, especially in product, were not very competent and seemed to be looking for someone less capable than them, instead of the best person for the job. The engineering and design teams seemed okay, but the product team was pretty weak. Normally product managers are nice, but not here.
- Can you discuss a product you admire and suggest improvements for it?
- Describe a situation where you used data to make a decision.
- Tell me about a time when priorities shifted and how you managed it.
Percolate Interview Questions
Quoted word for word from Percolate interview reports.
“Write code to parse a file and then pretty print it.”
Read reports →“At 3:15, what angle do the hour and minute hands of a clock form?”
Read reports →“Can you explain foreign keys in the context of database design?”
Read reports →“What metrics are you using to track content marketing performance?”
Read reports →“When is it appropriate to cut corners to release a product?”
Read report →“What are the best practices for saying no to customers?”
Read report →“What were the specific responsibilities of each person involved in those deals?”
Read report →“Can you describe how you would build a tweet scraping system, touching on aspects like APIs, data modeling, storage, writing scripts, and overall architecture?”
Read report →“Could you take a small app developed using an older framework and rebuild it using your current front-end framework, ensuring it functions the same way?”
Read report →Formats, difficulty and experience
Across all 76 Percolate interview reports.