Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Staff Software Engineer, Identity and Authorization
- Remote from
- Argentina
- Salary
- Undisclosed
- Department
- Cybersecurity
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 13 Dec 2026
- Listing views
- 33
- Application actions
- 1
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
About this role.
Who we are
At Domino, we build solutions that help the largest, highly regulated organizations adopt AI to accelerate mission-critical use cases. Our platform integrates a streamlined model and app development environment, advanced model, agent, and app hosting capabilities, and novel governance capabilities providing regulator-ready AI at scale. Our customers — like Johnson & Johnson, GSK, Bristol Myers, UBS, FINRA and the US Navy — are using our software to solve some of the most important challenges in the world, such as developing new medicines, securing our financial markets, or protecting our country. Backed by Sequoia Capital, Coatue Management, NVIDIA, Snowflake and other leading investors, we have been in business for over a decade but are still a small team operating with the spirit of a startup. In the world of AI today, we believe that the future is still being invented — and we want to be the ones building it. For more information, visit www.domino.ai
What we are building
Domino’s Identity and Access platform (IDSM) is the foundation for how customers in some of the world’s most regulated industries manage who can see and do what. We’re evolving it into a centralized, relationship-based authorization framework built on SpiceDB, and you’d be the technical anchor for its next phase.
- A unified authorization model. Extend a centralized, fine-grained, relationship-based model across the platform, replacing feature-specific permission checks with consistent, reusable primitives.
- Production-grade operations. Harden the authorization layer for the scale, reliability, and security that enterprise and public-sector customers expect.
- A thoughtful migration path. Make the sequencing and design calls that let us retire legacy access checks without disrupting customers along the way.
- Groups and organizations that mirror real customers. Rethink how we model groups and organizational hierarchies so large enterprises can represent their teams the way they actually work.
- Cloud-native identity. Deepen integration with cloud workload identity, starting with AWS IRSA and extending to Azure and GCP equivalents.
- Foundations other teams build on. Design core identity and access capabilities, with clean interfaces and flexible abstractions, that engineers across the company can adopt with confidence.
- A stronger way of building. Set the patterns for how the team uses AI-assisted development to ship high-quality features faster, without compromising security or code quality.
What your impact will be
- Set the architectural direction. Design identity and access solutions that meet customer demands for managing user and group access, and are secure, scalable, and built on primitives teams can reuse.
- Bring clarity to complex decisions. Articulate the architecture clearly enough that the rest of Engineering can rally around it.
- Be the go-to authority. Engineers and teams building on IDSM will bring their auth questions to you, and your technical judgment will carry real influence.
- Raise the engineering bar. Lead design reviews, unblock engineers facing ambiguity, and champion flexible abstractions and well-thought-out interfaces.
- Increase velocity and reduce maintenance. Improve our architecture, including removing tech debt, so the team ships faster with less ongoing maintenance.
- Shape how we build with AI. Establish patterns for using AI-assisted development to deliver high-quality features faster without compromising security or rigor.
- Foster ownership and urgency. Help the team know what to build and value both quality and speed of iteration and contribute to experiences that make identity and user management easier for the enterprises we serve.
What we look for in this role
- A track record of evolving an enterprise-grade authorization system under real production traffic, with strong opinions about the architecture of these systems
- Experience designing a new auth system and migrating to it from a legacy approach (a plus)
- Experience on a platform team supporting other services within a larger engineering organization
- A background at a company that builds authentication or authorization products (a plus)
- A concrete example of an auth system you helped build that solved a recurring class of customer challenges
- A history of helping teams become better engineers by improving designs, velocity, and quality
- Authorization systems: Hands-on experience with relationship-based or fine-grained authorization, including schema design (relations, permissions, caveats) and the tradeoffs versus traditional RBAC
- Identity protocols: Solid grounding in OIDC and SAML, and ideally experience with an IdP such as Keycloak, Auth0, Okta, or ForgeRock
- Cloud identity: Practical experience with workload identity patterns such as AWS IRSA, Azure Workload Identity, or GCP Workload Identity Federation
- Secrets management: Familiarity with a credential management system such as Vault
- Backend engineering: Strong Go, Java, or a comparable language, comfort running services on Kubernetes, and API design instincts from owning a platform others build on
- System architecture: Experience architecting auth frameworks that scale to enterprise customers
- AI-assisted development: Considered, real-world experience using AI coding tools while maintaining code quality and security rigor
What We Value
- We value a growth mindset. High-performing creative individuals who dig into problems and see the opportunities for success
- We believe in individuals who seek truth and speak the truth and can be their whole selves at work
- We value all of you that believe improving is always possible At Domino Everything is a work in progress – we can do better at everything
- We emphasize an environment of teaching and learning to equip employees with the tools needed to be successful in their function and the company
- We strongly believe in the value of growing a diverse team and encourage people of all backgrounds, genders, ethnicities, abilities, and sexual orientations to apply
#LI-Remote
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
4/5Autonomy Level
5/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would first inventory existing authorization paths, define a target authorization model, and prioritize high-risk or high-value domains. I would introduce the new system behind stable interfaces, run dual-read or shadow evaluations where feasible, measure decision mismatches, and migrate incrementally with rollback controls. Clear ownership, observability, and customer-impact safeguards are essential throughout the transition.
The model should represent real business relationships clearly while keeping permission evaluation predictable and maintainable. I would define reusable relations and permissions, account for nested groups and organizational hierarchies, use caveats only where contextual policy is truly required, and test performance for high-cardinality relationships. I would also establish schema review practices and versioning to prevent policy drift.
I would use short-lived federated workload identities rather than static credentials. On AWS, that means IRSA; on Azure, Workload Identity; and on GCP, Workload Identity Federation. The design should enforce least privilege, bind identities to service accounts and namespaces, rotate trust configurations safely, and provide auditable access paths across clouds.
I start with common use cases and define a small set of durable primitives rather than exposing every underlying implementation detail. I validate API ergonomics with early adopter teams, provide strong defaults and documentation, and reserve extension points for demonstrated requirements. Platform success should be measured by safe adoption, reduced duplicated logic, and lower support burden.
AI tools can accelerate drafting, refactoring, test generation, and documentation, but they should not replace engineering accountability. I would set guidance for approved use cases, require normal code review and security review, avoid exposing sensitive data to unapproved tools, and validate generated code through tests, static analysis, and threat modeling. The goal is faster delivery with explicit quality and security controls.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
