Katkat

real interview stories, told over a cup of tea ♡

EPAM India Interview Experiences

3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.

3935
Experiences
857
Companies
532
Offers

8 results

  • EPAM India QA Automation Engineer interview: technical breadth and delaysEPAM India · QA Automation Engineer · Technical Screen · Jul 2026
    In progress

    The recruiter call went well. After that, though, the process became a long wait. I heard nothing for about two weeks, followed up by email and LinkedIn, then waited another week for a reply saying the recruiter was waiting on the hiring team. I followed up again about a week later, and the technical interview was finally scheduled almost a month after the first call. That interview covered Java…

  • EPAM India QA Engineer interview: Python automation and practical codingEPAM India · QA Engineer · Technical Screen · Jul 2026

    After the recruiter call, I had a technical screen focused heavily on Python and automation thinking. I discussed lists, decorators, generators, and the difference between iterators and generators in real code. They asked about PyTest fixtures, then moved into automation framework design and how I would structure it end to end, including CI/CD pipeline considerations. The coding portion was pract…

  • EPAM India Software Engineer conflicting-rounds interview experienceEPAM India · Software Engineer · Technical Screen · Jul 2026
    Rejected

    The process felt drawn out and wasteful. I had cleared two technical rounds, and HR scheduled a project interview. After that, HR told me I had cleared it and only needed a final managerial round. The managerial round felt disorganized. The manager did not seem to understand the project I was being considered for and asked questions that did not fit what I expected from the earlier stage. HR late…

  • My process stretched across many rounds and felt heavy from the start. I had several technical and client-facing sessions with professional interviewers, including positive feedback from one client discussion. I was surprised by how long the process took and how many people I spoke with. The difficulty came from deep-dive topics rather than basic problem solving. I got Python questions on slices,…

  • EPAM India Software Engineer interview with Python, SQL, cloud, and system design roundsEPAM India · Software Engineer · Online Assessment · Jul 2026
    Rejected

    The process started with a timed online assessment covering coding, programming, logic, and problem solving. After I cleared it, the recruiter moved me forward. The next stages were straightforward and reasonable. I first had an HR-style conversation where the interviewer was helpful and explained what the company wanted. The technical interviews matched my stack rather than relying on obscure Le…

  • My EPAM process was assessment-heavy. It started with an OA covering aptitude, OS, computer networks, and coding. Next came a pen-and-paper coding test in an auditorium, where I worked on an LRU cache problem. Then there was a group discussion where the evaluator let us choose the topic. After that came technical interviews on DSA, DBMS, OS, CN, and more coding, followed by HR. It was not one con…

  • EPAM India Software Engineer interview: Spring Security, tracing and Python internalsEPAM India · Software Engineer · Technical Screen · Jul 2026

    After the recruiter stage, I had a technical interview of about ninety minutes that went deeply into Spring and distributed systems. I discussed Spring Data JPA, Kafka, Java 8 functional interfaces and Spring Boot. For microservices, I explained the architecture, how services communicate and how security works. JWT questions went into detail: what a token is, how a service validates it, what happ…

  • My EPAM process began with a technical assignment rather than an immediate interview. I spent a lot of time on it, and after submitting successfully, an interview was scheduled. The process then became more typical: recruiter contact, a technical session, and a manager conversation. The technical content was mostly stack-aligned instead of unusual puzzles. I had linked-list questions, including b…