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

      WTW

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur WTW | Offres d’emploi chez WTW | Salaires chez WTW | Avantages sociaux chez WTW
      Entretiens chez WTWEntretiens d’embauche pour Technical Lead chez WTWEntretien chez WTW


      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 Technical Lead

      23 janv. 2023
      Candidat à l'entretien anonyme
      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 WTW en nov. 2022

      Entretien

      I was introduced through a recruiter. The first stage was an hour and a half technical interview. It was a difficult interview, but I thought the questions that were asked were relevant for assessing technical ability, which was refreshing compared to many of the technical interviews I've seen from the industry lately. 45 minutes of the interview were dedicated to a live coding exercise, which I felt was less useful. The solution required a lot of complex knowledge of syntax in one specific language - things that could be easily referenced by any knowledgeable developer, but made the live coding rather slow. I expressed this during the exercise and they offered to give me a take home assessment in addition to it. I was intrigued by the position and very impressed by the attitudes of the interviewing team, so I accepted. The take home assessment stated that it should only take 2-3 hours, but it was a few years out of date. It took that amount of time just to get it started because the API it said to utilize no longer exists, and there were configuration errors due to more recent updates to .NET Core. The solution took around 8-10 hours in total. Once it was complete and uploaded to a public repository, they requested a second interview to discuss the code. The hour long interview went well but it was apparent almost immediately that none of the interviewer had actually examined the code prior to the interview, which was a little disappointing considering the time spent on it. They seemed impressed with the solution and asked a few questions that indicated they would be extending an offer, which they did within the next week. In the end, I accepted another offer, but I was really impressed with the team. I came away with the impression that they have built a good culture where it is safe to fail and ask questions, and the interviewers seemed genuine and kind - as opposed to many technical interviewers that try to outsmart candidates, they seemed legitimately interested in assessing technical aptitude. If they'd extended the offer prior to the take home assessment, I would very likely be working for them right now, but the lengthy process provided time for another company to swoop in. I can't stress enough how difficult that choice was because of how impressed I was by the genuineness of the interviewing team.

      Questions d'entretien [1]

      Question 1

      Q: What is the difference between class components and functional components in React? Q: What is a hook in React? Q: Manipulate strings to find words that are scrambled within them, and output how many times those words are found amongst all of the strings.
      Répondre à cette question