Candidatei-me online. O processo levou 3 semanas. Fui entrevistado pela Smoobu (Berlim) em mai. de 2024
Entrevista
A waste of time and energy. The initial call with the recruiter was positive and smooth and I was invited to the next step. At the following interview, I did not manage to pitch myself because I was put under stress by the interviewer already as they had "a lot on schedule" and was rushed into answering the questions that were the most prepacked and standard questions from any HR manual you'd come across . Felt more like a psychological test than anything and it was a painful effort to even take it seriously. It felt like an offense to my intelligence and I asked the interviewer if their were serious or not. Then I was ghosted by the recruiter for weeks. Then I received an impersonal refusal email informing me that the company really valued my experience, so much so, that I did not get the job.
Candidatei-me online. O processo levou 1 semana. Fui entrevistado pela Smoobu (Berlim) em abr. de 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.
Perguntas de entrevista [1]
Pergunta 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
Candidatei-me online. Fiz uma entrevista na empresa Smoobu.
Entrevista
I was offended after this 10 minute phone call.
The office manager showed surprise at my accent, clearly hadn't read my resume, and actually left in the interview.
Only "question" or feedback from interviewer's side was "we need problem-solvers."