Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      EverQuote

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de EverQuote | Empleos en EverQuote | Sueldos en EverQuote | Prestaciones en EverQuote
      Entrevistas en EverQuoteEntrevistas para el cargo de Quantitative Developer en EverQuoteEntrevista en EverQuote


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Quantitative Developer

      6 may 2018
      Candidato de entrevista anónimo
      Cambridge, MA
      Sin ofertas
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en EverQuote (Cambridge, MA) en ene 2018

      Entrevista

      Phone Screen (Nicest HR person), Technical Interview (Leetcode Easy), ANOTHER Technical Interview (Leetcode LOL (Easy) and SQL) After the HR screen, I was interviewed by an engineer. I was asked the valid parenthesis problem from leetcode. I solved it in the most efficient way, but was told that my solution was O(n^2) which was preposterous because i can see my time complexity in leetcode and it beat 90%+ of the submissions. He was almost a new grad(1yr exp), but was a manager......... moving on, he later realized it and he scheduled another tech screen. Another new grad-ish turned manager way too soon. First question fizz buzz lol. Second question, design a MySQL schema, so, I designed an elaborate schema that allowed them to obtain unstructured data AND structured data, but that was waaaay too much for her to understand(she assumed I did it wrong? idk), so, I did it in the most basic way, but couldn't remember the MySQL commands for averaging stuff (probably just AVG or something), so, I loaded the information into my python (using a MySQL cursor)code and gave her the answer. She tried correcting my python code, but then she realized it was fine. Rejection the following week. Please have more competent engineers do the interviews.

      Preguntas de entrevista [1]

      Pregunta 1

      FizzBuzz, Valid Parenthesis, Design SQL schema
      Responder pregunta
      3

      Otras evaluaciones sobre las entrevistas para el cargo de Quantitative Developer en EverQuote

      Entrevista para Quantitative Software Engineer

      22 feb 2018
      Candidato de entrevista anónimo
      Cambridge, MA
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en EverQuote (Cambridge, MA) en ene 2018

      Entrevista

      First I had a phone screen with the HR asking general questions. Afterward a phone screen with the CIO who did the interview while driving. It was very hard for me to understand what he was asking. After that, I was invited for a set of interviews on site. I had two sessions (instead of three, saying the next person had a crisis) both asked about randomness. Both asked me if I wanted to find a better solution to the problem or to write the code. Which I found uncool. This situation is hard enough, I don't think this is a decision the candidate should make. Although they gave me the feeling I was during great and tried to convince me that I would love to work there, I got a rejection the next day...

      Preguntas de entrevista [1]

      Pregunta 1

      Two question about randomness
      Responder pregunta
      1