Wave logo

Wave Site Reliability 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

3.8 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wave.

Showing 3 of 5
Wave logo
Wave

Site Reliability Engineer

Engineering · nearly a year ago

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

I first chatted with a Wave recruiter after applying online. Then, over about 9 days, I went through several interview rounds. It kicked off on Thursday with a 30-minute screener, followed by a take-home programming assignment that took me about 4 hours on Friday. The following Tuesday, I had a 2-hour interview focused on monitoring and troubleshooting. On Thursday, there was a 1.5-hour session on critical thinking and rationale, and then a 1-hour culture fit and values chat. By Friday, I got the offer and accepted.

Confirmed questions1 question
  • The take-home task involved coding a rate-limiter function using Python. I was given specific instructions and a code repository with a starting point.
Wave logo
Wave

Site Reliability Engineer

Engineering · a year ago

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

A recruiter reached out on LinkedIn, I had a screening call, and then got a take-home task. I finished the take-home task completely according to their rubric, but then got rejected a few days later. Felt like a waste of time.

Confirmed questions1 question
  • Can you write a rate limiting micro service middleware for a rest api backend and deploy it onto GKE?
Wave logo
Wave

Senior Site Reliability Engineer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Take home Technical screen Onsite Presentation Background check Offer
Interview formats
Technical Coding Behavioral System Design Presentation

The interview process was quite organized and flowed well. I kicked things off with an initial chat with the hiring manager, followed by a technical test that I could do on my own time. Next up was a two-hour interview with one of the engineers, where we mostly chatted about monitoring and how to handle incidents. After that, I had a more in-depth talk with the hiring manager about my previous projects. The final step was an interview with the CTO. They sent over an offer pretty soon after that.

Confirmed questions3 questions
  • Tell me about your programming skills.
  • What's your experience with Google Cloud Platform?
  • Describe your experience in Site Reliability Engineering.

Wave Site Reliability Engineer Interview Questions

Quoted word for word from Wave interview reports.

How would you deploy a rate limiter to k8s and adapt a Flask app to use it?

Read reports

Can you write a rate limiting micro service middleware for a rest api backend and deploy it onto GKE?

Read reports

Describe your experience in Site Reliability Engineering.

Read report

Can you describe a technical accomplishment you've had in detail?

Read report

Could you describe a project you worked on and your specific role in it?

Read report

Formats, difficulty and experience

Across all 5 Wave interview reports.

Interview formats

Technical 31.2%
Coding 31.2%
Behavioral 18.8%
System Design 12.5%
Presentation 6.2%

Interview difficulty

Easy 0%
Average 80%
Difficult 20%

Candidate experience

Positive 40%
Negative 60%