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

      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

      Fresha

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Fresha | Ofertas de empleos en Fresha | Sueldos en Fresha | Beneficios en Fresha
      Entrevistas de FreshaEntrevistas para el puesto de Backend Engineer en FreshaEntrevista de Fresha


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Backend Engineer

      9 feb 2024
      Candidato de entrevista anónimo
      Londres, Inglaterra
      Sin oferta
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en Fresha (Londres, Inglaterra) en ene 2024

      Entrevista

      Got an initial screen with one of their internal recruiters who was really nice and was very helpful afterwards throughout the process. Next was an interview with the hiring manager. It was mostly a casual talk about my previous experience. They seemed nice and it went well. The next step was a technical interview which involved live coding in Elixir where I had to solve a LeetCode problem. The next step was a panel interview with 3 people. It involved 3 live coding sessions (LeetCode again) that had a mix of system design sprinkled in between. Unfortunately, I did not manage to pass this round, so I don't know what the next step would be. Overall, I'd rate this interview experience a 5 out of 10. I had a good experience during the initial stages. However, the technical interviews were a mess. I repeatedly asked what kind of topics would be covered during the live coding aspects. I specifically asked if it would be LeetCode. I was told that it would involve real-world code, so I had the impression that the coding session would involve something like fixing a bug on an existing system or pair programming to develop a feature. I went into the technical interview only to be blindsided when it turned out the live coding session was actually LeetCode instead of real-world code. When I managed to pass this round, I asked what the next interview would be about. I was told that there might not be live coding anymore which led me to believe that the next interview would be about system design. Once again, I was blindsided when it turned out to be 3 leetcode questions. While I did manage to solve them all, I wasn't able to get to the solutions immediately which I think was the reason why I got rejected. I also did pretty badly in their follow up questions because I wasn't able to recover fast enough from being blindsided. I think I would have performed better if I was informed properly about the structure of the whole interview process. If they wanted to do LeetCode, they should have just said so from the start instead of trying to be secretive about it. It was frustrating because I know the recruiter was doing their best to help me. It gave me the impression that the people doing the technical interviews were purposely misleading the recruiter, so I wouldn't be able to prepare myself properly.

      Preguntas de entrevista [1]

      Pregunta 1

      How HTTP works. LeetCode Easy problems on Strings and HashMaps using Elixir. LeetCode Easy problems on SQL (aggregation). Follow up questions on how to scale your solutions (system design).
      Responder pregunta
      2