Pebl logo

Pebl Software Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

4 Rounds average
Average Typical difficulty
40% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Pebl.

Showing 3 of 15
Pebl logo
Pebl

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen Offer
Interview formats
Behavioral Coding

Everyone was super nice. I usually got a response within a week after each interview. First, a quick zoom call, no video. They asked about my salary expectations, past experiences, etc. Then, a behavioral interview. After that, a coding interview. Then, a second coding interview. Finally, a congratulatory call to discuss the offer. The coding interviews were pretty fair. Nothing too crazy like inverted binary trees. They seemed more interested in my thought process and problem-solving skills, and I was even allowed to Google things.

Confirmed questions5 questions
  • What are your salary expectations?
  • What is the biggest team you've worked on?
  • Do you have any questions for me?
Pebl logo
Pebl

Software Engineer

Engineering

Mid Average Negative experience No offer 4 rounds
Interview process
Technical screen Onsite
Interview formats
Technical Coding System Design Behavioral

First there was a Woven assessment which had 3 parts: debugging, coding, and code review. Then, I was sent for an onsite interview. Recruiter mentioned that it could be anywhere from 2-4 interviews. The onsite included a behavioural/leadership interview with about 5-6 questions, a standard system design interview, and a technical interview. The technical interview had a very open ended question which required a lot of probing to understand the solution. My interviewer was not engaged at all, and did not respond to my questions or just gave one word answers. They seemed to be multitasking during the interview. This resulted in me not solving the technical challenge. After the interview, I asked about the company and the interviewer struggled to say anything positive about it or their experience working there. I got a really negative vibe from the interviewers onsite. They were cold, distant, and seemed like they had better things to do. I was rejected, but I would have declined an offer anyway based on the onsite experience.

Confirmed questions8 questions
  • Can you describe a past project you were involved in?
  • Could you share an instance where you faced a tough decision?
  • Could you elaborate on a debugging problem you encountered?
Pebl logo
Pebl

Software Engineer

Engineering

Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

It started with a recruiter screen, though the recruiter didn't seem very knowledgeable. Next was the hiring manager chat, which finished 15 minutes early. Then there was a poorly worded woven assessment. The onsite was really short: one system design interview, one coding interview, and one 'behavioral' interview that mostly focused on project details, lasting about 30 minutes. It might be good practice for other interviews, I guess. I wouldn't have joined anyway because no one made an effort to 'sell' the company.

Confirmed questions4 questions
  • Why do you want to join VG?
  • Typical systems design questions
  • Coding questions

Pebl Software Engineer Interview Questions

Quoted word for word from Pebl interview reports.

How would you calculate the monthly subscription cost for a group of users, taking into account active users, those who have deactivated, and new users joining within a specific month?

Read reports

Could you design a music streaming service, similar to Spotify but focusing only on the downloading functionality?

Read reports

Given tasks with priorities, how would you ensure they execute before others? (Hint: Use a minHeap).

Read report

Could you elaborate on a debugging problem you encountered?

Read report

Formats, difficulty and experience

Across all 15 Pebl interview reports.

Interview formats

Coding 27.7%
Behavioral 27.7%
Technical 23.4%
System Design 19.1%
Group 2.1%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Negative 33.3%
Neutral 26.7%
Positive 40%