J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez EPAM Systems (Pune) en juill. 2021
Entretien
Initial Interview: Discuss qualifications and role fit. Technical/Skill Assessment: Complete tests or tasks related to the job. Additional Rounds: Meet various team members and stakeholders. Behavioral Interviews: Discuss past experiences and problem-solving skills. Panel Interviews: Face a group of interviewers. Assessment Centers: For leadership roles, with exercises. Reference Checks: Contact your references. Final Interview: With top executives, if applicable. Offer and Negotiation: Receive and negotiate the job offer. Onboarding: Prepare for your first day and orientation. Remember, the specific process may vary by company and role.
J'ai passé un entretien chez EPAM Systems (New York, NY)
Entretien
Great step by step process and timely response. They shared the feedback wat went well and their expectations and areas to improve etc… interviewer basically test coding, logical thinking and fundamentals of core skills
J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez EPAM Systems (Bengaluru) en oct. 2025
Entretien
One round, kept asking unnecessary questions, expecting asking questions on theory, they are looking for parrots who can memorize each and every fancy jargon on the internet related to software engineering
Questions d'entretien [1]
Question 1
YAGNI, DRY every fancy jargon on internet Test pyramid, AAA pattern
J'ai postulé en personne. Le processus a pris 2 jours. J'ai passé un entretien chez EPAM Systems en mars 2025
Entretien
I received a call from a recruiter and had an interview scheduled with the lead. However, I'm not sure if they are actually hiring. The interview lasted 1.5 hours, and in the end, he said my approach was unsuitable for their requirements.
He asked basic theoretical questions, like "operator overloading" and constructors in Python, along with a request to write a design pattern, which I did. He also asked me to solve a few Python coding problems. I provided solutions covering all edge cases with O(n) complexity, but instead of appreciating it, he seemed insecure about how I was able to solve them.
Despite answering all his questions and solving the problems correctly, he was not happy. It felt like he was unwilling to accept my approach just because it exceeded his expectations. If I wasn’t suitable for the role, why conduct a 1.5-hour interview in the first place? Interviewers should encourage strong solutions rather than dismissing them.