EPAM Systems Senior DevOps Engineer interview questions

I applied for a Senior DevOps Engineer role and found the process highly professional, though technically demanding. The technical interview lasted about 90 minutes and was conducted via a dedicated platform; the discussion was deep and focused on real-world scenarios involving GCP, Docker, and advanced CI/CD in GitHub Actions/ArgoCD and other pretty standard tools. I particularly appreciated the high level of professionalism from the interviewers and the subsequent transparency from the recruitment team, who provided detailed and constructive feedback outlining both my strengths and specific development areas such as mTLS security protocols and advanced GitOps workflows. Despite the well-managed process, I ultimately decided to decline the offer because the proposed remuneration was way below my expectations and does not align with current market standards for a senior-level position in this field. I would recommend the process to those seeking a technical challenge, but I suggest ensuring budget alignment early on. Even though I tried to align the budget with the recruiter and the technical feedback was positive, the final offer did not reflect what was initially discussed.

Entrevista extremamente mecânica, impessoal, mais de 90 minutos de puro questionário sobre diversos assuntos. Entrevistador de mau humor, nada cooperativo, só estava interessado em acabar logo com a entrevista. Perguntas muito específicas para avaliar áreas inteiras de conhecimento, sem interesse nas respostas do candidato além do que eles esperam. Live coding era extremamente básico mas envolvia ler disco e memória, sem qualquer auxílio de documentação e nem ajuda do entrevistador, se você não soubesse os métodos da biblioteca psutil de cabeça, era reprovado. Uma vez que você tinha aceitado fazer em python não havia como mudar para bash ou mudar o desafio.