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 Senior Software Engineer 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. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      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 Senior Software Engineer

      4 juin 2024
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Clipboard en mai 2024

      Entretien

      A Complete Waste of Time! Immediately after submitting my application, I received an assignment via a platform called Woven, consisting of tasks I've detailed in the questions below. The assignment itself was straightforward. Notably, there was no human interaction until the first round of interviews, which was disappointing. Subsequently, I received a well-detailed document outlining their interview process—commendable clarity here. However, the process is excessively lengthy, entailing about seven rounds, including three coding interviews, one system design round, and discussions with various leadership roles up to an executive-level interview. The first round was marred by connectivity issues, and the interviewer seemed disinterested, which did not inspire confidence. One question involved Object-Oriented Programming (OOP), which was relatively simple. Although I admit to a minor error in my approach, the expectation to produce production-grade code within an hour, based on incomplete requirements, seemed unreasonable. In a professional setting, product specifications and engineering efforts are collaborative and clearly defined. If the intent is to mimic a realistic work environment, it should either be executed accurately or not attempted. This experience leaves me concerned that ambiguity in product requirements might be a regular issue at this company, and I consider my rejection a fortunate escape.

      Questions d'entretien [4]

      Question 1

      Woven Question 1 - Reviewing a pull request
      1 réponse

      Question 2

      Woven Question 2 - Add observations on possible causes of latency in a system
      1 réponse

      Question 3

      Woven Question 3 - Implementing a function to create billing amount for users based on the subscription and user data provided.
      1 réponse

      Question 4

      Coding Round 1 - Dimmer and Bulbs problem
      Répondre à cette question
      2

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Clipboard

      Entretien pour Sr. Software Engineer

      19 déc. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Clipboard en déc. 2025

      Entretien

      *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

      Questions d'entretien [1]

      Question 1

      given an api, seeded data with employees, workplaces, and shifts, implement 2 scripts to grab top 3 (requirements showed top = max shift count)
      Répondre à cette question

      Entretien pour Senior Software Engineer

      13 mai 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 3 semaines. J'ai passé un entretien chez Clipboard en déc. 2025

      Entretien

      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

      Entretien pour Senior Software Engineer

      31 oct. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 jours. J'ai passé un entretien chez Clipboard en oct. 2025

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Aggregate some data by querying APIs.
      Répondre à cette question
      2