Your RoleWe ship fast, and we intend to keep shipping fast.
The consequence is that our system is outgrowing the amount of deliberate design that went into it.
We run AI agents over customer documents in a domain where being wrong is expensive, and a lot of the load-bearing decisions.
That means codifying golden paths, building the shared primitives and APIs that product engineers work on top of, owning the architecture of the system as a whole, and establishing what our reliability actually needs to be before an incident establishes it for us.
Platform at Cortea sits between software engineering, DevOps and SRE.
Its customers are other engineers.
This is not a DevOps role under a different name: you will spend more time in application code than in YAML, and the reason we want infrastructure experience is that we don't believe you can design a system well without being able to run it.
The bar we are hiring against is someone who has taken a system from nothing to production and owned it end to end.
You picked the technology, argued the tradeoffs in writing, provisioned the infrastructure, and were responsible for it when it broke.
On AIWe use AI heavily and we want you to.
What we are not looking for is someone who outsources their judgment to it.
The mental model of this system has to live in your head, not in a context window.
Use agents to move quickly on implementation.
Do the design, the reasoning and the writing yourself, and be able to defend every decision you ship.
What you'll doFour areas, roughly in the order you will spend time on them.
You won't work on all of them at once, but you should be open to any of them.
Product platform.
Make the easiest way for product engineers to do something (the paved road, or golden path) also the most secure, reliable and scalable way by default.
Build the shared primitives, libraries and APIs that hide comp.