EXL Service Philippines Software Engineer Interview Experiences 2026
Real, anonymous reports from people who interviewed for Software Engineer at EXL Service Philippines, newest first and distilled into what to expect across the loop.
Get your personalized EXL Service Philippines Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My interview journey started with HR connecting to confirm my background and schedule a first virtual round. The call was designed to be straightforward, and the schedule window was about thirty minutes. After that, I went into two more rounds that were technical from start to finish.
Both technical rounds focused on Lightning Web Components (LWC) and Apex development, with questions tied to recent updates in the Salesforce ecosystem—new features and platform enhancements. There were also Salesforce admin-oriented questions that covered configuration concepts. On the Apex side, I was asked about asynchronous processing, specifically the differences and use cases behind future methods, queueable, and batch Apex.
8 months ago
Average Positive Pune
The interview I had was a system-design style technical round. I was asked to walk through a scenario involving a REST API, and the discussion covered a mix of foundational software topics and implementation details.
We touched on basic Python as well as data structures, databases, and SQL versus NoSQL tradeoffs. The round also went into serverless API implementation, including how to think about deployment and the role of things like an API gateway and a web server. It wasn’t just theory; I remember needing to describe how the pieces would fit together end to end.
11 months ago
Average Positive India
My first stage was an L1 technical round that focused on Dialogflow basics. I talked through intents, entities, how context is handled, and how to use…
12 months ago
Easy Positive Noida
My process was pretty lightweight and straightforward. There was an OA first with aptitude plus basic AI/ML questions, and it also included cloud and …
12 months ago
Average Positive Gurgaon, Haryana
The interview started with questions centered on my projects, and then it moved into a case-study style problem-solving segment. I was given puzzles t…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Rounds
Candidates can expect multiple technical rounds focusing on a variety of topics, including Python, SQL, and specific frameworks like Salesforce or .NET. The emphasis is often on practical application and problem-solving rather than just theoretical knowledge.
PythonSQLSalesforce
Client-Facing Evaluation
Some interviews include client-facing scenarios where candidates are assessed on their ability to communicate technical concepts and problem-solving approaches in a client context. This often follows initial technical evaluations.
Client interactionProblem-solvingCommunication
Behavioral and Managerial Rounds
Interviews typically include behavioral and managerial discussions that assess cultural fit, future growth potential, and how candidates handle challenges. These rounds often follow technical evaluations.
BehavioralCultural fitGrowth potential
Interview Structure and Flow
The interview process is generally well-structured, with clear stages that progress from screening to technical evaluation and finally to HR discussions. Candidates should be prepared for a sequential format that builds on previous rounds.
Structured processSequential roundsClear stages
Focus on Practical Skills
Interviews often prioritize practical skills and real-world application over rote memorization, with scenarios designed to test understanding and reasoning under pressure. Candidates should be ready for hands-on coding and problem-solving tasks.
Candidates may encounter a wide range of topics during technical evaluations, from basic concepts to advanced system design and architecture discussions. This diversity requires a broad knowledge base and adaptability.