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

      Whalar

      ¿Esta es tu empresa?

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Whalar | Ofertas de empleos en Whalar | Sueldos en Whalar | Beneficios en Whalar
      Entrevistas de WhalarEntrevistas para el puesto de Senior Backend Engineer en WhalarEntrevista de Whalar


      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. Indeed, Inc. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Indeed, Inc.

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

      11 sept 2025
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva

      Otras opiniones sobre las entrevistas para el puesto de Senior Backend Engineer en Whalar

      Entrevista de Senior Backend Engineer

      12 sept 2024
      Empleado anónimo
      Tallin
      Oferta aceptada
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Whalar en jun 2025

      Entrevista

      The recruitment process was clear, well-structured, and very human. From the first call, I felt supported and informed about each stage. I especially valued the meetings with the team, which gave me the chance to exchange ideas and see how we could work together.. There was also a meeting with the CTO, which was also valuable to grasp a good overview of the big picture The interviews were focused yet relaxed, allowing me to express myself comfortably. Communication was smooth, and the recruiter and team always made time for my questions. Overall, it was a good process The technical assignment was quite long and required significant time and effort, so future candidates should be prepared to invest patience and dedication in completing it

      Preguntas de entrevista [4]

      Pregunta 1

      About PHP, Symfony, tooling, etc. Questions related to PHP ecosystem
      Responder pregunta

      Pregunta 2

      Domain-Driven Architecture concepts, also Clean Architecture
      Responder pregunta

      Pregunta 3

      About automated testing, like unit tests or mutation testing
      Responder pregunta

      Pregunta 4

      About technology like RabbitMQ (queue systems) or Elasticsearch
      Responder pregunta
      1
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en Whalar (Tallin) en jul 2024

      Entrevista

      The interview process consists of 4 steps: HR Interview: The HR representative was professional and efficient. She asked about my background, interest in the company, and some standard technical questions. Her approach was structured and clear, which made the interview smooth. CTO Interview: The CTO is highly experienced. He began with a few behavioral questions to assess my level, followed by logical and technical questions. His style is hard to define because it feels more like a casual conversation about technical topics rather than a formal interview, which made the experience enjoyable. Head of Backend Interview: The Head of Backend is extremely knowledgeable. His questions were mostly about software architecture rather than specific programming languages. He was more focused on understanding my development approach, problem-solving abilities, and critical thinking. Home Assignment: They provided a PDF outlining a project in PHP. Since my experience is mostly in Java, I kindly requested to use Java, and they were flexible in allowing that. In fact, the company uses multiple languages, including PHP, Python, and Go. Overall, the interview process was smooth and efficient. The HR was very responsive, with no delays and prompt communication at each stage. The CTO and Head of Backend were both very knowledgeable, and they don't expect you to have all the answers or answer every question perfectly. If you're unsure of something, you're welcome to skip the question.

      Preguntas de entrevista [1]

      Pregunta 1

      I have an NDA, so can't share any questions
      Responder pregunta
      1

      Entrevista de Senior Backend Engineer

      13 may 2024
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 2 meses. Acudí a una entrevista en Whalar

      Entrevista

      Whole process is online and it goes like this: - Call with the Recruiter, where she asks some technical questions based on template - Hiring manager call (with CTO): It is a casual friendly technical discuss, that does not feel like an interview, it was not like other interviews I had in the past. - Home assignment (A well-thought task to highlight competencies) - Technical Interview (To challenge the applicant based on the assignment)

      Preguntas de entrevista [1]

      Pregunta 1

      They asked why did I make a specific decision in my code, and how could I improve it.
      1 respuesta
      1