SailPoint IdentityIQ — Interview Experience (2026)

Profile: IAM Engineer · SailPoint IdentityIQ · 3.8 years experience Outcome: Offer from EY

Sharing this because I found very little detailed material on what SailPoint IIQ interviews actually look like at this level. Everything below is what I was genuinely asked.

EY — Senior Security Consultant 1

Result: Cracked ✅ Package: 16.5 LPA Rounds: 3

Round 1 — Technical Interview (45 minutes)

Screen-share, and I was asked to write code live. Worth preparing for — it's very different from talking about code.

Topics covered:

• Application onboarding — mainly Web Services and JDBC applications
• Workflows and rules
• QueryOptions — writing filters and searches
• Role mining
• Certifications

The onboarding questions went deep. Not "what is a connector" but how you configure operations, schemas, correlation, and what you do when the data is messy.

Round 2 — Technical Manager Round (45 minutes)

This one was in person. The process: they assign you a point of contact, you travel to the office, and they arrange an interview loop on site.

Topics covered:

• Plugins — architecture, how they're built, what they can register
• My recent work — walked through what I'd implemented and why
• Write a JDBC provisioning rule — live coding again

Know the

ProvisioningPlan

ProvisioningResult

Offer letter was released after these two rounds cleared.

Round 3 — Client Interview (1 hour)

The hardest of the three. Roughly 35 questions in an hour.

This happened after the offer. Rapid-fire, broad, and much more operational than the earlier rounds — less "explain the concept", more "you're on our team, what would you actually do".

Every question I was asked

SQL and queries

1. SQL queries and syntax (general)
2. Access request queries
3. List of users with the same last name as a given user

Reporting 4. Details about reports in SailPoint — how to build them

Day-to-day and development 5. Day-to-day activities in SailPoint IIQ 6. How to develop a plugin in SailPoint

Web Services onboarding 7. Onboarding an application via Web Services 8. How to configure an endpoint operation 9. Quality control / testing for a Web Services integration 10. Once integrated in SailPoint, how do you do quality control within IIQ 11. What quality checks do you do on the provisioning side

Scale and operations 12. Challenges seen with 300,000 identities 13. If a test server goes unhealthy, how would you handle that 14. Upgrade path from 8.1 to 8.4 — what do you do 15. Do you have to rely on other teams during an upgrade 16. How to check the status of servers 17. What can you do in the Admin Console 18. What operations can you perform on servers in the Admin Console

Entitlements — troubleshooting 19. Reasons why entitlements may not be showing for a user 20. Entitlement visible in the catalog but not showing on the user — why 21. Write BeanShell to get an entitlement object from its ID 22. Write BeanShell to get all entitlements a given user has 23. Instead of

context.search

IdentityEntitlement

Provisioning troubleshooting 25. User requested access, the request failed, they weren't added to the AD group — how do you troubleshoot 26. Running a batch request without the "generate identity request" option — how do you track it

Logging and debugging 27. A developer added debug-level loggers, an issue occurred, but nothing appears in the INFO logs — what's missing 28. A task calls a rule directly with no workflow, and the loggers aren't printing — troubleshoot it

Java fundamentals 29. Difference between

final

finally

finalize

Certifications and roles 30. What do you call a certification entry in a manager review 31. Which role type gives the relationship between a role and its entitlements

Debug page and configuration 32. In the Debug page, which section gives entitlement information 33. Process for adding an additional attribute to the Identity object

Tasks 34. A refresh task failed — how do you know which users didn't get refreshed 35. A partitioned task failed on the very first user — how do you find the other affected users

What I'd tell someone preparing for this round

The client round was operational, not architectural. They wanted to know whether I could be dropped onto a live environment and be useful.

Three themes ran through it:

• Troubleshooting. Half the questions were "X isn't working, what do you do." Have a method, not memorised answers.
• Scale. 300k identities changes everything — partitioning, delta aggregation, task tuning, where the bottlenecks are.
• Operations. Admin console, server health, logging, upgrades. Things you only know if you've actually run IIQ rather than just built on it.

Also: plain Java still comes up.

final

finally

finalize