I applied through college or university. I interviewed at EPAM Systems (Bengaluru) in Feb 2026
Interview
The recruitment process was conducted as a pool campus drive with participation from multiple colleges. The first round was an online assessment, which I cleared successfully. The second round was an in-person pen-and-paper coding test that began around 10:30 AM, and results were announced around 2:00 PM. Approximately 400 students appeared for this round, and around 30 candidates were shortlisted.
The pen-and-paper round focused more on object-oriented programming concepts rather than traditional DSA. Candidates were asked to design a system using abstraction and inheritance principles. After the written round, the shortlisted candidates proceeded to an in-person technical interview. The overall process was structured and competitive, with a strong emphasis on core OOP fundamentals and logical thinking rather than pure algorithmic problems.
I appeared for the interview in February 2026 in Bangalore. Based on what seniors had shared, earlier batches were typically asked more DSA-focused questions. However, in my case, the focus shifted more toward object-oriented design and abstraction concepts rather than traditional algorithm-based problems.
The overall emphasis was on OOP fundamentals, class hierarchy design, and clarity of implementation.
Interview questions [1]
Question 1
In the pen-and-paper round, all candidates were given the same problem statement. I am not entirely certain if this was the exact wording, but the core requirement was to design a system using abstraction and inheritance principles.
Specifically, I had to create an abstract class named Hospital, define abstract methods such as getDescription(), and declare the required variables. Then, I needed to create a Person class with a string variable name, extend it into a Patient class, and override the getDescription() method. Additionally, I was asked to implement simple logic such as retrieving the next patient based on priority.
The focus of the question was mainly on understanding abstraction, method overriding, class hierarchy, and applying basic low-level design concepts rather than solving a pure data structures problem.
one tehnical interview that focuses on your projects, REFRAMEWORK, debuging, selectors, SQL(asks you what select from * means and how you select from a table and how to give a price variable the 10% of price), regex ( asks particular element from a regex what it means aka ^)
Interview questions [1]
Question 1
one tehnical interview that focuses on your projects, REFRAMEWORK (how to use it ), debuging, selectors, SQL(asks you what select from * means and how you select from a table and how to give a price variable the 10% of price), regex ( asks particular element from a regex what it means aka ^)
I applied through a recruiter. I interviewed at EPAM Systems (Chennai) in Feb 2026
Interview
The first discussion was with HR, and he scheduled the first tech round with an interviewer who has 12+ years of experience in Frontend development. The first round was purely technical with advanced concepts in JS, React, security, and performance
Interview questions [1]
Question 1
Event loop
SOLID principles
Currying - sum(1)(2)() - implementation
Const Person = {
Name
Age
setName() => arrow
setAge: function()
}
console(Person.name)
console(Person.age)
Websocket, Polling
requestAnimationFrame()
RBAC, theme - context or store
Union, intersection
Git rebase, merge
Partial, omit
Testing library - jest, rtl
Directives, composition
Using ref - change button color
useHistory - maintain prev and next
array.map(a => a < 3)
React fiber
Prioritisation in react - how does it happen
ssr, nextjs
Liskov, IoC
Code review
Performance optimization - initial load 10s
Garbage collection
Memory optimization
Critical rendering path
when you use custom hook how would you maintain reference when its used across multiple components, something to do with useEffect
Proto and prototypal inheritance
Lifecycle hooks
React versions
Owasp top 10
Cors
Xss
How react handles xss
V8 engine - implementation