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

      Thoughtworks

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Thoughtworks | Offres d’emploi chez Thoughtworks | Salaires chez Thoughtworks | Avantages sociaux chez Thoughtworks
      Entretiens chez ThoughtworksEntretiens d’embauche pour Senior Software Engineer chez ThoughtworksEntretien chez Thoughtworks


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

      6 sept. 2020
      Candidat à l'entretien anonyme
      Barcelone
      Offre refusée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Thoughtworks (Barcelone) en août 2020

      Entretien

      TLDR: A nice collective of people. They make you feel comfortable in every step. No tricky Computer Science question but real-world and market-geared ones. Lots of "cultural fit" questions and awareness of the candidate on topics as social equity and alike. The recruitment process is very long, it took 10 different meetings, spanning 1 month. Once I finally received the offer, I declined. First step: Screening interview. They want to know about my past experiences, salary expectations, notice period, etc... Duration: Around 30-40 minutes Second step: Technical chat with 2 developers; They asked me about the difference between OOP and FP, asked about the biggest challenge I have faced, how I develop tests, and if I use TDD. Duration: Around 1 hour Third step: A feedback from HR saying that the previous call was good and I have been selected to go to the next step. Duration: Around 20 minutes Fourth step: 1) Pair session with a developer. The key here is to solve a coding challenge with them. 2) Another pair session right after the previous one. I had to on-board the new developer, explaining the problem, and develop along with them. 3) A cultural fit interview that let you answer questions from different categories like "Ability to learn", "Team playing" and "Social awareness". It is a relaxed session of Q&A without any right answer. This step defines how much you are a fit for TW's culture. Duration: Around 4 hours Fifth step: 1) A chat with the project manager. Super relaxed, talked about previous experiences, what I was looking for in a team/project and again salary expectation. 2) Technical meeting with 2 other developers to talk about Software Development as a whole. Including previous experiences, how I dealt with problems I faced before, what I think about testing, what the team I am looking for is like, how do I deal with junior members and so on... Duration: Around 2 hours Sixth step: A call with the HR in charge of the recruitment giving feedback. In my case, I passed in all steps and received the offer via e-mail. Duration: Around 30 minutes Seventh step: I made a counteroffer, they analyzed and gave the best offer they could offer me. Since that wasn't aligned with my expectations, I declined the offer. About the offer: It was good in terms of social benefits, like meal budget, transport ticket, and learning budget. The deal-breaker to me was the salary. It was below the average for a senior position and even lower than the amount I was making in my previous company. My feedback for the company: Please review the salary bands for the engineering department, because even in COVID-19 times it was quite below what the other companies are offering. Also, I feel that the entire recruitment process could be optimized to be faster. For example, 2 meetings could have been e-mails. So in this regard, I think you can optimize the whole process to be faster for you and the candidate that most of the time can't afford to spend so much time interviewing but be sure to keep the balance so you still offer a great experience to the candidates and are sure you get the right one. Despite all, the TW recruitment process is still one of the best I've passed through. Very unique and kind.

      Questions d'entretien [1]

      Question 1

      How do you manage conflicts in a team?
      Répondre à cette question
      5
      avatar
      Réponse de Thoughtworks
      5y
      Thank you for taking the time to leave such a detailed and thoughtful review. We've put a lot of time and effort into creating a recruiting process that is candidate focused and enjoyable. While it is thorough and involves multiple rounds, we feel that it helps us hire future ThoughtWorkers who are truly excited to work here and embrace our culture and how we approach challenges. We appreciate your feedback about the length of the process and compensation; we've brought this feedback to our teams to take into consideration. Thanks again!

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

      Entretien pour Senior Software Engineer

      28 mars 2026
      Candidat à l'entretien anonyme
      Singapour
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via une autre source. J'ai passé un entretien chez Thoughtworks (Singapour) en févr. 2026

      Entretien

      When through HR, asked about mainly day to day on my current work and about agile methodologies. Also asked about my tech stack that I used on my current project

      Questions d'entretien [1]

      Question 1

      What techstack do you use for you current project?
      Répondre à cette question

      Entretien pour Senior Software Engineer

      4 déc. 2025
      Employé (anonyme)
      Chennai
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Thoughtworks (Chennai)

      Entretien

      Code pairining+2level of interview. Repo will be provided in all the oops languages and oops interview questions Code pairining+2level of interview. Repo will be provided in all the oops languages and oops interview questions

      Questions d'entretien [1]

      Question 1

      Architecture level of hotel management
      Répondre à cette question

      Entretien pour Senior Software Engineer

      24 nov. 2025
      Employé (anonyme)
      Singapour
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Thoughtworks (Singapour)

      Entretien

      Pairing: Work with an engineer on a small coding task to assess collaboration and problem-solving. Domain Modeling: Discuss and model a problem space to evaluate system thinking and design skills. Culture Fit: Conversational session to understand alignment with team values and working style.

      Questions d'entretien [1]

      Question 1

      They asked about the function you wrote and how you'd approach unit testing it using TDD.
      Répondre à cette question