Me postulé a través de una recomendación de un empleado. El proceso tomó 3 semanas. Acudí a una entrevista en Clipboard en dic 2025
Entrevista
Initial chat.
A take home project.
Two interviews over the course of the take home. In each one we discussed the work I had done offline then worked through an issue together. At the end of the first I was sent the updated requirements for the take home to complete before the second interview.
Final behavioural interview
Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Clipboard
Me postulé en línea. Acudí a una entrevista en Clipboard en dic 2025
Entrevista
*BEWARE*
1. As many people said, even if you answer correctly it will be rejected. They're either not hiring or there's something else going on.
2. The test setup isn't correct for the given scripts so this repo clearly isn't even being maintained. The design is fairly poor as well.
3. There's an unknown package installed. I worked in a sandbox and deleted it as soon as I was done
Preguntas de entrevista [1]
Pregunta 1
given an api, seeded data with employees, workplaces, and shifts, implement 2 scripts to grab top 3 (requirements showed top = max shift count)
Me postulé en línea. El proceso tomó 2 días. Acudí a una entrevista en Clipboard en oct 2025
Entrevista
You get what appears to be an automated invitation to complete a coding exercise, they claim that it'll take about 25 minutes, which seems too optimistic, it took me about 2 hours to complete as I documented and tested the solution. It's highly ambiguous and there's zero opportunity to ask questions.
After submitting the solution, I got a rejection with an ambiguous response "Attention to detail: there may be more data on the running server than your solution accounts for.". I specifically documented that this would likely be the case, however due to the ambiguity I didn't know what scale to expect. Should I expect there to be hundred records or a billion records? The solution for a billion records would be much different than a solution for a hundred records, therefore I chose the safe route. Apparently the safe route wasn't good enough.
They need to disambiguate the task a bit to ensure no one gets "lucky" with the right solution, I could have easily made the right choice, but it also could have just as easily been the wrong one due to the ambiguity.
This company appears to rely too much on automation to validate their own assumptions, even their own feedback on other response confirms that assumption.