Real, anonymous reports from people who interviewed for Software Engineer at Clipboard, newest first and distilled into what to expect across the loop.
Get your personalized Clipboard Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After I applied online, the process kicked off with a take-home assignment delivered via an automated email. It asked me to work in their repo and produce API-based output around “top workers” and “workplaces,” essentially by cloning what they provided and following the instructions closely. It felt straightforward while I was building it, because I could run everything locally and see the expected results.
When I submitted, the turnaround was basically a silent rejection: a generic email with either no explanation or very shallow feedback like “attention to detail” / not adhering to the spec. A couple of times, the rejection claimed my script didn’t return correct results for the dataset, even though I could reproduce the correct behavior. I tried to reply for clarification, but replies were bounced or ignored, so I couldn’t tell what was actually wrong—whether the review process was automated, cursory, or based on something other than the code I turned in.
8 months ago
Average Positive United States
Right after applying, I didn’t really get the normal back-and-forth. I was sent a case study / coding exercise first, without a recruiter call or any real conversation beforehand. The task itself was wildly unrealistic in my view, and it was the kind of thing that would take hours to reason through even when you’re trying to be careful.
I eventually submitted and then basically heard nothing. The email flow and response pattern felt automated and opaque, and multiple parts of the setup raised red flags—like questionable repo/test setup details, including things that seemed like they weren’t maintained properly. One of the most frustrating moments was realizing that even when I did the work, there was no meaningful follow-up, no real feedback, and no confirmation of what the reviewers were actually looking for.
12 months ago
Easy Negative New York, NY
My process started with a recruiter touchpoint, then moved quickly into a timed, take-home screening. It was backend-focused and built around their st…
> 1 year
Average Negative Canada
After a recruiter touchpoint, I got sent a repo-based task by email with a short window to finish. There was no real conversation with anyone inside t…
> 1 year
Average Neutral United States
I went through a take-home style assessment first, with a short, timed window to complete it and submit work that led into an interview. The initial t…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Take-Home Assignment
Candidates typically start with a take-home coding assignment that involves working with the company's repository to produce specific outputs. The experience often feels impersonal and lacks clear guidance, leading to frustration over vague feedback and a lack of actionable insights post-submission.
Take-homeCoding assignmentFeedback
Interview Structure
The interview process generally includes a series of structured interviews following the take-home assignment, often focusing on reviewing the candidate's submitted work and discussing their thought process. However, many candidates report a disconnect between their performance and the final evaluation, leading to confusion about the decision-making criteria.
Candidates frequently express dissatisfaction with the communication throughout the process, citing a lack of meaningful feedback and follow-up after submissions. Many report receiving generic rejection emails without specific reasons, which contributes to a sense of disorganization and frustration.
CommunicationFeedbackRejection
Technical Focus
The interviews tend to emphasize technical skills, including coding and system design, with candidates expected to demonstrate their problem-solving abilities in real-time. While some find the technical challenges reasonable, others feel the expectations are misaligned with the prompts provided.
Technical skillsSystem designCoding challenges
Overall Experience
Overall, candidates describe the process as lengthy and often disjointed, with a lack of human interaction until later stages. Many leave feeling that their time was not respected and that the evaluation process was not transparent or fair.
Candidate experienceProcess lengthTransparency
Expectations vs. Reality
Candidates often find that the expectations set during the application process do not match the reality of the tasks and interviews, leading to a sense of being unprepared for the actual evaluations. This mismatch can contribute to feelings of disappointment and confusion regarding their performance.