
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
Candidate interview experiences
First-hand accounts from people who interviewed at Pebl.
Software Engineer
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.
- What are your salary expectations?
- What is the biggest team you've worked on?
- Do you have any questions for me?
Software Engineer
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.
- 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?
Software Engineer
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.
- 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 →“Can you solve the Valid Parentheses problem?”
Read reports →“How would you calculate a moving average?”
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 →“What things bring you down?”
Read report →“What was your favorite cultural value?”
Read report →“Why do you want to join VG?”
Read report →“Could you elaborate on a debugging problem you encountered?”
Read report →Formats, difficulty and experience
Across all 15 Pebl interview reports.