The EPAM interview had three stages: an HR screening, a technical round with coding questions, and a managerial discussion. It took about two weeks, with clear communication but a rigorous technical focus.
Interview questions [1]
Question 1
Explain how you would design a scalable system for a high-traffic application.
After an initial conversation with the recruiter it was followed by a very easy technical interview, interviewer was friendly and overall a good experience. The process was short and they kept good and quick communication.
Interview questions [1]
Question 1
Basics of OOP and a some live coding to show familiarity with the language
I applied through a recruiter. I interviewed at EPAM Systems
Interview
I was initially contacted by an EPAM recruiter via LinkedIn. The first round was a screening call where we talked about my background, experience, and salary expectations.
The second round was a technical interview. It involved a mix of behavioral questions and many short technical questions related to the Cloud Support Engineer role. These questions covered a broad range of basic topics like cloud service models, networking, and Linux fundamentals. The format felt rapid-fire, with lots of brief questions rather than deep dives.
After the technical round, I was told that they had “decided to hold off on the position,” even though the job posting remained open, which was confusing and disappointing.
Another thing that stood out was the video call setup—they asked me to turn my camera on, but none of the interviewers turned theirs on. It felt one-sided and a bit uncomfortable, bordering on unprofessional.
Interview questions [1]
Question 1
They asked a mixture of behavioral questions and basic technical concepts relevant to the role. For example, I was asked about how I handle high-pressure situations when troubleshooting production issues, and also about fundamental topics like cloud service models, networking basics, and Linux commands.