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.
My first technical round ran close to an hour and felt very deep and fully hands-on. It stayed entirely in the Power BI ecosystem and the data engineering details around it. I talked through Power Query, pivot-style modeling, and what happens in the Power BI service, plus how external tooling fits into the flow. The discussion also went into how Fabric ETL pipelines are built, how CI/CD is handled, and how RLS and incremental refresh work in practice.
My process started after an internal EXL team screen, then moved through a multi-round technical flow. I had multiple technical conversations with the EXL side, and the later rounds shifted toward a client-facing format. The structure felt deliberate: early rounds were about fundamentals and problem-solving approach, and then it progressed into a more client-style deep dive.
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.
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.
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.
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.
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.
