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

      Boost Insurance

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Boost Insurance | Offres d’emploi chez Boost Insurance | Salaires chez Boost Insurance | Avantages sociaux chez Boost Insurance
      Entretiens chez Boost InsuranceEntretiens d’embauche pour Senior Backend Engineer chez Boost InsuranceEntretien chez Boost Insurance


      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 Senior Backend Engineer

      5 mars 2019
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Boost Insurance (New York, NY) en févr. 2019

      Entretien

      I was contacted by a local third-party recruiter for the position of a Senior Backend Engineer with Boost Insurance in New York. I first had a 30-minute phone call with the hiring manager. I was called on time which is good. The conversation seemed informal, but don't let this fool you. Throughout my interaction with him, a candidate may be fooled into believing he is easygoing, but the fact is that he is looking to weed you out at every turn. The phone call covered my experience and my interests along with the expectations for the position. Note that they use Scrum. I asked the manager what he does himself, whether he is hands-on or not, and the answer I got suggested that he is not personally hands-on. I was then sent a 75 minute HackerRank challenge which I passed although I didn't solve it perfectly. I was scheduled for an on-site interview which lasted three hours. The hiring manager inadvertently made me feel uncomfortable for showing up a little early. I could've quietly waited, but instead I felt embarrassed for proactively showing up minutes before the scheduled time. I interviewed with the hiring manager, his boss, two engineers, and one remote engineer. I had numerous programming questions, a whiteboard service-design architecture test, and a database design test, with nothing out of the ordinary. The engineers all seemed good to work with. I was asked what I would do if I had more unplanned work than could reasonably be performed that week. This question didn't really make sense in a scrum setting. It was so obvious that they are looking to get a worker who would work free overtime, and they think that being a startup gives them this privilege. It was a red flag. The men's restroom at their office was uncomfortably small, but this is common at some startups startups in the area. The hiring manager took two references, both of which he spoke to. I trust my references to have given a positive recommendation. The hiring manager nevertheless then turned me down. This was burdensome to me and my references. It took a fair bit of effort on my part to extract feedback. It was that they were looking for someone who is not a strong personality, and that they already have enough strong personalities in the team. In summary, I think what they're looking for is someone who will put their head down, won't ask too many questions or make demands, and will regularly put in free overtime. To top it off, they want assurances that such a worker to stick around for many years. If you interview for this position, be prepared to be asked several trick questions about your working style that have little to do with your skills as an engineer.

      Questions d'entretien [4]

      Question 1

      In elections that use the ballot box system for voting, each voter writes the name of a candidate on a ballot and places it in the ballot box. The candidate with the highest number of votes wins the election. If two or more candidates have the same number of votes, then the tied candidates' names are ordered alphabetically and the last name in the alphabetical order wins. For example, votes are in the names ['Joe', 'Mary', 'Mary', 'Joe']. Each candidate received two votes, but Mary is alphabetically later than Joe, so she wins. Complete the function electionWinner in the editor below. The function must return a string denoting the name of the winning candidate. electionWinner has the following parameter(s): votes[votes[0],...votes[n-1]]: an array of strings representing the names of the candidates as voted by the ith voter.
      Répondre à cette question

      Question 2

      Build a system that needs to generate different insurance policy documents based on incoming policy data. It needs to first fetch policy data from a source API. For each policy data object it retrieves, it will need to create a new document utilizing the data from the policy object and a corresponding base form which is selected base on the 'type' of the policy. The policy object data needs to be merged with its base form (think 'templating') to create the final policy document. The system then needs to save multiple versions of that final form: PDF, Word Document and perhaps ACCORD XML one day. Each rendered document (PDF, Word, etc.) needs to be uploaded to AWS S3 and Google Cloud storage. Policy fields: id, type, customer, cov_limit, cov_start_date, cov_end_date, deductible. Form format: HTML file.
      Répondre à cette question

      Question 3

      We have a database table with insurance policies. This is managed by a service that exposes an API that our customers can use to create and modify policies. When a change is made to a policy, like for example the coverage limit being increased, we need to store both the old and the new revisions of the policy. The API needs to be able for any given time to return the state of the policy as it was on a given date. As an example, we have a 1 year renter's insurance policy starting January 1. On July 1, i.e. 6 months later, the policy (customer) decides to increase the coverage limit from $50K to $75K. We need to store the policy as it was before and after the change. How would you implement this? The backend is a relational database, but if you have other methods or data store types to solve this that you find to be better, feel free to use them. Columns: id, type, deductible, cov_limit, cov_start_date, cov_end_date, customer_id
      Répondre à cette question

      Question 4

      Explain these Python concepts: GIL, threading, multiprocessing, decorators, generators
      Répondre à cette question
      1

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Amazon
      3.7★Rémunération et avantages
      avatar
      Deloitte
      3.5★Rémunération et avantages
      avatar
      KPMG
      3.6★Rémunération et avantages
      avatar
      TP
      4.3★Rémunération et avantages