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

      G-Research

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur G-Research | Offres d’emploi chez G-Research | Salaires chez G-Research | Avantages sociaux chez G-Research
      Entretiens chez G-ResearchEntretiens d’embauche pour Devops Engineer chez G-ResearchEntretien chez G-Research


      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 Devops Engineer

      23 mai 2021
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez G-Research (Londres, Angleterre) en sept. 2020

      Entretien

      Recruiter found me through a job site. I was mainly interested in the company because I had an interest in moving to London. My first interview was a conversation with the hiring manager to learn about the roles. That was followed by a timed hackerrank test which was fairly easy. After the hackerrank submission was accepted, I interviewed with two members of the team to go where we spent much of the time going over my hackerrank submission. While they were fairly nice, one of the interviewers (the one who did all of the talking) claimed that my Python looked like C++ and that he could tell I had spent many years as a C/C++ developer by looking at my code. I don't believe this is true since I try to write Pythonic code, and, while I've spent many years writing C/C++, I had also written a good amount Python at that point. He then claimed I could have written my code more compactly by using the "max" function to find the maximum length string in a list of strings. This is NOT true. He claimed that the "<" operator returns true if the length of the left operand is shorter than the right operand and that strings. This is NOT true. He claimed that strings are compared from right to left. This is NOT true. Pretty much every programming language performs string comparison by looking at the lexicographic ordering of each character from LEFT to Right. If what the interviewer claimed were true, string sorting would result in a completely unintuitive, non "dictionary" ordering. A week or so later, after not having heard back from the recruiter, I asked for an update and was told they're going with other candidates. The only feedback I got was the thing about my Python code looking like C/C++. Needless to say, it's quite frustrating to have my Python coding criticized by someone who clearly doesn't have a good grasp of Python. But I guess the Dunning Kruger effect also applies in the UK.

      Questions d'entretien [1]

      Question 1

      Easy hackerrank problems. I think there three problems.
      Répondre à cette question