Principal Software Engineer (Platforms)
Summary
Builds and runs Rowden's internal developer platform for its software teams — CI/CD, source control, secrets, and reproducible environments on containers/Kubernetes — while leading the rollout, guardrails, and advocacy for agentic AI coding agents. Not a delivery role; the platform is the product. SC clearance eligibility required.
Salary
For senior roles, compensation is tailored to the scope of the role and the specific experience a candidate brings. Because that can vary significantly, we do not always publish a fixed salary band. We will, however, discuss compensation openly at the first stage of the process and can share an indicative range before either side invests significant time.
- Build the Internal Developer Platform: design, build, and run the platform that Rowden's software teams and their coding agents depend on to write, test, ship, and operate code.
- Own software engineering infrastructure and workflows end-to-end: source control, CI/CD, artefact management, secrets, and the environments our software runs in.
- Champion new tooling and best practice: track what the best engineering organisations are doing, evaluate it rigorously, and bring in whatever earns its place.
- Raise standards through influence: set technical direction and standards across teams you do not manage, by building things that people choose to use.
- Lead the implementation of agentic AI: roll out coding agents across engineering workflows and own how and where they're used.
- Advocate for agentic engineering across the business: run evaluations, evidence the benefits, and train teams on effective use.
- Build the infrastructure that makes agents trustworthy: sandboxing, permissioning, audit logging, and observability so that what an agent did is efficient, secure, and fully transparent to the engineer who has to stand behind it.
- Create repeatable development environments: make local, cloud, and target-representative environments reproducible, quick to stand up, and identical for every engineer.
- Substantial experience as a principal or staff software engineer.
- Demonstrable experience building developer platforms, internal tooling, and paved paths used by engineering team.
- Hands-on experience implementing agentic AI in real engineering workflows (beyond individual experimentation).
- Experience designing the guardrails around agentic AI: sandboxing, permissioning, audit logging, or observability for tools operating with elevated access.
- Deep, hands-on experience of CI/CD, infrastructure as code, containers, and Kubernetes.
- Experience of building and deploying reproducible development environments.
- A track record of driving adoption by persuasion and good product decisions, not mandate.
- Clear written communication, including documentation that engineers actually read.
- You treat the platform as a product and your colleagues as customers, and you measure yourself on their throughput rather than your own.
- You notice friction that everyone else has learned to live with, and you fix it.
- You're a genuine advocate for agentic engineering. You make the case for it with evidence, help teams adopt it well, and are honest about where it isn't the right tool.
- You are opinionated about tooling and you change your mind when the evidence changes.
- You are comfortable owning something long-lived rather than moving between projects.
- You can tell the difference between a genuinely better tool and a fashionable one.
- You are honest about trade-offs, including the ones in your own work.

