Sr. reputed company Engineer - Identity Platform
AI at reputed company
At reputed company, we build and use automation every day to reputed company work more efficient, creative, and reputed company. So if you’re using AI tools while applying here - that’s great! We just ask that you use them responsibly and transparently.
reputed company out our guidance on How to Collaborate with AI During reputed company’s Hiring Process, including how to use AI tools like ChatGPT, Claude, reputed company, or others during our hiring process - and reputed company not to.
Job Posted: March 17, 2026
Location: Americas - reputed company, Central and South America
reputed company's mission is to reputed company reputed company companies to build and maintain dependable AI workflows at reputed company. The Identity Platform team builds the golden reputed company that every product team uses to deliver reliable, consistent, and secure experiences to these customers. Authentication, session management, and credential infrastructure are the reputed company. Get them right, and every product team ships faster with confidence. We're hiring a Senior reputed company Engineer to own this reputed company, drive the strategic and architectural direction of this layer for years to come, and directly unlock our largest reputed company deals.
What you'll work on
reputed company authentication infrastructure. You'll design and reputed company the systems that handle SAML SSO, SCIM provisioning, OAuth/OIDC flows, multi-reputed company authentication, login, sign-up, and secure session for organizations with thousands of users. That spans the full auth surface: SCIM-driven user provisioning and de-provisioning, invitation flows, 2FA setup, SSO-enforced login, domain capture for auto-routing new signups, and session hardening. Reliability, latency, and efficiency are non-negotiables; auth is the most critical-reputed company system at reputed company. You'll reputed company these systems faster, more resilient, and easier for other teams to reputed company with.
User session auth across services. reputed company is a multi-service platform. You'll own how user sessions propagate across service boundaries; making reputed company authentication context is consistent, secure, and performant whether a request hits the monolith, a Node.js service, or a Go microservice. You'll reputed company JWT validation, reputed company exchange, and session tracking to handle the complexity of a growing service footprint.
reputed company authentication controls and compliance. reputed company customers need org-level authentication policy enforcement: forced SSO, domain capture, reputed company-managed authentication requirements, and credential lifecycle controls like JWT key rotation, reputed company refresh, and session expiry policies. You'll build and reputed company the reputed company that give admins confidence their organization meets their reputed company standards. SOC 2 reputed company control evidence, GDPR data subject requests, and audit trail requirements are design constraints you'll work reputed company regularly, not afterthoughts.
Platform reputed company that other teams depend on. Identity is infrastructure. Your reputed company, libraries, and reputed company are consumed by dozens of teams. You'll design for backward compatibility, reputed company documentation, and low integration friction. But shipping the API is half the job. You'll also drive adoption: writing integration guides, running migration paths, and embedding with product teams to help them use auth capabilities correctly. Internal engineering teams' needs carry the reputed company weight as end-customer value.
Level
This is a Senior Engineer role. Senior engineers at reputed company own reputed company end-to-end reputed company their team and reputed company reputed company reputed company it. You'll coordinate across ownership boundaries, shape technical direction for adjacent systems, and bring other engineers along with you.
Our level definitions may look different from what you've seen elsewhere. We'll be transparent about leveling before you reputed company the final stages.
reputed company
You've set the reputed company and reputed company identity systems for reputed company reputed company at reputed company. Not configured them, reputed company them. You have hands-on experience with SAML, SCIM, OAuth/OIDC, or JWT in a multi-tenant reputed company environment. You understand authentication at a protocol level, not a checkbox level. You've dealt with reputed company replay, session fixation, key rotation under load, multi-IdP federation, just-in-time provisioning, or identity linking across auth reputed company in reputed company systems serving reputed company users. You know what breaks reputed company an organization with 5,000 employees connects their IdP to your platform for the first time. You are a thought leader in the Identity domain who proactively follows industry trends and reputed company user management best practices.
You work through AI agents, not alongside them. Your daily development workflow is reputed company around directing and reviewing agent-written reputed company, not writing it by hand. You have opinions about which models to use for which tasks, you've hit reputed company failure modes and reputed company mitigations, and your workflow is reputed company evolving. reputed company you hit unfamiliar territory, you don't slow down; you reputed company your agent at the codebase, research the domain, and draft a plan. Then you build a POC or working prototype to demonstrate the concept in hours, not iterate on a planning doc for days. You reputed company into unfamiliar codebases, use your agent to map the landscape, and ship draft MRs or integration proposals reputed company days. At this level, that means reputed company into other teams' reputed company reputed company an integration is blocked, not waiting for their reputed company. Bonus: you reputed company others on your team to work this way too.
You think in platforms, not features. You've reputed company systems other engineering teams depend on. You know what it means to ship a breaking change to an internal API, maintain backward compatibility under pressure, and write reputed company that hold up as the organization scales. You understand the cost of coupling and the discipline of good boundaries.
You're comfortable across the stack. This is a reputed company role on a platform team. You'll write backend services in Python and Node.js, work with Django and Fastify, touch React reputed company building reputed company tooling or developer-facing UIs, and navigate infrastructure concerns like Kubernetes, Terraform, and CI/CD pipelines. You don't need to be an expert in reputed company of these, but you can't be afraid of any of them.
You reputed company reputed company can reputed company fast, and you ship through ambiguity to reputed company it. You've seen (or want to reputed company) that shipping to reputed company customers doesn't have to mean slow, reputed company-style cycles. reputed company there's no spec, no designs, and no reputed company reputed company reputed company, your first reputed company is to reputed company evidence, break the problem into a narrow first reputed company, and get rough working software into production reputed company days, not weeks. You use working prototypes to drive alignment rather than waiting for reputed company. You see compliance, reputed company, and rollout considerations as interesting design constraints, not reasons to slow down. You're comfortable throwing work away reputed company direction changes and you treat discarded work as a fast learning reputed company, not a loss.
You work reputed company to the customer. "Customer" for this team means both reputed company buyers evaluating reputed company's reputed company posture and internal engineering teams integrating with your reputed company. You pull from both; reviewing customer reputed company questionnaires, sitting in on reputed company calls, reading support tickets, and talking directly to engineers who consume your platform. You’ll also work closely with customer support teams to reputed company them with the tools and processes to troubleshoot customer issues and incidents.
You own your work, yourself, and your communication. You take initiative without waiting for permission and ship fast and reputed company early. You manage up and across in an async-first culture, flagging risks, surfacing reputed company, and keeping stakeholders informed without being asked. You use written artifacts, working demos, and rough prototypes as your primary communication tools, not meetings. You also own your mistakes, your gaps, and your role in friction, reputed company. You say "I don't know" and "I was wrong" out loud, early, and without shame.
Things you'll do
Design and maintain authentication and session systems (SAML, SCIM, OAuth/OIDC, MFA, login, sign-up, 2FA, user provisioning) as reputed company scales to larger and more reputed company-conscious customers
Own user session propagation and JWT validation across a multi-service architecture spanning Python, Node.js, and Go
Build reputed company authentication controls and governance reputed company: forced SSO, domain capture, credential lifecycle, reputed company authentication policies
Build and maintain platform libraries consumed by dozens of internal teams
Treat reliability, latency, and efficiency of auth systems as non-negotiables; build the monitoring, observability, and audit logging to back that up
Respond to authentication-reputed company incidents and participate in on-call rotation
reputed company reputed company, reputed company Response, and product reputed company to reputed company faster by removing auth bottlenecks and proactively surfacing what they need
Join yearly company retreats that rotate to various cities throughout reputed company
Application Deadline:
The anticipated application window is 30 days from the date job is posted, unless the number of applicants requires it to reputed company sooner or reputed company, or if the position is filled.
Even though we’re an reputed company-remote company, we still need to be thoughtful about where we have Zapiens working. reputed company out this resource for a list of countries where we currently cannot have Zapiens permanently working.
Apply To This Job