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 Principal Consultant 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 Principal Consultant

      13 juin 2015
      Candidat à l'entretien anonyme
      New York, NY
      Offre refusée
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Thoughtworks (New York, NY) en mai 2015

      Entretien

      The interview process and the outcome mirrored the experience of a previous commenter who had applied for a Principal Consultant position (and posted a review on March 29, 2015). I applied online, and I got a positive response the very next day. The first conversation was with an internal TW recruiter out of the Chicago office. A very engaging discussion, and she was sure to capture my compensation requirements within the first few minutes. Next step was a discussion with a Technical Director, which is a pretty high-level title at TW. The director had to cancel at the last minute, and instead, I spoke to a Principal out of the San Francisco office. After successfully submitting my coding test and presentation, I was invited to come into the NYC office. There, I had a panel discussion about my presentation, a pairing interview, a short interview about my views on social justice (TW's Pillar 3), and then a logic test. The next week, I had a video debrief from the Managing Principal of the NYC office. A week later, I was invited to come into the NYC office to discuss an offer. There was a huge disconnect, and I ended up leaving the office very frustrated. As soon as I got home, I sent an email to the TW recruiter in which I said that I withdrew my name from the candidacy. My main complaints were: 1) During the first ten minutes of my initial interview with the TW recruiter, we narrowed down my salary expectations. Then, during the last meeting, where they told me that they were going to give me an offer, the Managing Principal asked what my salary requirements were, and after telling him, he said that he was not authorized to offer that much, and he would have to get special permission from a person who was a level or two higher. In my opinion, when you tell someone to come in to talk about the offer, you actually have a number in hand !!!! 2) At various times during the interview process, the interviews did not take place at the scheduled time. They have something wrong going on their with their internal clocks. The second interview I had was delayed twice because the recruiter in Chicago messed up on the times. The final debrief was delayed for two hours, resulting in a very awkward situation where they gave me ten minutes notice that they needed to have a video chat with me ... and I was sitting in my office at my current job. 3) I originally was slated to speak with one of the technical directors. He cancelled at the last minute, and instead, I spoke to a Principal out of the San Francisco office. The interviewer was on a cell phone at a nosy location, and it was difficult to communicate with the interviewer. In my opinion, when someone is being interviewed, they should be on a land line and in a quiet location. Especially if you have a senior-level candidate that you are speaking to. Basically, despite their proclaimed excellence at technology, the internal processes are not what you expect from a company that carries the ThoughtWorks name.

      Questions d'entretien [1]

      Question 1

      ThoughtWorks was pleasantly surprised when I volunteered to take the coding test. From what the recruiter said, Principals are not expected to take this test. They sent over a list of a few problems, and I chose one of them to do. This was the famous Kiwiland problem. I won't go into details, but it is easy to find this problem with a simple Google search. The problem was made a bit easier for me due to the fact that I was just starting to write a graph package for myself for a side project. So, I wrote some algoirthms around that core package that enabled me to solve the Kiwiland problem in a few hours. During the on-site pairing interview, I was asked to expand on the problem a bit. We did not get to the final answer, but the interviewers and I discussed ways that I could adapt my classes and algoirthms to solve their problem. Some good discussions went on, and I appreciated the comments of the interviewers. During the debrief, the feedback was that my code was not designed in a TDD-like fashion (which it wasn't), so TDD-designed code seems to be something that ThoughtWorks looks out for. ThoughtWorks also gave me a presentation to write up. They sent over a list of five business scenarios that they probably encounter frequently (ie: integration of disparate systems, scaling up a development org that is having issues, etc), and they asked me to choose one and give a presentation on it. I wrote up a brief PowerPoint, and during the on-site interview, a panel of three TWers grilled me on my presentation and philosophies. It was an engaging discussion, and a lot of it revolved around the use of MicroServices vs Monolithic apps, and how you would implement them at a customer site. In fact, many of their questions for a Principal-level applicant are geared around how you would deliver for tricky clients. At the on-site, two very young TWers asked me about my opinions on social justice and what I was passionate about. I was interested in devoting part of my time at TW to helping social causes, but it looks like a lot of that work is done out of their offices in India and Africa. They do have a bit of work going on in NYC with Unicef. The last part of the interview is their famous logic test, where you are basically given an array of integers and written directions, and you are asked to solve various problems. For me, the key was to take the written descriptions, translate them into simple C-like pseudocode, and "run" the code by hand. After the on-site, TW followed up with a one-hour debrief and final interview with the Managing Principal of the NYC office. Again, more questions about how I would handle tricky client situations.
      Répondre à cette question
      11

      Autres retours d’entretien d’embauche pour un poste comme Principal Consultant chez Thoughtworks

      Entretien pour Principal Consultant

      23 oct. 2024
      Employé (anonyme)
      Midwest City, OK
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Thoughtworks (Midwest City, OK)

      Entretien

      Series of interviews with various department heads with various focusses on how my engagement could leverage their expertise to win new logos. Each wanted to understand various scenarios and how I'd approach them.

      Questions d'entretien [1]

      Question 1

      Detail your methodology to acquire business in new Industries.
      1 réponse

      Entretien pour Principal Consultant

      4 avr. 2024
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Thoughtworks

      Entretien

      They were very professional in their email communications with me and followed up on a regular basis to try to schedule a call or interview with me once I confirmed my interest in their company

      Entretien pour Principal Consultant

      4 déc. 2022
      Candidat à l'entretien anonyme
      Bengaluru
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Thoughtworks (Bengaluru)

      Entretien

      Started with a case study that they wanted me to solve for them. After this, they would conduct the interviews with candidates. They provided a week's time to solve the case.

      Questions d'entretien [1]

      Question 1

      They asked for solution of a case study. After getting the solution they did not get back. No communication!!
      Répondre à cette question