Bobyard Software Engineer Interview Experience — Five Rounds From a Take-Home to a Four-Person Panel Onsite

Bobyard·Software Engineer·Apr 2026
OnsiteTechnical ScreenTake-home Projectmedium

Five rounds total.

Round 1 is about your resume and experience. They have a technical recruiter who asks about some tech details. They asked a few common coding questions: if you find the frontend is loading slowly, how do you fix it? If you find a prod bug, how do you handle it?

Round 2 is a take-home project. They ask you to design the frontend, backend, and DB for a comment system, satisfying CRUD functionality. No time limit, just turn it in within 2-3 days.

Round 3 is 30 minutes. It's purely giving requirements and then coding, there's no chat at all. Based on your comment system, add sorting functionality. It needs to support ascending and descending order by timestamp and userId. Then extra points: if you can make sure these choices persist after a refresh.

Round 4 is 45 minutes. Still pure coding, no chat portion to prepare for. Same comment system, but now the shape of the data has changed. Now each piece of data comes with a parentId. The requirement is to implement nested comments based on this new shape. No backend changes needed, you can just use mock data directly on the frontend. Extra points: support filtering within the nested comments. You only show the matched comment and its children. All other comments outside of that should not show.

Round 5 is the onsite. There are two parts total: panel interview + manager 1:1. The panel interview has 4 people interviewing together (PM + CEO + manager + senior dev).

Senior dev: asked me a lot of system design questions, all centered around their system. For example, their system needs to generate images. Then asked how I would design a system like that. Said that generating images takes a long time, so a normal HTTP request would have timeout issues — how would I solve that. Including how I'd solve the problem that user requests need to be ordered. Then if I know the frontend is slow, how would I figure out which specific element is causing it.

CEO: I felt like he was asking whatever came to mind. He asked a little bit of everything.

PM: asked about past experience/projects. Focused on behavioral questions. But I felt like they leaned pretty startup-style in how they asked things. They really wanted you to talk about a lot of big things you've done.

Manager: I think this was more supplementary to what came before. Asked a bit of both behavioral and system design.

1:1: this was just if there was anything more they wanted to know. The manager would dig deeper.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Bobyard
Role
Software Engineer
Rounds
Technical Screen → Take-home Project → Onsite
Difficulty
medium
Interview date
Apr 2026
Questions from this interview
3 questions

Real Bobyard interview experiences

First-hand reports from Bobyard candidates — the rounds, the questions they were asked, and how it went.

All 6 Bobyard interview experiences