O processo levou 4 semanas. Fiz uma entrevista na empresa Grover.
Entrevista
Step 1 - HR call: in this step I had a very pleasant conversation with the recruiter. She spoke about the company, its mission and vision, and the position. I had time to ask a lot of questions too.
Step 2 - on site: I was invited to visit the office and discuss the technical and product side in further details. I had three meetings scheduled, one with a senior software engineer, one with a PO and the last was with the CTO. We discussed my technical skills as well as my previous experience.
Step 3 - take home task: I received a task to work on and submit in a couple of days. I finished it in 5 days which they were totally fine with it.
Step 4 - task discussion: this was a short call with the same senior software engineer to discuss the task and how I approached it.
Step 5 - meet the team call: this was the last call (also technical) where I spoke with the team that I was a candidate for. I spoke with the lead and two engineers who were very friendly and answered all the questions that I had about the role and the expectations from it.
Step 6 - offer.
Perguntas de entrevista [2]
Pergunta 1
What are you looking for in your new job/position?
Candidatei-me por meio de recrutador(a). Fui entrevistado pela Grover (Berlim) em jan. de 2026
Entrevista
The company provided a coding challenge in advance, but during the live interview the task was changed without prior notice. I was expected to work in a large unfamiliar codebase and implement backend functionality under significant time pressure.
The process felt disorganized from the start. The technical environment did not function as expected, APIs and requirements were unclear, and parts of the exercise appeared disconnected from the company’s actual technology stack. There was a noticeable gap between the hiring process and the engineering reality, which led to inconsistent expectations throughout the session.
More concerning was the lack of technical coherence during the discussion. Some fundamental aspects of the codebase and system design could not be clearly articulated when questions arose, which was surprising given the context of the interview and the seniority implied by the role.
Overall, the interview did not resemble a structured or rigorous technical evaluation. Candidates should be prepared for a improvised experience rather than a well-calibrated assessment.
Candidatei-me online. O processo levou 1 dia. Fui entrevistado pela Grover em fev. de 2025
Entrevista
The HR interview was unusually long and exhausting, stretching to almost an hour of relentless questioning about cultural fit, past experiences, and mandatory office days.
After reflecting on my interview, I'm confident I communicated effectively and professionally. Despite this, I was rejected before even getting the chance to take the technical assessment, which should be the true measure of a candidate's potential contribution. The stated reason was that they chose someone who could start sooner, but with multiple positions open, this explanation didn't seem genuine. It felt like the HR representative was acting as a gatekeeper, making decisions based on personal impression rather than objective qualifications.
Perguntas de entrevista [1]
Pergunta 1
Are you searching for an individual contributor or a leadership position?
How did you discover us and what made you apply?
What else are you looking for in terms of company culture when considering your next role?
Candidatei-me por meio de recrutador(a). O processo levou mais de 2 meses. Fui entrevistado pela Grover em jul. de 2021
Entrevista
I had only 2 interviews (HR, Pair Programming). After the last one, I didn't receive any feedback, so I asked for the status, but no one got me back.
Still don't know whether I've been rejected or not