I was first contacted by a recruiter who clearly explained the position and the remuneration, which I found very transparent and helpful before proceeding with any interviews. The first step was a 30-minute standard call with the recruiter, mainly to align my experience with the job requirements. The second step was a call with the Hiring Manager, which was an engaging discussion involving interesting questions and situational examples from my experience. The third session was a live coding exercise with a senior engineer from another team. I found this step somewhat unclear in terms of expectations and task definition. The main goal communicated was simply to get the task working, with less emphasis on best practices or code quality—which I delivered as requested. Eventually, I received feedback that they would not be proceeding with my application. I followed up to request more detailed feedback on what fell short of expectations, but I have not received a response to date. In my view, the role itself seemed more aligned with a Tech Lead position rather than an Engineering Manager role. Overall, the process was structured, but I felt that the expectations for the position did not fully match the typical scope of an Engineering Manager role.

I recently completed an interview process that consisted of four distinct stages: 1. Initial recruitment screening 2. Discussion with the management team 3. Technical assessment involving API integration 4. A leadership evaluation interview The first three stages were exceptionally positive. Each interaction was professional, constructive, and provided valuable insights into the organization's culture and technical expectations. However, the final interview stage presented a markedly different communication experience. The interaction was characterized by communication patterns that significantly deviated from the professional standards established in previous rounds. The interviewer demonstrated a communication approach that hindered meaningful dialogue, consistently interrupting and creating barriers to effective two-way communication. This experience raised questions about the consistency of interview methodologies and the importance of maintaining uniform communication standards throughout the recruitment process.