The first call was a recruiter screening. Then I was given a take-home coding exercise, no time limit, and easy to implement. The next step was 1-1 virtual coding interview that lasted 70 minutes. First, I needed to extend an existing codebase that was calculating the payment for on-call engineers. I had about 15 minutes for this, and this was not the same code I was given at first. The remaining 55 minutes were about how I'd plan additional features, and product thinking, what new features I think should be added to this codebase.
After this, there are 3 more onsite calls.
Perguntas de entrevista [1]
Pergunta 1
The first coding question was about implementing validation for an on-call scheduling, and merging two on-call schedule lists, a list of standard schedule entries and a list of overrides.
The second coding interview question was a different codebase. I needed to extend a code calculating the pay by hour for each on-call engineer, the extension needed to read new pay rates from config files for holidays like new year and Christmas. Watch out for someone being on-call across different hours with different pay rates. They will tell you that it is more important that you explain the solution and that you arrived to a shared understanding, this is not true. If you don't implement the solution, you will fail.
Candidatei-me por meio de recrutador(a). Fui entrevistado pela incident.io (Londres, Inglaterra) em mar. de 2026
Entrevista
First stage was standard questions about the role, company, and my experience. The company also requires 3 days per week in the office, which was communicated during the process. The second stage was a take-home coding task to implement a solution and explain it via a Loom video. The task was described as a 1-hour exercise, but in practice it required significantly more time to complete properly. The scope of the task itself suggests it cannot realistically be completed within one hour if done properly, which makes the stated expectation misleading. Additionally, the 5-minute Loom constraint is not enough to clearly explain the codebase, decisions, and trade-offs, which feels misaligned with the expectations.
The recruiter reached out, I accepted the first stage video interview, they mentioned their clients, what they do, interview stages, etc. Few days later received an email the examples shared don't reflect their mindset compared to others. No specific examples mentioned.
