Exl Software Engineer interview typically runs 2 technical rounds. In this case, it was canceled 4 hours before the first round, with no reschedule and poor communication.
$105K
Avg. Base Comp
$138K
Avg. Total Comp
2
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Exl is looking for more than someone who can write code in a vacuum; the signal is whether you can operate comfortably inside the Salesforce ecosystem. The planned discussion centered on Lightning Web Components, Apex, async Apex, and Flows, with newer platform features like Agentforce also in the mix. That combination tells us the bar is less about generic software engineering and more about whether you can connect application logic to platform constraints and admin-style configuration decisions.
A recurring theme is that Exl seems to value practical Salesforce fluency over abstract theory. The mix of development topics and Salesforce Admin/configuration concepts suggests they want engineers who can move between building, extending, and troubleshooting on the platform without hand-holding. For candidates, that means the strongest impression will come from showing you understand how Salesforce pieces fit together in real business workflows, especially in consulting, finance, and insurance contexts where reliability and platform fit matter.
We also saw a clear process signal from the candidate experience itself: communication quality matters. The interview was canceled just hours before the scheduled time, with no real follow-up, and that left a strong negative impression. Even when the technical bar is the main focus, Exl’s candidate experience suggests that responsiveness and coordination are part of the story too, so any interaction that feels vague or improvised can color the whole evaluation.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Exl process.
The process was supposed to be two technical rounds, but it never really got that far. I had already prepared for the interview when it was canceled just four hours before the scheduled time, and the reason given was budgetary constraints. That was frustrating, especially because there was no real follow-up or attempt to reschedule, so the whole thing felt very poorly managed from a candidate perspective.
What stood out from the original interview plan was that the technical discussion was going to center on Salesforce work, especially Lightning Web Components and Apex. I was also expecting questions around newer Salesforce features like Agentforce, plus practical topics such as async Apex and Flows, along with some Salesforce Admin/configuration concepts. So the role seemed to be looking for someone who could handle both development and platform knowledge, not just pure coding. Unfortunately, the cancellation meant I never got to see how deep the rounds would go. Overall, it left a negative impression because of the last-minute change and lack of communication.
Prep tip from this candidate
If you’re interviewing for this role, be ready to discuss Lightning Web Components, Apex async patterns like Future, Queueable, and Batch, and newer Salesforce topics such as Agentforce and Flows. It also looks worth brushing up on Salesforce Admin/configuration basics, since those were part of the planned technical scope.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Exl
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Size of Joins | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Three Zebras | |
| Target Indices | |
| Duplicate Rows | |
| Type I and II Errors | |
| Swap Variables | |
| Your Strengths and Weaknesses | |
| Branch Sales Pivot | |
| Random SQL Sample | |
| Cyclic Detection | |
| Same Characters | |
| Integer String Addition | |
| Triangle as Binary Array | |
| Why Do You Want to Work With Us | |
| International e-Commerce Warehouse | |
| Stakeholder Communication | |
| Client Solution Pushback | |
| Justify a Neural Network | |
| Processing Large CSV | |
| Creating Companies Table | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders |
Synthesized from candidate reports. Individual experiences may vary.
The candidate was contacted and the interview was scheduled as part of a planned technical process. Based on the experience, there was no indication of an extensive screening phase before the technical rounds.
The first technical interview was expected to focus on Salesforce development work. Likely topics included Lightning Web Components, Apex, async Apex, Flows, and newer Salesforce features such as Agentforce, along with some Salesforce Admin and configuration concepts.
A second technical round was also planned, with the same emphasis on practical Salesforce platform knowledge and development skills. The process was canceled four hours before the scheduled interview due to budgetary constraints, and there was no rescheduling or follow-up.