Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

8 stories

Likes earn the author +10 XP for the first 3 likes each day

EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer conflicting-rounds interview experience

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…

RejectedTechnical Screen0
EPAM IndiaQA Automation Engineer
Reported Jul 2026

EPAM India QA Automation Engineer interview: technical breadth and delays

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…

In progressTechnical Screen0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview: Spring Security, tracing and Python internals

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…

Technical Screen0
EPAM IndiaQA Engineer
Reported Jul 2026

EPAM India QA Engineer interview: Python automation and practical coding

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…

Technical Screen0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview: LRU cache, technical rounds, and canceled follow-up

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…

No response0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview: technical assignment, stack questions, and project availability

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…

Online Assessment0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview with Python deep dives and an unaccommodated emergency

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,…

Rejected0
EPAM IndiaSoftware Engineer
Reported Jul 2026

EPAM India Software Engineer interview with Python, SQL, cloud, and system design rounds

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…

RejectedOnline Assessment0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP