Riskified Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Riskified.
Riskified
Backend Developer
Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Technical Coding System Design
It started with a recruiter call, then a 1.5-hour technical interview. The interviewer was professional and we discussed past projects. After that, there was a second interview with the team lead and another developer. We discussed a company problem and I had to propose a solution. Then, I had to implement the solution, but some requirements weren't clear which made it a bit confusing. A day later, HR called to let me know I didn't pass and gave feedback.
Confirmed questions5 questions
- What is wrong with this code?
- Solve the 2 Sum problem.
- How to implement setAll in O(1)?
Riskified
Backend Developer
Mid Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Behavioral Technical Coding
Had a call with a TL, then got invited to the office for a 2-hour interview with another TL. We talked about my current job and a project I worked on. Then, we went over some code for multi-threads and discussed it. The next day, HR told me I didn't pass.
Confirmed questions1 question
- Questions about multi-threads and data structures.
Riskified
Backend Developer
Mid Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical System Design
It felt like a pretty standard backend developer interview process. I had a Zoom chat with someone from the company who was on the team. The interview went for about an hour and a half, and they told me all about the job and the company.
Confirmed questions1 question
- Can you explain how you would design a URL shortening service like TinyURL?
Riskified Backend Engineer Interview Questions
Quoted word for word from Riskified interview reports.
“How to implement setAll in O(1)?”
Read reports →“Solve the 2 Sum problem.”
Read reports →“What is wrong with this code?”
Read reports →“How would you optimize the performance to achieve O(n) complexity?”
Read reports →“What errors can you spot in the provided code?”
Read report →“Can you explain how you would design a URL shortening service like TinyURL?”
Read report →“Would you review this specific function's code and suggest improvements?”
Read report →“Implement a solution where the functional requirements were not clear.”
Read report →“Can you tell me about your recent projects?”
Read report →Formats, difficulty and experience
Across all 5 Riskified interview reports.