> Markdown version of [/jobs/ext/4559628-identity-security-engineer](https://www.wearedevelopers.com/jobs/ext/4559628-identity-security-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Identity Security Engineer - **Company:** Scopely - **Location:** Barcelona, Spain - **Contract:** Franchise - **Skills:** Microsoft Access, Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Audit Trail, User Authentication, Cloud Computing Security, Code Review, Cyber Security, Continuous Integration, Data Security, Video Game Development, Identity and Access Management, Intrusion Detection and Prevention, Python (Programming Language), OAuth, OpenID, Role-Based Access Control, Anti-Phishing, Zero Trust Network Access, Security Assertion Markup Language (SAML), Security Information and Event Management, TypeScript, Scripting, Google Cloud, Okta, Delivery Pipeline, Multi-Agent Systems, Agentic-AI, Customer Identity Access Management, Build Management, Kubernetes, Drift Detection, Terraform, Software Version Control - **Published:** November 4, 2026 - **Apply:** https://startup.jobs/senior-identity-security-engineer-scopely-company-10149155 ## About the Role * 5+ years of experience in IAM, or identity-focused cloud/security engineering, including hands-on ownership of production identity controls in complex environments. * Strong experience with Okta or a comparable workforce identity platform and AWS/GCP IAM, as well as federation and provisioning protocols such as SAML, OIDC, OAuth, and SCIM. * Production experience building, testing, and operating identity services or automation using Terraform or comparable infrastructure as code, Python, Go, or TypeScript., APIs, version control, and CI/CD. * Strong knowledge of least privilege, just-in-time privileged access, identity lifecycle and governance, authentication controls, and non-human or workload identity risk. * Experience threat-modeling identity architectures, integrations, and access paths, and driving remediation with service owners. * Hands-on experience building AI-native workflows: systems where agents carry out multi-step work end to end, designed from the start around what agents can be trusted to do and where humans approve. Using a coding assistant does not count. * Working fluency with harness engineering and multi-agent development: defining tools and permissions, scoping context and data, writing evals, orchestrating specialized agents, and instrumenting agent runs so failures are diagnosable, plus the judgment to keep those systems inside least-privilege boundaries. * Ability to lead technical work from design through deployment and operations, and explain identity risks and implementation choices to stakeholders. * Experience with identity governance, privileged access, or cloud entitlement tooling, or having built the equivalent in-house. Nice-to-have * Consumer identity (CIAM) at scale, Kubernetes workload identity, detection engineering or SIEM experience, Okta or cloud security certifications, gaming or live-service experience. ## Description * Reduce standing and excessive access with least-privilege roles, just-in-time and time-bound elevation, and automated access reviews. * Build repeatable identity and access workflows that make onboarding, approvals, role changes, reviews, and offboarding consistent, traceable, and timely. * Govern non-human identities, including service accounts, workload identities, CI/CD identities, API credentials, and AI agents and their tool integrations: inventory them, assign owners, replace long-lived secrets with short-lived or federated credentials, and rotate or revoke on a schedule and on signal. Strengthen identity protection and resilience * Protect access to critical business processes and systems with phishing-resistant authentication (passkeys/FIDO2), device trust and posture signals, tightly controlled privileged access, and prompt revocation of suspicious sessions or compromised credentials. * Threat-model identity platforms, integrations, and access paths to identify exploitable trust relationships, privilege escalation, and credential misuse. * Build identity telemetry and response workflows to detect risky sign-ins, privilege changes, credential misuse, and compromised integrations. * Design and test break-glass and recovery procedures for identity services and cloud access so teams can regain secure access during an outage or compromise. * Extend the same patterns to player and partner identities where security owns the controls: platform identity federation (Apple, Google, Steam, console), account linking and recovery, external and vendor access, and defenses against account takeover and credential stuffing. Build AI-native identity services * Build and operate reusable identity controls and services using infrastructure as code, APIs, scripting, and delivery pipelines. Apply code review, testing, drift detection, and audit trails so that every change, whether made by an engineer or an agent, is safe to deploy and easy to investigate. * Design and build multi-agent workflows that surface identity risk, run access attestations, and triage and remediate access issues end to end. Engineer the harness those agents run in: scoped tools and permissions, curated context and data access, evals and test cases, orchestration between agents, and observability, so agent behavior is predictable, reviewable, and improvable. * Treat agents as identities. Give every agent and MCP integration its own scoped credentials, least-privilege permissions, and bounded data access; validate inputs and outputs; log every action; and require human approval for changes that touch privileged access or production. * Work with game and platform stakeholders to adopt shared identity patterns. Measure progress through reduced standing privilege, stale access, and unmanaged identities, and less manual work. * Produce audit-ready evidence for access reviews, privileged access, and lifecycle events as a byproduct of the workflows rather than a separate project.