Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Clipboard

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Clipboard | Offres d’emploi chez Clipboard | Salaires chez Clipboard | Avantages sociaux chez Clipboard
      Entretiens chez ClipboardEntretiens d’embauche pour Software Engineering Manager chez ClipboardEntretien chez Clipboard


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineering Manager

      21 mars 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Clipboard en févr. 2025

      Entretien

      Like others have mentioned, very questionable experience. Recruiter at Clipboard reached out to me on LinkedIn. After sending my resume and scheduling time he mentioned I would actually be talking to someone else but later said he was looking forward to speaking with me himself. The talk with the recruiter was totally one-sided, basically explaining the company and majorly emphasizing how everything they do is as async as possible. At the end I asked if there was anything she wanted to know about me or my background, but there wasn't. At no point did my past experience or motivations come up, which was odd for an initial screen. At times it was hard to tell if it was a real person I was even talking to. The next step was to submit a code review on a basic node/typescript API. One of the tips for success in the instructions was "you should come to this assessment with the mindset that the level of work that you may have done in the past or typically think of as acceptable may not meet our bar here", so that was a bit of a red flag. The whole thing took a few hours over one night. I left several comments on the PR with suggestions or required changes along with justifications, including business logic specific feedback. After 3 days I emailed the recruiter for an update and the next day got a generic automated rejection from a third person.

      Questions d'entretien [1]

      Question 1

      You are the Engineering Manager for the team that owns the backend service responsible for worker shift management. Your team is working on adding a new feature to your existing, in-use, production apps which will allow healthcare facilities to rate the job performed by the workers of the facility's shifts. Your task is to review the PR submitted by a member of your team to implement new feature requirements below, and provide them with concise, specific, and actionable comments, including a top-level comment with your general assessment of their work (e.g. approve the submission, recommend or request changes, etc.).
      Répondre à cette question
      2

      Autres retours d’entretien d’embauche pour un poste comme Software Engineering Manager chez Clipboard

      Entretien pour Software Engineering Manager

      29 juin 2026
      Candidat à l'entretien anonyme
      Denver, CO
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Clipboard (Denver, CO) en juin 2026

      Entretien

      I was contacted by a recruiter about the position and we scheduled a time to discuss within a few days of the cold call. I did my due diligence and checked the GD review on this company and was a little hesitant as there are many negative reviews about the interview process and, in particular, for this role. However, I'm feeling that the criticism I am reading wouldn't be something that bothers me so much, so I proceed to accept the call. The screen with the recruiter went well; I liked the mission of the org, the recruiter was pleasant and knowledgable and I seemed to be a good fit. We discussed the next phase of the interview, which was to review a technical design document and provide input with the simple instruction being: review this technical design document just as you would as an engineering manager. At this point, I haven't spoken with anyone except the recruiter so I have very little to go off of. I got into the spirit of it and poured over the 16 page technical design design document. I've been doing these technical reviews for years, so this felt very natural and I expected that it would have gone well. I kept all of my feedback constructive, asked questions, didn't prescribe solutions and was quite thorough. After 8 days I received an email notification that they would not be proceeding but without any feedback as to why. I replied requesting feedback on the review so as to understand what it is that is not aligning with their expectations or needs. I have not received a reply to this email. Additionally, and worth calling out, is a note in the rejection email that I found particularly offensive and disheartening. They thanked me for the time I invested in the process but also stated: "I just wanted you to know that we don't take the time you've spent with us lightly. We've spent sufficient time on our end as well, reading, debating, and regrouping." Which seems a curious move to make, creating a false equivalency between the time invested by candidates in the interview process to get a job and employers getting paid to perform their job when evaluating candidates.

      Questions d'entretien [1]

      Question 1

      Evaluate a technical design document for a systems architecture that can prioritize asynchronous email delivery from multiple vectors with unique SLAs while not exceeding a strict throughput requirement on a downstream SMTP server
      Répondre à cette question

      Entretien pour Software Engineering Manager

      3 juin 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Clipboard en avr. 2025

      Entretien

      Did the recruiter call and then was sent a PR review assessment. Like all the other reviews for this position, I didn't get past the PR review and was sent a rejection email from the recruiter with the exact message another person posted here. I wonder what exactly they're looking for cause it seems like no one has been able to get past that first stage. I called out the 2 missed requirements of the rating value range and not blocking workers from applying to shifts. Existing endpoints broken due to the changes. New endpoint added was also broken. Returning 500s when it shouldn't. Incorrect HTTP method used. OpenAPI docs not reflecting what was actually implemented. Blocked and requested changes on the PR due to how many things were wrong with it. Looking back, I think where I went wrong was not spelling out what exactly should change with code examples, i.e. instead of just saying they need to add validation to the rating field, write out the code for them and point out exactly where to add it.

      Questions d'entretien [1]

      Question 1

      Do a PR review on github
      Répondre à cette question