Infosys Salesforce Developer Interview Experience Round 1 2025: If you are planning to apply for the Salesforce Developer role at Infosys, here’s something that can really help you. I recently appeared for Round 1 of the Infosys Salesforce Developer interview, and I want to share my experience with all the questions I faced.
This round mainly tested my practical knowledge in LWC (Lightning Web Components), Apex programming, Trigger logic, and Salesforce Integration concepts. The questions were real-time scenarios — not just theory-based — and were aimed at checking how well I could think like a Salesforce developer.
LWC (Lightning Web Components) Interview Questions
The interviewer asked a few tricky questions on LWC behavior, event handling, and errors. These are the exact questions:
| Question | What It Checks |
|---|---|
| 1. What happens if two components on the same page import the same Custom Permission but one is deleted from the org? | Understanding metadata dependency and failure behavior |
| 2. What happens if you dispatch a custom event from a child LWC but the parent listens with the wrong case in the event name? | Knowledge of event bubbling and case sensitivity |
3. How does Promise.all() behave in LWC if one of the wired Apex calls fails with an unhandled rejection? | Error handling in multiple parallel promises |
💡 Tip: Be clear about how Promise.all() works and how event names are handled (they are case-sensitive!).
Apex Interview Questions
Next, I was asked questions on Apex logic, async behavior, and error handling. These were quite scenario-based:
| Question | What It Checks |
|---|---|
1. What happens if you call a @future method inside a batch finish() method and the batch fails halfway? | Behavior of async methods inside batch |
2. How does Apex handle Database.saveResult if you perform an insert with partial failures and don’t check isSuccess()? | Handling DML with partial success |
| 3. What happens if you enqueue a Batchable job inside a Queueable and the batch internally schedules another Schedulable? | Chaining async jobs and governor limits |
💡 Tip: Revise the Apex execution flow and how async chaining can hit platform limits.
Trigger / Asynchronous Logic Questions
These questions were based on real trigger behavior, exceptions, and governor limits:
| Question | What It Checks |
|---|---|
| 1. What happens if a trigger throws an unhandled exception in an after insert context? Are the records rolled back? | Transaction rollback understanding |
| 2. What happens if two triggers on the same object update the same field differently in before update context? | Behavior of multiple triggers in the same transaction |
| 3. What happens if you schedule 100 batch jobs in one transaction from a trigger? | Scheduling limits and best practices |
💡 Tip: Always know Salesforce governor limits and how unhandled errors affect the transaction.
Integration Interview Questions
The interviewer also tested my understanding of real-world API integrations and Named Credentials:
| Question | What It Checks |
|---|---|
| 1. What happens if you exceed the daily API request limit in Salesforce? | Handling API governor limits |
| 2. How can Named Credentials help simplify authentication in integrations? | Secure and easy authentication |
| 3. What happens if an external API you call returns a 500 Internal Server Error? | Handling failed callouts gracefully |
💡 Tip: Be ready to explain retry logic, Named Credentials setup, and error handling strategies.
My Personal Experience & Tips for Infosys Salesforce Developer Interview Experience Round 1 2025
Round 1 at Infosys was completely technical. There were no coding exercises, but I had to explain how I would approach each scenario.
Here’s what I noticed:
- Questions tested thinking and logic, not just bookish knowledge.
- The panel wanted to see if I understand Salesforce limits, execution order, and error handling.
- They preferred clear and structured answers with real examples.
If you’re preparing, focus on:
- LWC lifecycle and event communication
- Apex transaction handling and async patterns
- Trigger design principles and recursion handling
- Integration best practices using Named Credentials
Final Thoughts
This was my Infosys Salesforce Developer Interview Experience – Round 1, and I hope it helps you get a clear picture of what to expect. If you’re preparing for Infosys or any Salesforce Developer interviews, don’t just memorize answers — practice real-life scenarios and understand the “why” behind each concept.
All the best for your interview — you’ve got this!
Infosys Round 2 Salesforce Developer Experience:
Infosys salesforce selection process for experienced:
There will be total 3 Rounds in Salesforce developer role in Infosys Compnay:
- Technical Round
- Technical + Managerial Round
- HR Round
