Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Algolia

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Algolia | Offerte di lavoro di Algolia | Stipendi di Algolia | Benefit di Algolia
      Colloqui di AlgoliaColloqui per Customer Solutions Engineer presso AlgoliaColloquio di Algolia


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      BMW Group
      4.0★Stipendio e benefit
      avatar
      Sinch
      3.7★Stipendio e benefit
      avatar
      Anton Tech
      3.6★Stipendio e benefit

      Colloquio per Customer Solutions Engineer

      7 ago 2016
      Dipendente anonimo
      San Francisco, CA

      Altre recensioni di colloqui per Customer Solutions Engineer presso Algolia

      Colloquio per Customer Solutions Engineer

      27 lug 2016
      Candidato anonimo a colloquio
      San Francisco, CA
      Nessuna offerta
      Offerta accettata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un'altra fonte. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Algolia (San Francisco, CA) nel mese di lug 2016

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Tell me about a time when you had to deal with a difficult client?
      Rispondi alla domanda
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto più di una settimana. Ho sostenuto un colloquio presso Algolia (San Francisco, CA) nel mese di lug 2016

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

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

      Colloquio per Customer Solutions Engineer

      26 mag 2016
      Candidato anonimo a colloquio
      San Francisco, CA
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 7 settimane. Ho sostenuto un colloquio presso Algolia (San Francisco, CA) nel mese di mag 2016

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 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
      Rispondi alla domanda
      2