Skip to content

Jobicy

Staff Software Engineer, Identity and Authorization at Domino Data Lab

Jobicy is hiring a Staff Software Engineer, Identity and Authorization at Domino Data Lab for a remote role open to applicants in Argentina. Level rates it ; you can apply on Jobicy.

Source: Jobicy. Level lists this role from Jobicy; you apply on their page.

Level's read on this job

  • Little AI ●○○○ is how Level rates this software engineer role: aI is not part of the work.
  • This is listed as a remote role.
  • The posting mentions Spicedb, AWS and Azure among its tools and skills.
  • Jobicy has 425 other open roles on Level.
  • Posted within the past week.

AI in this role

Lead the development of a centralized, relationship-based authorization and identity framework for an AI data platform.

SpicedbAWSAzureGoogle Cloud
software-engineeringidentity-and-access-managementcloud-nativeauthorizationdistributed-systems

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

How we rate this

Staff Software Engineer, Identity and Authorization at Domino Data Lab at Jobicy rates 20 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.

Classification

Little AI. AI is not part of the work.

  1. ●●●● Builds AI80 to 100
  2. ●●●○ Works on AI60 to 79
  3. ●●○○ Uses AI40 to 59
  4. ●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.

Prepare for this job

Built from this posting and from similar jobs on Level.

Skills and AI tools this role asks for

Software EngineeringIdentity And Access ManagementCloud NativeAuthorizationDistributed SystemsSpicedbAWSAzure

Also common in software engineer jobs at this level

Pay

Typical software engineer job
$167k

This posting doesn't list pay. Use the typical software engineer figure when pay comes up. See software engineer jobs

Questions you could be asked

  1. Tell me about a project where software engineering was part of your work. What did you do?
  2. Tell me about a project where identity and access management was part of your work. What did you do?
  3. Tell me about a project where cloud native was part of your work. What did you do?
  4. Tell me about a project where authorization was part of your work. What did you do?
  5. Tell me about a project where distributed systems was part of your work. What did you do?

Adapt your resume

  • List these exact terms on your resume: Software Engineering, Identity And Access Management, Cloud Native, Authorization, and Distributed Systems. An applicant tracking system matches the wording, not the idea.
  • Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.

Get your CV reviewed before you apply

Send your CV and the role you want next. Your review arrives by email usually within a few hours.

Get new remote software engineer jobs by email

One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.

Free.

Similar roles

Software Engineering roles that involve little AI, at other companies.

What kind of AI work fits you?

Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.

Find my next step

More jobs at Jobicy

More software engineer jobs

Related searches

Same AI level