
Raptive Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 35 interview experiences · FREE TO READ
Which role are you interviewing for?
15 roles · 35 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Raptive.
Engineer
I had six interviews for this role, and honestly, only two of the people interviewing me seemed to know anything about the team I was applying to join. Everything seemed to go okay during the interviews, but ultimately I didn't get the job. In total, I spent more than six hours interviewing with Raptive. That feels like way too much time for both me and them. The whole process felt super inefficient, so I'd tell others to be really careful about agreeing to interview with Raptive because their process is just not reasonable.
- Tell me about a time you had to champion a customer's needs.
Software Engineer
The interview process kicked off with a recruiter call, followed by a hiring manager screen. Then came a technical screen focusing on data structures and algorithms (DS&A), and a coding round also centered on DS&A. Next was a code review exercise and a system design interview where I had to design a software system from scratch. The project deep dive focused on a complex data platform design I owned, which I could explain verbally or draw on a whiteboard. Finally, there was a behavioral interview centered on leadership behaviors. The whole process felt pretty lengthy but most interviewers were friendly. DS&A questions were generally easy to medium difficulty.
- Can you explain the difference between an inner join and an outer join?
- Could you clarify the meaning of 'this' in JavaScript?
- What distinguishes callbacks from promises?
QA Automation Engineer
Got a 15 min recruiter chat, which was totally fine. Then a 75 min interview with a team member, including a screen share task. The interviewer was nice, and overall it felt good. But here's the bad part: I had my first interview on Wednesday and they laid out the process, which included 3 more calls. Then on Friday, I got an email saying someone accepted an offer on Thursday. Why bother with a 75 minute interview if they already made an offer the day before? I applied right after the job was posted and heard back fast. I scheduled the interview ASAP. How did someone else finish the whole thing in that time?
- How would you test a get endpoint and automate those tests in Postman?
Data Intelligence Vice President
The interview process lasted for 3 weeks from the initial interview until the offer was extended. Everything was done remotely via Zoom, making it a pretty straightforward experience. First, I had a chat with the Hiring Manager. Then, I met with some stakeholders and team members for the second round. Finally, the third round involved a conversation with HR.
- Can you share details about your past work experience?
- Describe your approach to stakeholder management.
- What are your capabilities regarding technical skills?
Raptive Interview Questions
Quoted word for word from Raptive interview reports.
“Implement a function to validate balanced brackets in a given expression.”
Read reports →“How would you find all pairs in an array of numbers that sum up to a target number?”
Read reports →“Can you create a class for a movie rating database?”
Read reports →“Could you clarify the meaning of 'this' in JavaScript?”
Read reports →“Can you solve the Valid Brackets problem?”
Read report →“How would you test a get endpoint and automate those tests in Postman?”
Read report →“Could you explain what an inner join is in the context of databases?”
Read report →“Can you explain the difference between an inner join and an outer join?”
Read report →“How can code A/B testing be performed using edge functions?”
Read report →Formats, difficulty and experience
Across all 35 Raptive interview reports.