Clipboard Health Frontend Engineer, repository take-home and debugging follow-up

Clipboard Health·Frontend Engineer·Reported Mar 2026
Take-home ProjectOtherRejectedHard

I went through a largely take-home-driven process that was somewhere between average and difficult. It usually started right after I applied and often ended with a rejection after little actionable feedback.

For the automated or online take-home, I cloned a provided repository, often involving Node.js, NestJS, React, or a backend API, and built logic to calculate results in the style of "top workers" or "top workplaces."

In several versions, the follow-up focused on debugging and assessment. They pointed out intentional issues or a backend "gotcha" bug, then asked me to reason through fixes and correctness. Some paths also included a call to explain my approach, optimizations, and how I’d extend the solution.

Many processes ended with generic or contradictory feedback, such as comments about "attention to detail" or claims that my implementation didn’t match the specification. Sometimes the details were ambiguous, and there were even claims that my output was wrong. I didn’t move forward, and my consistent impression was that the tasks took a lot of time while the feedback remained vague, sometimes because of repository or test quirks.

Location: United States. Overall feedback: Negative. Offer status: No offer.

Published

Curated and edited by PracHub

Discussion

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

Loading comments…

Interview at a glance

Company
Clipboard Health
Role
Frontend Engineer
Rounds
Take-home Project → Other
Outcome
Rejected
Difficulty
Hard
Date
Reported Mar 2026

Real Clipboard Health interview experiences

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

All 9 Clipboard Health interview experiences