Bobyard Interview Questions & Experiences

Bobyard·Software Engineer·Onsite - System Design / Architecture

Jul 2026

System design round at Bobyard for a software engineer role. Two prompts back to back, both with enough moving parts to keep you busy. Not the hardest I've seen but definitely required thinking across the full stack.

Design a full-stack comment system supporting create, read, update, and delete operations, with the ability to sort comments by timestamp or user ID in ascending or descending order. The user's sort preference should persist after a page refresh.
Design a service that generates images asynchronously, where the generation process can far exceed a normal HTTP request timeout. How do you accept requests, process jobs in the background, surface status and results to users, and maintain a consistent ordering of items in the UI?

“The CRUD part was fine, I had that down.”

View Post

Bobyard·Software Engineer·Onsite - Coding / Algorithms

Jul 2026

Live coding round for a full-stack role at Bobyard, building on top of a take-home comment system. Thirty minutes, no real back-and-forth, just code.

Extend the comment system from your take-home to support sorting by timestamp and by userId, both ascending and descending. Bonus: persist the user's sort selection across page refreshes using localStorage or URL query params.

“The core sort wiring wasn't bad, I had state for the sort field and direction and just passed a comparator down.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

Jun 2026

Bobyard had me build a client-side comment system from scratch, no backend, just data modeling and browser persistence. Pretty design-heavy for a software engineer role but I kind of liked that it wasn't another leetcode grind.

How would you design the data model for a client-side comment system that supports nested replies?
How would you persist comment data and user preferences like sort order using localStorage, and what are the tradeoffs?
How would you implement sort and filter behavior for comments, including nested replies?
Walk through your rendering strategy for a deeply nested comment tree.
What edge cases would you handle in this comment system?

“This is where I spent most of my mental energy.”

View Post

Bobyard·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at bobyard for a full-stack role. The whole thing was one big question that kept branching into sub-problems, more like a conversation that slowly revealed how deep the rabbit hole goes.

Design a system that generates images on demand, like an AI image-generation product. Walk through the full architecture including frontend, API gateway, queue, worker pool, storage, and CDN.
Image generation jobs can take much longer than a typical HTTP request. How do you handle that without just timing out the client?
If multiple workers are processing jobs concurrently, how do you ensure a single user's requests are handled in the correct order?
The frontend feels slow. How do you diagnose the problem and narrow it down to a specific element or cause?

“I started with the happy path and it went fine, frontend hits an API gateway, jobs get queued, workers pull and process, results go to object storage, CDN handles delivery.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026

Two practical engineering questions at Bobyard for a software engineer role. Nothing behavioral, just straight into the weeds on frontend performance and production incidents. Felt more like a working session than an interview.

A web app's frontend is loading slowly. How would you diagnose the problem, pinpoint the specific bottleneck (a component, asset, API call, DOM issue, etc.), and then fix it?
A bug has just been found in production. Walk through how you'd triage severity, reduce impact, find the root cause, keep stakeholders informed, ship a fix safely, and make sure it doesn't happen again.

“I started with the network tab and worked outward from there.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026

Two scenario-based questions for a full-stack role at bobyard, both pretty involved. Felt more like a working session than a standard interview, which I wasn't totally prepared for.

A user reports the frontend feels slow. Walk through how you'd diagnose it and prioritize fixes.
A production bug just got reported. Describe your full runbook from triage through prevention.

“I started with the network waterfall and bundle size because those are usually the obvious culprits, then got into render-blocking resources and caching.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026

Bobyard frontend interview, one meaty coding question that covered more ground than I expected. It started looking like a simple sort-and-display task but kept expanding into tree logic and persistent state. Not a bad experience, just caught me underestimating the scope.

You're given a flat array of comment objects with fields for id, userId, timestamp, content, and a nullable parentId. Implement the frontend logic to: sort comments by timestamp or userId in either direction, persist the chosen sort settings across page refreshes, reconstruct the nested comment tree from parentId relationships without touching the backend, and filter visible comments by content text so that only matching comments and their full descendant chains are shown.

“This one kept growing.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026

Live coding round at Bobyard for a full-stack role, about 45 minutes, no discussion time built in. The task was purely implementation focused and had a bonus filter feature that I suspect most people don't finish.

Given comment data that includes a parentId field, render the comments as a nested threaded tree in the frontend using mock data (no backend changes needed).
Bonus: add a filter to the nested comment view so that only comments matching the filter text and their descendants are shown, hiding non-matching siblings and their subtrees.

“The core part wasn't too bad once I stopped overthinking the recursion.”

View Post

Bobyard·Software Engineer·Take-home Assignment

Apr 2026

Bobyard sent over a take-home for a full-stack role, 2-3 days to build a comment system from scratch, frontend to backend to database. Decent scope for a take-home, not insane but definitely not a quick afternoon thing either.

Build a full comment system end-to-end: a frontend UI for browsing and posting comments, a backend API with full CRUD operations, and a database for persistence. Include a data model, API contract, input validation, error handling, and a README with run instructions and design notes.

“The scope felt manageable until I started thinking about all the moving pieces at once.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

Apr 2026

Did a technical round at Bobyard for a full-stack role, and the whole session was basically one extended problem about building a nested comment system. Decent problem, though I probably spent too long on the data model discussion before getting to actual code.

Design the data model for a nested comment system where comments can have replies, and replies can have their own replies.
How would you recursively render a comment tree with indentation based on depth?
Walk through how you'd handle adding a reply to any node in the tree, including updating the data structure and re-rendering.
Compare flat storage using parentId versus storing a fully nested tree structure. What are the trade-offs for fetching, rendering, and updating?

“I went with the flat parentId approach first, which felt natural, but they pushed me on what the data shape actually looks like per node.”

View Post