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

      Smoobu

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Smoobu | Offres d’emploi chez Smoobu | Salaires chez Smoobu | Avantages sociaux chez Smoobu
      Entretiens chez SmoobuEntretiens d’embauche pour Senior PHP Backend Engineer chez SmoobuEntretien chez Smoobu


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

      9 avr. 2024
      Candidat à l'entretien anonyme
      Berlin
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Smoobu (Berlin) en avr. 2024

      Entretien

      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.

      Questions d'entretien [1]

      Question 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
      Répondre à cette question
      2