If you already write Java or support enterprise applications, SailPoint IdentityIQ (IIQ) development is one of the most direct routes into identity and access management. But "SailPoint developer training" means very different things on different course pages. Some teach the admin screens and call it development. This post lists what a developer-focused SailPoint course should actually cover, and how to check a syllabus before you pay.

What a SailPoint IIQ developer actually does

On a typical IIQ project, the developer:

  • Onboards applications: configures connectors, schemas, aggregation and correlation so identities and accounts match correctly.
  • Writes rules in BeanShell (Java syntax): correlation, customization, build-map, before/after provisioning and identity attribute rules.
  • Builds workflows: joiner, mover and leaver lifecycle events, access-request approvals and custom provisioning flows.
  • Debugs: reads logs, traces failed aggregations and provisioning, and fixes them without breaking production.
  • Deploys: moves configuration between DEV, TEST and PROD using XML exports and a build process.

A training course that skips any of these leaves you unprepared for the first week of a real project.

What SailPoint developer training should cover

Use this as a checklist against any syllabus:

  1. IIQ architecture and the object model: identities, links, entitlements, applications, rules and tasks, and how they relate in the database.
  2. Application onboarding: delimited file, JDBC and Active Directory connectors; schema design; aggregation tasks.
  3. Correlation: why accounts fail to correlate and how correlation rules fix it.
  4. BeanShell rules: writing, testing and debugging rules with the SailPoint API (SailPointContext, Identity, Link, QueryOptions).
  5. Roles and policies: business vs IT roles, assignment rules, separation-of-duties policies.
  6. Certifications: building access review campaigns and handling revocations.
  7. Lifecycle events and workflows: workflow XML, steps, transitions and variables; joiner-mover-leaver flows end to end.
  8. Provisioning: provisioning plans, before/after provisioning rules, handling failures.
  9. Reporting and quick links: custom reports and forms.
  10. Troubleshooting: log levels, common aggregation, correlation and provisioning errors, and how to read stack traces.

If troubleshooting and workflows are missing, the course is teaching screens, not development.

How to check a course before you enrol

  • Ask for the module list with hours per module. Rules and workflows need real time, not one session.
  • Ask how many years the trainer has spent implementing IIQ at clients.
  • Ask whether classes are live, and whether you can ask questions about your own code.
  • Ask how long you keep access to recordings. Most developers revise before interviews.
  • Be wary of "100% placement guarantee". Placement assistance (resume help, mock interviews, referrals) is the honest version.

How long it takes

For someone with basic Java and SQL, about 45 days of live evening classes plus regular practice is realistic to become comfortable with rules, workflows and troubleshooting. Recorded videos alone usually stop at configuration.

One option

IAM Careers runs a live online SailPoint IIQ course that covers all of the above across 15 modules in 45 days, including rules, workflows and a dedicated troubleshooting module. Classes run at 8 PM IST, Monday to Friday, in small batches, with recordings available for 2 years and a trainer with 15 years of IAM implementation experience. There is also a short guide on what a SailPoint developer course should cover.

This training is provided by IAM Careers and is not affiliated with, authorized by, sponsored by, or endorsed by SailPoint Technologies, Inc.