Principal Security Architect (Product Security)

Role Summary

This role owns the architecture itself: the reference designs engineering builds against, the review of the hardest problems, and the work of making secure-by-design real across the Hyperblock and Polaris platform and the AI product surface. As the most senior technical individual contributor in the security architecture practice, you set the technical bar the practice codifies into standards. The value of this role is not in producing documents that describe good architecture; it is in producing architecture that engineers adopt because it is genuinely the better path. You will work hands-on, on the problems that carry the most risk.

Anaplan is not a simple SaaS application. The platform performs highly dimensional, enterprise-scale modelling with responsive recalculation and strong correctness expectations. The technical surface area includes the legacy Hyperblock engine, the newer Polaris engine, and a growing set of AI-powered products, including CoModeler for AI-assisted model building and CoPlanner for conversational, analyst-style planning support. AI-assisted capabilities such as CoModeler and CoPlanner are reshaping how the platform behaves, which means identity, authorisation, supply-chain integrity, and verification all need designing rather than reusing. The hardest security design problems land here, with real room to set the patterns. Security architecture has high leverage because it sits close to engineering and platform decisions.

Your Impact:

• Define reference architectures: own the security reference designs for the platform and the AI products, and keep them current as both evolve.

• Own identity and authorisation architecture: including authorisation for AI agents and analyst-style workflows, where assumptions about who is acting no longer hold.

• Set cryptography architecture: encryption and key-management standards, with a clear position on what is mandatory versus contextual.

• Design AI guardrails: input and output controls, tool and authorisation boundaries, and abuse and prompt-injection defences, informed by references such as MITRE ATLAS and the OWASP LLM Top 10.

• Lead threat modelling on the riskiest systems: and turn the findings into concrete design changes.

• Drive secure-by-design into the supply chain and attack surface: including build integrity and provenance, hardened images, and reduction of exposed surface.

• Set the technical bar the practice codifies: establish the standard that becomes adopted, enforceable guidance across the team.

• Stay hands-on: write and review real designs and prototypes, and pressure-test your own architecture rather than only specifying it.

Your Qualifications:

• Deep, demonstrable architecture mastery: secure software architecture, cryptography, identity and authorisation, and threat modelling at scale.

• Real AI and ML security depth, not vocabulary: a working grasp of how LLM-driven features change identity, authorisation, supply chain, and verification.

• Hands-on technical authority: you still design and review real systems and can defend your choices to strong engineers.

• The ability to influence senior engineers without formal authority, especially when risk and delivery pressure are in tension.

• Enterprise-scale, SaaS or cloud-first experience where architecture decisions carried real consequences.

Nice to have

• Published research, talks, or contributions to standards such as NIST, ISO, or OWASP.

• Experience designing for enterprise and regulated environments.

• An offensive grounding, formal or informal, that you use to pressure-test your own designs.