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 Graduate Developer 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 Graduate Developer

      16 avr. 2013
      Candidat à l'entretien anonyme
      Melbourne

      Autres retours d’entretien d’embauche pour un poste comme Graduate Developer chez Thoughtworks

      Entretien pour Graduate Software Developer

      18 oct. 2025
      Employé (anonyme)
      Singapour
      Offre acceptée
      Aucune offre
      Expérience neutre

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez Thoughtworks (Melbourne)

      Entretien

      I applied to this company twice. The first time, I applied it online between Jan and Feb 2013. I got an email a week before the Careers Fair said that I was rejected because I did not have enough skills. I sent back Thank You email and did not ask specific reason why I got rejected because I knew at the time TW would be attending the Careers Fair the following week. I came there and talked to one of them (incidentally the same guy who rejected me on my first application). I introduced myself to him and asked him why I got rejected. He expected me to write why I want to work at TW on my cover letter. He also asked me to send him another cover letter straight forward to his email instead of going through the online application. After I sent him my cover letter, the next morning he sent me code assessment with 3 problems. I chose the easiest one, Sales Taxes, because I wanted to try TDD (at the time I only learnt TDD for 2 weeks only). It took me 3 days to finish it. About 3 weeks ago, I got another email from him again about phone interview. I managed to pass this round last week. During this interview, he only focused about what do I know about TW. He started the question, "How do you find TW?". I mentioned about the 3 pillars and elaborate them more. This week, I have to do the Wonderlic test and Logic test. I still do not know whether I am going to pass those 2 tests or not.

      Questions d'entretien [1]

      Question 1

      So far, nothing.
      Répondre à cette question
      4
      Expérience positive
      Entretien moyen

      Candidature

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

      Entretien

      2024 interview process - Hackerrank - Pair programming round - pretty manageable, don't need to over prepare - Culture round - I was asked to share my thoughts about societal issues Interview process was smooth and quick

      Questions d'entretien [1]

      Question 1

      Pair programming round: If you had more time, is there anything you would like to change?
      Répondre à cette question

      Entretien pour Graduate Developer

      25 mars 2025
      Employé (anonyme)
      Pune
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Thoughtworks (Pune)

      Entretien

      The whole process was of 4 rounds, comprising of one OA , then a code pairing round then a technical interview, and finally HR.1 The interview was around one hour with 2 interviewers.

      Questions d'entretien [1]

      Question 1

      Questions were asked from everywhere, including computer science fundamentals, SQL , data structures, and projects. As I wrote react in my resume questions like how to implement lifecycle methods in function based components were asked.
      Répondre à cette question
      1

      Entretien pour Graduate Developer

      28 déc. 2023
      Employé (anonyme)
      Xi’anbian
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Thoughtworks (Xi’anbian)

      Entretien

      First round is culture round. They give you a topic in advance and you are going to give a 10-15 min presentation. After that there will be Q&A related to your topic. Second round is technical and pair programming. They gave you a repo for you to get familiar. The interviewer will ask a few theoretical question about programming and pair programming is related to the repo given. You will write about 3 new requirements together.

      Questions d'entretien [1]

      Question 1

      Some basic programming knowledge questions. During pair programming there will be questions about why are you writing the code like that.
      Répondre à cette question
      2