← Back to Directory

Bobyard

Small

Screna has 7 Bobyard interview write-ups. The most reported round is the technical phone screen (3).

7 interview notes · updated Jun 2026

Bobyard·Software Engineer·Technical Phone Screen

Jun 2026
Live coding round at bobyard for a full-stack role, about 45 minutes, no talking through design or architecture, just build it. The problem was frontend-focused with a tricky bonus filter requirement that I didn't fully see coming.
  • 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, while non-matching siblings and their subtrees are hidden.

“The parentId part is straightforward if you've done tree rendering before, basically build a map of id to children and recurse.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026
Bobyard full-stack interview had me building out a nested comment system, which sounds straightforward until you're mid-explanation and realize you haven't thought hard enough about the storage trade-offs.
  • Design and implement a nested (threaded) comment system where users can reply to any comment, replies can have their own replies, and the whole thing forms a tree structure. Walk through the data model, recursive rendering, and how you'd handle adding a reply.
  • What are the trade-offs between storing comments in a flat structure using parentId references versus a fully nested tree structure, specifically around fetching, rendering, and updating?

“The data model part I got fine, parentId on each comment, children array, nothing surprising.”

View Post

Bobyard·Software Engineer·Take-home Assignment

May 2026
Bobyard sent over a take-home for a full-stack role, basically build a comment system from scratch with a frontend, a REST API, and a database. A few days to do it, no hard timer, which sounds relaxed until you realize that just means you have no excuse for cutting corners.
  • Build a full comment system end-to-end: a frontend UI for browsing and posting comments, a backend CRUD API, and a database for persistence. Include a README with run instructions and design notes.

“The scope felt reasonable at first but the 'end-to-end' part adds up fast.”

View Post

Bobyard·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at bobyard for a full-stack role, focused almost entirely on past work and the decisions behind it. Less about what you built and more about why, what you traded off, and whether you actually owned it.
  • Walk me through the highest-impact project you personally drove. What was the scope, what decisions did you own, and what was the measurable outcome?
  • Pick one or two flagship projects and go deep: what made the problem ambiguous, what trade-offs did you personally own, and what would you do differently?
  • How did you collaborate with others when the path forward wasn't clear? Give a specific example.

“This is the kind of question that sounds easy until you're mid-answer and realize you've been describing team work for two minutes without saying 'I' once.”

View Post

Bobyard·Software Engineer·Technical Phone Screen

May 2026
Bobyard full-stack interview that was basically two big scenario questions back to back. Less coding, more 'talk me through what you'd actually do on the job.' Felt like a senior eng check more than anything else.
  • A user reports the frontend feels slow. Walk through how you'd diagnose it and prioritize fixes.
  • A production bug just got reported. Walk through your entire runbook from triage to prevention.

“I started with the network waterfall and bundle size angle, which felt right, but I kind of fumbled the render-blocking resources piece.”

View Post

Bobyard·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at bobyard for a full-stack role. The question was one big sprawling prompt covering image generation infrastructure end to end, and they clearly wanted you to go deep on multiple sub-topics rather than just sketch a happy path.
  • 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 can take a long time, well beyond a normal HTTP timeout. How would you handle that in your design?
  • With multiple concurrent workers processing jobs, how do you guarantee that a single user's requests are processed in the order they were submitted?
  • If users are reporting that the frontend feels slow, how would you diagnose the problem and narrow it down to the specific bottleneck?

“I started with the happy path and drew out the obvious pieces, gateway takes the request, drops it on a queue, workers pick it up, result goes to object storage, CDN serves it.”

View Post

Bobyard·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Live coding round for a full-stack role at Bobyard, building on a take-home comment system. Thirty minutes, no real back-and-forth, just code.
  • Extend your take-home comment system to support sorting by timestamp and by userId, both ascending and descending. As a bonus, persist the user's sort preference across page refreshes using localStorage or URL query params.

“The core sort UI wasn't bad, wired up a controlled select and passed the sort key and direction down as props.”

View Post