Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Algolia

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Algolia reviews | Algolia jobs | Algolia salaries | Algolia benefits
      Algolia interviewsAlgolia Customer Solutions Engineer interviewsAlgolia interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Top companies for "Compensation and Benefits" near you

      avatar
      BlackBerry
      3.6★Compensation and benefits
      avatar
      Grafana Labs
      4.1★Compensation and benefits

      Customer Solutions Engineer Interview

      7 Aug 2016
      Anonymous employee
      San Francisco, CA

      Other Customer Solutions Engineer interview reviews for Algolia

      Customer Solutions Engineer Interview

      27 Jul 2016
      Anonymous interview candidate
      San Francisco, CA
      No offer
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I applied through other source. The process took 3 weeks. I interviewed at Algolia (San Francisco, CA) in Jul 2016

      Interview

      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.

      Interview questions [1]

      Question 1

      Tell me about a time when you had to deal with a difficult client?
      Answer question
      Neutral experience
      Average interview

      Application

      I applied through a recruiter. The process took 1+ week. I interviewed at Algolia (San Francisco, CA) in Jul 2016

      Interview

      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.

      Interview questions [1]

      Question 1

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

      Customer Solutions Engineer Interview

      26 May 2016
      Anonymous interview candidate
      San Francisco, CA
      No offer
      Negative experience
      Difficult interview

      Application

      I applied online. The process took 7 weeks. I interviewed at Algolia (San Francisco, CA) in May 2016

      Interview

      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.

      Interview questions [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
      Answer question
      2