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

      Smoobu

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Smoobu | Ofertas de empleos en Smoobu | Sueldos en Smoobu | Beneficios en Smoobu
      Entrevistas de SmoobuEntrevistas para el puesto de Senior PHP Backend Engineer en SmoobuEntrevista de Smoobu


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

      9 abr 2024
      Candidato de entrevista anónimo
      Berlín
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Smoobu (Berlín) en abr 2024

      Entrevista

      I applied for the position online in their official website and swiftly received an invitation for a discussion. The process was remarkably smooth and efficient. My initial interaction with HR consultant left a positive impression. The questions primarily focused on my career trajectory, reasons for selecting my previous company, and the motivation behind my decision to leave, with a particular emphasis on why I wanted to join their organization (approximately 20-30 minutes via Zoom). Following this, there were technical rounds with the Engineering team, Team lead and a senior developer working remotely from Poland, spanning around 2 hours via Google Meet. The team introduced themselves and delved into technical inquiries predominantly centered around backend development. Towards the end of the session, they provided a code snippet that required adjustment, which lasted for the final 15 minutes. Despite not advancing further in the process, I found the interviewers to be friendly, supportive, and technically adept. The atmosphere was relaxed, contributing to a conducive environment for meaningful discussions. Interview was on plain English only.

      Preguntas de entrevista [1]

      Pregunta 1

      Principles: KISS, DRY, and YAGNI principles and their relationship Command Query Responsibility Segregation (CQRS) based on my previous experience context Shared context-related code like the Singleton design pattern SOLID principles Loose Coupling vs. Tight Coupling, Inversion of Control mechanism Security: XSS and SQL injection handling, Auth handling security like use of Cookie HttpOnly Best practices for storing JWT shared keys (e.g., session storage or secure-flagged cookies) Testing: Unit tests: Testing state vs. testing interaction, their relation with the maintainability of the code Database: SQL: Different join types, optimizing slow MySQL queries Comparison between DB engines, mainly InnoDB vs. MyISAM Strategies for changing a DB field name in production without disrupting other long running processes (maybe discussing transactional differences between engines) Coding Challenge: Fixing a state test function without using PHPUnit, but with assertions The payload transformation encapsulated within a private function (which we need to test), also called by another log function which call logger->log, the logger was not injected rather created by new, so it need ot be injected as an interface (e.g., PSR LoggerInterface) and creating a concrete logger to output the tested payload and assert with the given input of the test assertion function and maybe others I forgot
      Responder pregunta
      2

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Motorola Solutions
      3.9★Remuneración y beneficios
      avatar
      Adobe
      4.1★Remuneración y beneficios
      avatar
      Turing
      3.6★Remuneración y beneficios
      avatar
      AVEVA
      3.8★Remuneración y beneficios