Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Algolia

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Algolia | Vagas da empresa Algolia | Salários da empresa Algolia | Benefícios da empresa Algolia
      Entrevistas da empresa AlgoliaEntrevistas do cargo de Customer Solutions Engineer da empresa AlgoliaEntrevista da empresa Algolia


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Glassdoor LLC. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Glassdoor LLC.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Customer Solutions Engineer

      7 de ago. de 2016
      Funcionário(a) sigiloso(a)
      San Francisco, CA

      Outras avaliações de entrevista de vagas de Customer Solutions Engineer da empresa Algolia

      Entrevista para Customer Solutions Engineer

      27 de jul. de 2016
      Candidato(a) sigiloso(a) à entrevista
      San Francisco, CA
      Nenhuma oferta
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me de outra forma. O processo levou 3 semanas. Fui entrevistado pela Algolia (San Francisco, CA) em jul. de 2016

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      Tell me about a time when you had to deal with a difficult client?
      Responder à pergunta
      Experiência neutra
      Entrevista com nível médio de dificuldade

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou mais de 1 semana. Fui entrevistado pela Algolia (San Francisco, CA) em jul. de 2016

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      What tools could be used to convert ES6 to more compatible Javascript?
      1 resposta
      1

      Entrevista para Customer Solutions Engineer

      26 de mai. de 2016
      Candidato(a) sigiloso(a) à entrevista
      San Francisco, CA
      Nenhuma oferta
      Experiência negativa
      Entrevista difícil

      Candidatura

      Candidatei-me online. O processo levou 7 semanas. Fui entrevistado pela Algolia (San Francisco, CA) em mai. de 2016

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 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
      Responder à pergunta
      2