Four 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 complexity and carry our quality and observability standards with them. Own the architecture and the core stack: what gets standardized, what gets reused, and where the system should be in eighteen months.
Infrastructure, observability and reliability. Infrastructure as code by default, from cloud resources through to dashboards and alerts. Provision, run and tune our Kubernetes cluster and cloud footprint, and keep CI fast as the deploy rate grows. Define SLIs for the workloads that
matter, build SLOs on top of them, and make the alerting high-signal enough that people trust it. Drive down AI and infrastructure spend.
Security and compliance. Keep the internal foundations secure by default: IAM, dependency management, secrets. Own the authentication and authorization stack, including ReBAC models covering both humans and agents. Implement SOC 2 and ISO 27001 controls without taxing every future change.
AI dev tooling. Keep product engineers and their agents on the paved road by making sure the documentation and agent guidelines they need are in place. Shorten the path from design to implementation with standardized automations and development environments that stay close to production.
What this looks like in practice
•
A system of record for managing and distributing constantly evolving agent configurations, under strict auditability and tenant isolation requirements
•
The harnesses powering our AI agents, abstracting over use cases that change faster than the code
•
Centralized progress tracking that holds up across a growing number of parallel agent executions
•
Usage-based tenant billing with quotas and rate limiting across a growing set of products
•
SLIs for the background job system behind our agents (execution latency, AI spend, memory, CPU), then fixing the bottlenecks they expose at both the application and infrastructure level
•
A document pipeline handling dozens of file formats, very large spreadsheets and hundreds of parallel uploads, under a strong reliability requirement