Most of the interview was about management style and dealing with situations and stakeholders. Some technical questions about DDoS, TCP, Kubernetes, VM vs Docker, gitops, release process and SRE practices. More like quick and effective checks to know if the candidate knows her/his stuff.
LC medium but mostly solvable. Make sure you have good K8s and cloud knowledge.
They ask your priority what you are looking for and what's your expectation from them and according they shortlist and schedule interviews with your choice of company as per availability of open positions.
How did you make sure any issues before releasing any software updates/ deployment on production.
One of the most thought-provoking questions came during the technical round: “How would you design a self-healing system for a high-traffic payment infrastructure, and what metrics would signal true resilience?” It wasn’t just a design question—it was a test of mindset. I spoke about proactive anomaly detection using telemetry pipelines, a fallback architecture driven by service degradation levels, and the use of SLOs mapped to customer-facing impact metrics. But beyond the engineering, I emphasized my belief in building systems that carry empathy—for users, for developers, for the edge cases that often get ignored. That question stayed with me because it wasn’t just about code—it was about the philosophy behind reliability.
How would you write a buffered IO layer? When would you use it? What are the drawbacks of using it?
Quais seus pontos fortes e fracos?
Para você qual melhor forma de servir o Desenvolvedor
No specific question. Conversation only.
* How would you fix a problem with a live system?
Viewing 891 - 900 interview questions