
Stavvy Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 27 interview experiences · FREE TO READ
Which role are you interviewing for?
14 roles · 27 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Stavvy.
Web Developer
Round 1 includes one or two behavioural interviews and one or two case interviews. Round 2 involves two behavioural interviews. Each interview usually lasts between 45 and 60 minutes, with the last 15 minutes reserved for your questions. You'll likely meet a different interviewer each time, and they'll be assessing both your skills and how well you fit in. Depending on the service line and location, expect either one or two behavioural and case interviews in the first round.
- Can you explain what CSS is and what an SQL query is?
- Can you explain what CSS is and what an SQL query is?
User Researcher
The interview process was pretty similar to Google's UX process, but without the whiteboard or portfolio presentation. They mentioned this is because it's research-based, so a portfolio wouldn't really be relevant. For a startup, there were quite a few rounds, which surprised me, but it seems they were really focused on finding someone who would fit in well with the team. In the final round, we even talked about my hobbies, and the interviewer noted that mine seemed to align well with others at Stavvy. The overall process took about five weeks and included: a call with a recruiter, a Zoom call with another User Researcher, and then three separate Zoom calls on the same day with a Product Manager, a Product Designer, and a Director of Product Management. I was told I'd hear back about a hiring decision a week or two after those final calls, but unfortunately, I never did.
- How do you communicate with team members and how have you resolved conflict?
- Can you describe how you resolve conflicts with team members?
- Tell me about your hobbies and how they might align with the team's interests.
Site Reliability Engineer
A recruiter contacted me on LinkedIn about a Senior SRE position. I discussed my salary expectations, and the recruiter provided a compensation range. My desired salary was a bit higher than their range, but the recruiter implied it was negotiable. I then went through 5 interview rounds. I received positive feedback throughout, and it seemed like a good match. A couple of days later, the recruiter called to extend an offer. However, the offer was about 15% below their stated range and 35% less than my initial request. The recruiter also indicated they wouldn't be offering a Senior role. When I asked for specific reasons why I wasn't considered for a Senior role, they said, 'No, everyone loved you.' It felt like a complete waste of my time.
- Can you discuss your background with X technology?
Software Engineer
First, there was a 15-minute call with the People Relations team where we talked about my resume, past jobs, and why I wanted to work at Stavvy. They were really nice and listened well. Then, I had a 45-minute interview with the Principal Software Engineer where I got to pick my programming language and build a basic class. After that, I interviewed with a Software Engineer II for 45 minutes and worked on some string manipulation methods. Finally, I had a 30-minute chat with Cofounder Josh about Stavvy's mission and our potential impact.
- They asked me to create a class that models a tree data structure.
- I was asked to answer several questions about string manipulation, specifically involving palindromes.
Stavvy Interview Questions
Quoted word for word from Stavvy interview reports.
“Find the missing integer in an array of numbers, like if the array is [1, 2, 3, 5, 6], the answer should be 4.”
Read reports →“How do you check if a number is a magic number?”
Read reports →“Design an SQL schema to add notification support to an existing database, meeting specific business goals and considering the current schema.”
Read reports →“Can you write a single line of Python code in the chat?”
Read reports →“Can you explain what CSS is and what an SQL query is?”
Read report →“Tell me about deep cloning.”
Read report →“What's the hardest part about building a design system, in your opinion?”
Read report →“What do you know about the marketplace?”
Read report →“Describe a time you designed a product that didn't turn out well.”
Read report →Formats, difficulty and experience
Across all 27 Stavvy interview reports.