Sure logo

Sure Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 70 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
55.7% Positive experience

Which role are you interviewing for?

16 roles · 70 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Sure.

Showing 4 of 70
Sure logo
Sure

Project Manager

Operations · more than a year ago

Senior Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Panel Offer
Interview formats
Behavioral Technical Presentation

The interview process spanned about 3 weeks and involved 5 rounds. The recruiter was really great, always keeping me in the loop about what was coming next and even sent over info on what to expect in each interview. Everyone I met was genuinely excited about the company and their work. The interviews themselves were more like good conversations, with interesting and thought-provoking questions. It started with a 30-minute chat with the recruiter, then an interview with the hiring manager, followed by a meeting with the VP of Product, then the CTO, and finally a panel with two program managers and another project manager. It was a really smooth and well-run process, and I was happy to accept their offer in the end!

Confirmed questions1 question
  • Can you describe how you foster effective communication and collaboration when working with a remote team?
Sure logo
Sure

Engineering Manager

Engineering · more than a year ago

Manager Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Presentation
Interview formats
Behavioral Technical Presentation

The whole thing took about five weeks and it was a good experience. The main recruiter kept in really close touch which was great. I always got a response within a few hours. Everyone I talked to was really passionate and welcoming. I had some really good talks that helped me decide to accept the offer, especially the one at the VP stage. The questions felt thoughtful and were designed to get you talking about a subject. They also sent a good amount of info upfront explaining the process and what to expect at each step.

Confirmed questions2 questions
  • Tell me about a difficult decision you had to make that impacted your team.
  • If we hire you, what might make you regret accepting the job within your first three months?
Sure logo
Sure

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check
Interview formats
Behavioral Technical Coding

So basically, the interview process here is what you make of it, and don't take my word for it. I was kinda nervous after reading other people's experiences, but honestly, I'm glad I went through it. What others missed is that right after you talk to the recruiter, they send you this super detailed interview guide. It lists all the jobs, not just for SWEs, but for other roles too. It also explains company values, gives interview tips, and links to their social media and career pages. For the SWE role specifically, the guide goes deep into the whole process. If people actually read it, they'd see there are no surprises because it lays everything out. It even tells you how long each part takes, so I think people just didn't read it and then complained about unexpected stuff. My process went like this: First, a 30-minute recruiter call, who might be your main contact. Then, a 45-minute Engineer Manager Peer Screen. After that, you can either do a take-home assessment (you get 3 days) or a 90-minute live pairing session. If you did the take-home and did well, you'd have a 1-hour review session. Finally, a 45-minute VP of Engineering Behavioral Interview. The order might shift a bit due to scheduling, but the guide was really clear and they followed it closely. They always got back to me quickly when I had questions. The take-home involves building a web app, dealing with quotes and data persistence. Seriously, read the requirements carefully and don't just do the bare minimum. Get creative, document your code, and make it presentable, not perfect but functional. Your README needs clear instructions on setup and running. Using Django is a big plus since it's in the job description, along with Python 3. Showing you know Django will definitely help. But that's just my take. It's cool that it gives you a taste of the actual work. The take-home review felt more like a chat, giving you a preview of daily work and collaboration. Be ready to talk about how you'd improve the code or use different approaches. This is your chance to show what you know. They really focus on soft skills, which makes sense since it's remote. Good communication and teamwork are key. I got an offer and accepted it because the pay is great, benefits are solid, and I'm excited about the new team. The interview process was the most positive I've had, with recruiters and the team being responsive and accommodating. I recommend Sure if you're willing to put in the effort.

Confirmed questions7 questions
  • How do you deal with conflict?
  • Tell me about how you bring up a new idea.
  • How do you communicate with others?
Sure logo
Sure

QA Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Panel
Interview formats
Technical Coding Behavioral

The interview process is quite long and honestly feels like a waste of time. They have 4 steps: first, an initial call with the recruiter. Then, an interview with the QA manager. Next is a take-home assignment which is way too long and frankly not great quality, with errors in it, yet they expect a polished output. Finally, after the assignment, there's a panel interview with three people. Even though the job is listed as manual QA, they seem unsure if they want manual or automation, going back and forth on it. Honestly, it's not worth the time and effort.

Confirmed questions1 question
  • Were there questions asked that were outside the typical scope of a QA Engineer's responsibilities?

Sure Interview Questions

Quoted word for word from Sure interview reports.

What are the characteristics of great leadership for a team?

Read reports

Could you build a limited RESTful API to create and save quotes for a new product, and also calculate the premium for each quote?

Read reports

Could you build an API to create and save quotes for a new product, and also figure out the premium for each quote?

Read reports

Create a frontend application fulfilling the following extensive and standard requirements: *insert large, typical requirements outline*.

Read reports

My previous team built two models, Model A and Model B, but we don't have a lot of records or instances to track. How would you refactor these models or create new ones to combine them?

Read report

For a PM, what's the single most important soft skill and what's the single most important hard skill?

Read report

What extra info would you put in a PRD to help engineers start work with good info?

Read report

What do you consider to be the most crucial soft skill for a Product Manager, and what is the most crucial hard skill?

Read report

Formats, difficulty and experience

Across all 70 Sure interview reports.

Interview formats

Behavioral 39.1%
Technical 35.3%
Coding 13.5%
Presentation 7.1%
Other 3.2%

Interview difficulty

Easy 22.9%
Average 70%
Difficult 7.1%

Candidate experience

Neutral 14.3%
Negative 30%
Positive 55.7%

Reports by job function

Engineering 37
Product 15
Sales 8
Operations 4
Design 2
HR 2