
RevenueCat Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at RevenueCat.
Software Engineer
The interview process started with an experience and values interview question to talk about the last company and projects to evaluate the senior experience. I talked about my last projects and the work that I was currently doing in the company. I expanded on the projects and explained them, but I end up not moving forward in the process. The seniority required for the role was higher. Cool thing was that everyone at the company knows about programming. The conversation was also really nice.
- Could you describe your most recent project at your company?
- What was your specific role within that company?
- What was the overall size of the company?
Software Engineer
The whole interview process was super quick and easy, wrapped up in about three weeks. Setting up the interviews was a breeze because they had a lot of open slots. I went through a few stages: first, I chatted with an Engineering Manager, then a technical screen. After that, there was an interview loop that dug into system design, testing/debugging, and also checked if I'd be a good culture fit. The last step was a final interview with one of the co-founders. Honestly, it was the best interview I've ever done.
- Can you discuss your approach to system design questions relevant to our business?
- How would you handle testing and debugging scenarios?
- What are your thoughts on value alignment and culture fit within our company?
Software Engineer
The process is quite extensive, with roughly 9 separate interviews. It starts with a 30-minute chat with a recruiter about your background and the role. Then, there's a 1-hour technical and live-coding session with an engineer. You'll also receive a take-home assignment, which is expected to take about 2 hours. This take-home will be reviewed with an engineer. Following that, there's a 1-hour interview with the team manager, another 1-hour coding session, a 1-hour system design interview, and finally, a 1-hour discussion about cross-functional work and company values. It's a significant time commitment, maybe more than other companies like Square, and it felt like it dragged on because it was hard to schedule. The take-home wasn't very related to the actual job, which was a bit disappointing. I liked the recruiter and engineers, but not so much the others.
- Tech challenge: data question in SQL, then the same again in python
- Take home: Build a react app to use some endpoints
- Behavioral: pretty standard
RevenueCat Software Engineer Interview Questions
Quoted word for word from RevenueCat interview reports.
“How would you design a toast-like UI element using Compose?”
Read reports →“Can you implement an LRU Cache?”
Read reports →“Can you build a web-app using a front-end framework, adhering to specific criteria for its features and design?”
Read reports →“What was the overall size of the company?”
Read reports →“Can you write a basic SQL query?”
Read report →“How do you manage negative feedback?”
Read report →“How do you handle stressful days and maintain productivity?”
Read report →“Could you solve this problem given the input data and required output, which reflects a potential work task?”
Read report →“What motivates your interest in working at RevenueCat?”
Read report →Formats, difficulty and experience
Across all 16 RevenueCat interview reports.