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

      Block

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Block | Offres d’emploi chez Block | Salaires chez Block | Avantages sociaux chez Block
      Entretiens chez BlockEntretiens d’embauche pour Software Engineer chez BlockEntretien chez Block


      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 Engineer

      17 mai 2012
      Employé (anonyme)
      San Francisco, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Block (San Francisco, CA) en mai 2012

      Entretien

      My first contact was with a recruiter, who was a bit disorganized - he missed our first phone call due to meeting schedules, a sign of how busy things are at Square. After some chitchat, he scheduled a Skype interview with an engineer. The Skype interview was fun, actually. Square has an Evernote-like online wordpad, on which the interviewer and I wrote code. The task was to implement a function from the C standard library, going through several iterations. The interviewer was also a bit disorganized, but was thoroughly pleasant and engaged throughout the hour-long process. The interview went well, and within a few hours the recruiter contacted me to set up an in-person battery of interviews for the next week. The in-person interviews took place at the main office in San Francisco, which is thoroughly modern and attractive. A series of 6 different interviews ensued, with a roughly equal mix of 'discussion' (read: whiteboarding) interviews with pairs of Square employees and pair-programming with single interviewers. The discussions ranged from in-depth discussions of system architecture to sketching out solutions to given problems. There was a pleasant lack of 'academic' challenges in the discussion phases. The pair programming exercises ranged from academic to practical, but the experience was good. The engineers were pleasant, and I never felt pressured or judged (despite the fact that an interview is, by definition, an exercise in judgement). After the formal interviews, I was told immediately that an offer would be made. I was introduced to some engineers and had dinner with one. A formal offer was made the following morning. On the whole, the hiring process was an odd combination of relaxed and rapid. I liked everyone that I met, had interesting discussions and challenges, and the whole process took 12 days - a record in my experience.

      Questions d'entretien [1]

      Question 1

      Given an architecture, describe possible approaches to minimizing latency and downtime.
      Répondre à cette question
      10

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

      Entretien pour Software Engineer

      16 mars 2026
      Employé (anonyme)
      Melbourne
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Block (Melbourne)

      Entretien

      Inital take home, followed by extension interview, followed by a coding challenge, followed by system design interview. The whole process took 3 months! The interviewers are usually really nice and want you to do your best.

      Questions d'entretien [1]

      Question 1

      Design an end to end banking system
      Répondre à cette question

      Entretien pour Software Engineer

      6 févr. 2026
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Block (New York, NY)

      Entretien

      The interviewer was nice, and he is friendly and willing to give hint, the question has 2 follow-ups, it was hard to complete in time. The question was not a typical LeetCode

      Questions d'entretien [1]

      Question 1

      talk about my past experience
      Répondre à cette question

      Entretien pour Software Engineer

      14 août 2025
      Employé (anonyme)
      San Francisco, CA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Block (San Francisco, CA)

      Entretien

      Phone screen and then a full day of interviews. 3 pair programming challenges, a system design review and a prior experience interview. There was also an onsite lunch with a person from the company.

      Questions d'entretien [1]

      Question 1

      To design a hotel booking system. Pick any part (backend, frontend, database, api etc) and deepdive into that, explaining the decisions along the way.
      Répondre à cette question