Peek logo

Peek Backend Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

4.7 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Peek.

Showing 3 of 6
Peek logo
Peek

Backend Engineer

Engineering

Mid Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Offer
Interview formats
Behavioral Technical Coding

It is basically composed by: 1. Phone screening interview - A brief talk with HR department to present to you the process, the position, the company, and get your expectations; 2. Talk with Manager - A 1 hour conversation with an Engineering Manager to discuss about your career, what kind of thing you've done and working with, and how do you work with your team and colleagues; 3. Technical test - You receive a test specification to build in your place, and you must send the final result in a few days (3~5 if I remember); 4. Test review - You talk with 3 or 4 engineers about your test, and other technical questions and scenarios. It's a dynamic "ask me anything" where you answer technical questions; 5. Chat with Manager - You and the previous Engineering Manager chat again about how was the test process, and career expectations; 6. Offer - You receive your final offer and feedback about how they fit you into a position.

Confirmed questions3 questions
  • How do you collaborate with remote teams?
  • Describe a time you dealt with an internal conflict at a previous job.
  • How would you adapt your software if a new scenario XYZ were introduced instead of your current solution?
Peek logo
Peek

Backend Engineer

Engineering

Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Technical Coding

The interview process was quite fast. First, a recruiter set up some initial screenings. Then, I had a tech challenge and a technical interview. After that, there was a final interview. Throughout the process, I received constant email updates about my status and what to expect next, so I felt well-informed. It felt more like a mutual discussion to see if we were a good fit, rather than a test to prove my worth or a way to weed out candidates.

Confirmed questions1 question
  • How can one keep a healthy mindset and work ethic during a period of rapid company growth?
Peek logo
Peek

Back End Engineer

Engineering

Senior Difficult Negative experience No offer 2 rounds
Interview process
Phone screen Take home
Interview formats
Technical Coding

I had a 45-minute phone call, and after that, they invited me to do a 10-hour take-home coding challenge. I declined because it's not reasonable to ask candidates for that much time.

Confirmed questions1 question
  • Complete a take-home coding challenge that should take 10 hours.

Peek Backend Engineer Interview Questions

Quoted word for word from Peek interview reports.

How can one keep a healthy mindset and work ethic during a period of rapid company growth?

Read reports

Can you explain your reasoning for the way you structured your code in the HackerRank challenge?

Read report

How would you adapt your software if a new scenario XYZ were introduced instead of your current solution?

Read report

Describe a time you dealt with an internal conflict at a previous job.

Read report

Formats, difficulty and experience

Across all 6 Peek interview reports.

Interview formats

Technical 37.5%
Coding 37.5%
Behavioral 25%

Interview difficulty

Easy 16.7%
Average 50%
Difficult 33.3%

Candidate experience

Positive 66.7%
Neutral 16.7%
Negative 16.7%