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

      Algolia

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Algolia | Offres d’emploi chez Algolia | Salaires chez Algolia | Avantages sociaux chez Algolia
      Entretiens chez AlgoliaEntretiens d’embauche pour Customer Solutions Engineer chez AlgoliaEntretien chez Algolia


      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 Customer Solutions Engineer

      7 août 2016
      Employé (anonyme)
      San Francisco, CA

      Autres retours d’entretien d’embauche pour un poste comme Customer Solutions Engineer chez Algolia

      Entretien pour Customer Solutions Engineer

      27 juil. 2016
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. Le processus a pris 3 semaines. J'ai passé un entretien chez Algolia (San Francisco, CA) en juil. 2016

      Entretien

      Overall, the interview process was very thorough. I got a chance to have a conversation with many different people across varying roles. Throughout the process, the recruiter was fully transparent about my progress and next steps. I had an 2 initial Skype calls with current CSEs, followed by a technical exercise and Skype call to review. The exercise consisted of creating a project using modern front-end technologies and the Algolia API. The final interview was a full day on-site that ended with an extemp presentation. Questions focused on technical, UX, and client communication skills.

      Questions d'entretien [1]

      Question 1

      Tell me about a time when you had to deal with a difficult client?
      Répondre à cette question
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Algolia (San Francisco, CA) en juil. 2016

      Entretien

      Met them at a job fair, and my contact from the job fair forwarded me over to the recruiter. The recruiter was very nice, but immediately sent me an email saying they weren't interested. I wrote them back asking for more info, as I have plenty of experience in this area, and she emailed saying that was actually a mistake and that she'd set me up with and interview. On the interview, I was expecting more of a 20 min phone screen or something, as it was my first contact with them really, but it ended up being a full hour call. I was kind of rushing the first half of the call, thinking I had limited time, but after I realized it was going to be an hour long call felt more comfortable and felt like I got to have a pretty good conversation with the interviewer. I was then asked to do a coding challenge, which almost felt intentionally vague, but it was a request that I build a front-end only autocomplete using their API. Arbitrarily, I needed to use SASS or LESS, and a build system like Gulp, and it had to be hosted on GH Pages. In addition to the coding challenge, I needed to answer a bunch of questions about pricing and their system. The coding challenge was a little annoying, as the expectation is that you'll learn their whole ecosystem, which is basically a complete waste if you don't get the job because it's pretty unlikely you'll need that knowledge again. In addition, they were pretty clear in the interview that you'd be helping to implement their code and building demos for clients, which means it could be overkill to use Gulp or something similar. Regardless, I made an autocomplete using Angular and their API. I probably could have made something organized a bit better, and definitely could have gone overboard with Gulp (I only used it for what seemed necessary on such a small site). Due to the vague instructions I ended up doing a full-stack solution first, then realized I needed to start from scratch and make it entirely front-end. I'd had really great experiences with their recruiter, but at this point I got a form email from someone I'd never heard of saying they were not moving forward (from a noreply email address) with absolutely no explanation as to what they didn't like in the coding challenge.

      Questions d'entretien [1]

      Question 1

      What tools could be used to convert ES6 to more compatible Javascript?
      1 réponse
      1

      Entretien pour Customer Solutions Engineer

      26 mai 2016
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 7 semaines. J'ai passé un entretien chez Algolia (San Francisco, CA) en mai 2016

      Entretien

      Initial call with recruiter, standard questions about history and experience. Had 3 followup skype sessions with existing team members over a period of about 3 weeks. These followup sessions were about getting to know the team and the types of problems they encounter daily. Be prepared for more technical question about the service and search in general. Most of the team members seemed genuinely focused on getting to know the candidate and establishing rapport, only one interviewer seem to be reading from a list of questions in a mechanical fashion. After these team sessions I was scheduled for another skype interview with a CSE team member and the VP of Engineering at 7:00am after initially suggestion an afternoon time. This was to review the completed technical challenge, so initially this started off with describing my process of approach and quickly devolved into a tag team style match of rapid-fire technical questions interspersed with general questions relating to problem analysis and solution improvement. After the last session I waited a full week for a response before emailing the recruiter again to ask about any feedback and shortly after received the "thanks but no thanks" boilerplate email.

      Questions d'entretien [1]

      Question 1

      Technical Test The goal of this test is to evaluate your ability to build a frontend application displaying an outstanding auto-completion menu. Objective: Build an Algolia-based auto-completion menu for e-commerce Instructions: Download the Bestbuy dataset used by our instant-search demo: data.json Imagine what would be the best auto-completion menu a end-user would have on an E-commerce website (both the UI & the UX matter) Implement a state-of-the art frontend application using at least: a general build system (Grunt, Gulp, ...), a CSS preprocessor (SASS, LESS, PostCSS, ...), and the AlgoliaSearch JS API client v3. Evaluation criteria: search experience: relevance, UI & UX quality of the code index schema Deliverable: create a Github public repository to host the code publish it using GitHub's gh-pages
      Répondre à cette question
      2