Own a real problem
Roles are defined around systems and customer outcomes, not narrow task queues.
S/Runtime is building the execution layer that lets enterprise agents use company context, take permitted action, and leave a record people can trust. The work spans distributed systems, product design, security, and close collaboration with customers.
Build the core product. Early decisions about identity, execution, and control will shape the platform.
Stay close to the work. Product, engineering, security, and customer teams share the outcome.
Be precise about trust. Enterprise agents need clear authority, predictable failure behavior, and evidence.
Search by discipline or team. Each page describes the work, the experience that matters, and the expected location.
56 roles
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Engineering
San Francisco or US remote
Security and trust
San Francisco or US remote
Security and trust
San Francisco or US remote
Security and trust
San Francisco or US remote
Security and trust
San Francisco or US remote
Security and trust
San Francisco or US remote
Security and trust
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Product and design
San Francisco or US remote
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Customer delivery
US remote, near enterprise customers
Go to market
US remote, near enterprise customers
Go to market
US remote, near enterprise customers
Go to market
US remote, near enterprise customers
Go to market
US remote, near enterprise customers
Go to market
San Francisco or US remote
Go to market
San Francisco or US remote
Go to market
US remote, near enterprise customers
Go to market
US remote, near enterprise customers
Company operations
San Francisco or US remote
Company operations
San Francisco or US remote
Company operations
San Francisco or US remote
Company operations
San Francisco or US remote
Company operations
San Francisco or US remote
Company operations
San Francisco or US remote
We are working at the boundary between AI behavior and enterprise operations. That means treating product quality, security, customer context, and operating reliability as one problem.
Roles are defined around systems and customer outcomes, not narrow task queues.
Clear decisions, interfaces, and operating records matter when software can act.
Approvals, stale permissions, partial failure, and recovery are part of the product.
Send a short note about the systems you have built and the problem you want to work on. Please do not include sensitive personal records.