Clipboard Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 105 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Clipboard.
Clipboard
Software Engineer
Mid Difficult Positive experience No offer 5 rounds
Interview process
Take home Technical screen Technical screen Background check Offer
Interview formats
Coding Technical Behavioral
I was given a PR assignment and then had a follow-up interview. Then there was another PR assignment or a technical design document, and another interview. After that, I had a hiring manager interview. The final round was an interview with the Co-CEO. I'm currently at the first stage and just need to get others' opinions.
Confirmed questions2 questions
- What motivated your interest in joining Clipboard?
- Clipboard has experienced rapid scaling while maintaining profitability. From an engineering perspective, the primary technical challenge has been the platform's growth. What are your proposed solutions for this challenge?
Clipboard
Software Engineer
Entry Average Negative experience No offer 1 round
Interview process
Take home Background check
Interview formats
Coding
They sent me a link to a Hatchways async task. I completed the assignment, following all instructions, created the PR and submitted it. After about 2 days, I got an email saying my submission had 'significant gaps'. This made me question if the reviewer actually understood the task requirements. The only feedback was 'Areas where you can improve: • Attention to detail: your solution did not adhere to the specification laid out in the task.' I emailed back asking what specific requirement I missed but didn't get a reply. This leads me to believe they might not even review the assignment, and instead rely solely on the resume, rejecting candidates based on their profile regardless of the assignment's outcome.
Confirmed questions2 questions
- The assignment involved submitting a PR to implement scripts for fetching top workers and workplaces using the existing API.
- I was instructed not to alter the existing APIs unless a bug fix was necessary.
Clipboard
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding Technical
I received an automated invitation for a coding exercise, which they said would take around 25 minutes, but it actually took me about 2 hours because I documented and tested my solution. It was really ambiguous, and I couldn't ask any questions. After I submitted it, I got rejected with vague feedback: "Attention to detail: there may be more data on the running server than your solution accounts for." I had actually mentioned this possibility in my documentation, but because the task was so unclear, I didn't know what scale to prepare for. Should I have expected a hundred records or a billion? The solution for a billion would be very different from one for a hundred, so I played it safe. Apparently, that wasn't the right move. This company seems to rely too heavily on automation to validate their assumptions, and even their feedback reflects that.
Confirmed questions1 question
- Could you aggregate data by querying APIs?
Clipboard Software Engineer Interview Questions
Quoted word for word from Clipboard interview reports.
“Write a database query to perform joins, group data, and count unique values in columns”
Read reports →“Find the problem with a Rest API that is not returning the expected data and fix it.”
Read reports →“Can you design a bulb and switch system that can handle variable voltage?”
Read reports →“Can you create a function to calculate monthly billing based on subscription info and a daily rate?”
Read reports →“How would you get data from an API, group it, and then sort it in descending order?”
Read report →“Could you design a search field that provides suggestions, given that the backend response time will vary between 1 and 2 seconds?”
Read report →“What is the reason for using clipboard, and what are the challenges in scaling it?”
Read report →“Can you explain why clipboard is used and how it can be scaled?”
Read report →“Implement 2 scripts to retrieve the top 3 employees based on shift count, given an API and seeded data for employees, workplaces, and shifts.”
Read report →Formats, difficulty and experience
Across all 105 Clipboard interview reports.