• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. • Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked • We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. You're setting the technical defaults a growing team will inherit, so the early decisions matter. • Day to day, that looks like: • Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked • We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. • Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production. • Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it. • Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't. • Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked. • Expecting you to have opinions about where this should go, and to write them down.