The short answer: if you're optimizing for the next 5-10 years of your career rather than the next 12 months, ISC is the right direction. SailPoint's investment signals, the direction of new enterprise IGA implementations, and the industry's move toward cloud-native governance all point the same way. Your 8 years of IIQ depth isn't wasted — it's the foundation that makes your ISC transition faster and more credible than someone starting fresh.

The longer answer requires understanding what the IIQ and ISC job markets actually look like right now and where they're heading.

The Current IIQ Job Market Reality

IIQ is not going away. SailPoint continues to support it, large enterprise customers who have invested years in IIQ implementations are not migrating on a short timeline, and the maintenance and support demand for existing IIQ environments will persist for years. There is a real job market for experienced IIQ engineers.

The characteristics of IIQ-focused roles:

Maintenance-oriented work at incumbent customers. The majority of IIQ demand is in organizations that already have IIQ implemented and need experienced engineers to maintain, extend, and troubleshoot existing configurations. This work is technically challenging and well-compensated, but it's maintenance work rather than greenfield architecture work.

Declining new implementation demand. New IIQ implementations are increasingly rare. SailPoint's sales motion is ISC-first, and organizations evaluating IGA for the first time are being directed to ISC. The new implementation project work — which typically commands higher rates and offers more interesting technical challenges — is shifting to ISC.

Migration project opportunities. There is a near-term wave of IIQ-to-ISC migration projects that requires engineers who understand both platforms. Your 8-year IIQ foundation is specifically valuable here because migrating effectively requires understanding what the existing IIQ implementation is doing and how to replicate or improve it in ISC. This migration work will be significant for the next 3-5 years and represents an opportunity that pure ISC engineers without IIQ depth can't fully capture.

The ISC Job Market Reality

ISC is where SailPoint's development investment is concentrated, where new customer implementations are happening, and where AI-enhanced IGA capabilities (autonomous access reviews, natural language workflow generation, NHI governance) are being delivered. The ISC job market is growing faster than IIQ.

The characteristics of ISC-focused roles:

New implementation and architecture work. Organizations choosing IGA for the first time in 2024-2026 are implementing ISC. These greenfield projects involve platform architecture, connector development, integration design, and governance program design — the higher-value, higher-skill work that commands better rates.

ISPM and AI-adjacent capabilities. SailPoint's ISC roadmap includes Identity Security Posture Management, NHI governance, and AI-assisted access reviews. Engineers who develop expertise in these areas as they ship are positioning for the next wave of enterprise IGA demand rather than the current steady state.

Faster certification path. ISC's cloud-native architecture has a shorter learning curve for the operational aspects compared to IIQ's on-premises complexity. Your IIQ background means the governance concepts, provisioning logic, and compliance requirements are already familiar — you're learning the platform implementation, not the domain.

What Your 8 Years of IIQ Experience Is Worth

Don't underestimate the value of IIQ depth in the ISC context. Several things your IIQ experience gives you that pure ISC candidates don't have:

Deep understanding of what enterprise IGA actually does. Provisioning logic, correlation rules, access certification design, SoD policy construction, joiner-mover-leaver workflow complexity — you've worked through the real implementation challenges that trip up engineers who learned IGA from documentation rather than production environments.

Credibility with IIQ customers evaluating ISC. Organizations currently running IIQ who are evaluating ISC migration want engineers who understand their existing environment deeply. Your IIQ background makes you credible in those conversations in a way that someone who only knows ISC cannot be.

The migration opportunity. As noted above, IIQ-to-ISC migrations require both platforms' expertise. Engineers who can bridge both are specifically valuable in the next 3-5 year migration wave. This is a specific market opportunity created by your background that you should position explicitly in your job search.

Understanding of complex on-premises and hybrid governance scenarios. ISC's growing enterprise customer base includes organizations migrating from IIQ who have complex on-premises and hybrid scenarios that ISC's cloud-native architecture needs to accommodate. Engineers who understand these scenarios from IIQ experience are better positioned to architect ISC implementations for this customer segment.

The Certification Decision

ISC Engineer certification is the right primary direction. The market signal from SailPoint's investment, the new implementation demand, and the direction of enterprise IGA all point to ISC as the more durable certification investment. In 5 years, the IIQ-specific certification will have a narrowing market; the ISC certification will have a growing one.

Don't immediately abandon your IIQ positioning. While preparing for ISC, actively position the IIQ-to-ISC migration expertise as a differentiated value proposition in your job search. "Experienced IIQ engineer transitioning to ISC" is more compelling to many hiring managers than a pure ISC candidate without the underlying depth.

The "switch to a different tool" advice your colleagues offered deserves honest consideration rather than dismissal. The colleagues suggesting you evaluate other platforms entirely are responding to a real market reality: the IGA space is being disrupted by cloud-native platforms (Zluri, ConductorOne, Lumos, and others) that deploy faster, cost less, and are gaining market share in the mid-market segment that SailPoint is less competitive in. If you're open to broadening beyond the SailPoint ecosystem, gaining familiarity with next-generation IGA platforms alongside ISC gives you coverage across the enterprise (SailPoint) and mid-market (modern IGA) segments of the employer market.

Practical Recommendation

For your immediate situation — switching jobs while preparing a certification:

Start the ISC certification path now. Your IIQ background will make the ISC learning curve faster than you expect. The governance concepts are the same; the platform implementation is different. Give yourself 3-6 months to develop working ISC proficiency alongside the certification preparation.

Update your positioning before you start applying. Your 8 years of IIQ experience is an asset, not just a legacy. "Senior identity engineer with deep IIQ implementation background, currently building ISC expertise for migration and new implementation roles" is a strong market position. Emphasize migration project capability explicitly.

Consider hands-on ISC exposure. SailPoint's developer program and trial access allow you to build ISC familiarity in a non-production environment. Building and documenting an ISC configuration — even a personal lab project — gives you specific ISC talking points in interviews beyond "I'm studying for the certification."

Keep an eye on the broader IGA market. If your interest is in the architecture and design side of identity governance rather than specifically in the SailPoint ecosystem, understanding what next-generation platforms do differently — and where they're gaining traction — is useful context even if you remain SailPoint-focused.

Frequently Asked Questions

Is SailPoint IIQ still worth learning in 2024-2025?

IIQ remains valuable for the specific market segment of organizations maintaining existing IIQ implementations and the IIQ-to-ISC migration wave. New greenfield IIQ implementations are rare, so IIQ-specific investment is most valuable for practitioners already in the IIQ ecosystem who want to maximize the migration opportunity. For practitioners starting in IGA without existing IIQ experience, ISC is the better starting point.

How different is SailPoint ISC from IIQ technically?

ISC and IIQ share governance concepts — access profiles, provisioning policies, certification campaigns, connectors — but differ significantly in architecture and implementation. ISC is a cloud-native SaaS platform with a UI-configured workflow model and REST API-first integration approach. IIQ is an on-premises application with extensive Java-based custom logic (BeanShell) and XML-based configuration. Engineers migrating from IIQ to ISC need to translate IIQ's custom logic into ISC's more structured configuration model, which requires understanding both platforms well.

Should an experienced IIQ engineer consider non-SailPoint IGA platforms?

Yes, particularly if you're interested in architecture roles rather than implementation-specific roles. The IGA market includes enterprise platforms (SailPoint ISC, Saviynt), mid-market modern platforms (Zluri, Lumos, ConductorOne), and ISPM/authorization intelligence platforms (Veza). Broad familiarity with the market — what each platform does well and for which segment — makes you a stronger architecture advisor than deep expertise in a single vendor. Many senior identity architects maintain working knowledge of 2-3 platforms.