This role exists to change how engineering at Safe gets work done — not to add AI tools on top of today’s workflow, but to rebuild the engineering operating model around AI, automation, and redesigned process, and to prove the gain in numbers.
You will look across the full lifecycle — requirements, design, implementation, review, testing, deployment, operations, incidents, documentation — find where engineers lose time, and decide what actually fixes it: an AI agent, an automation, a platform capability, or a process change. Then build it to production quality, drive adoption, and measure whether cycle time moved.
This is not a Developer Experience, DevOps, or internal-tools role. It is a software engineering role whose product is engineering throughput.
Engineering output is the constraint on how fast we ship against Fortune 500 demand. AI can lift it — but most organizations bolt AI onto unchanged workflows and get a chat window. The leverage is in redesigning the workflow around what AI can now do, putting agents inside CI, review, testing, and incident response, giving them real engineering context, and setting guardrails so engineers move fast without lowering the bar.
The objective is not AI adoption. It is materially higher engineering output, speed, and quality.