Staff Software Engineer, Delivery Engineering

Contract type
Ongoing
Work mode
Remote · Europe, Eastern time zone
Experience
Senior · 8+ years

Job description

A senior engineering role in CircleCI's Delivery Engineering team focused on building and standardizing agentic software development tooling and platforms across the engineering organization. The role shapes the end-to-end agentic SDLC and drives adoption of shared tooling.

At a glance

Employment
Full-time · Employee (employment agreement)
Work mode
Remote · Europe, Eastern time zone
Pay
CAD 195,000 – 265,000 / year

What you'll do

  • Build AI-natively, treating AI as the default starting point for approaching and solving problems
  • Help define the end-to-end agentic SDLC, from identifying a change through planning, execution, pull request, merge, and measuring impact afterward
  • Evaluate shared tooling and patterns, and help decide what teams standardize on
  • Spend time with engineering teams to understand their workflows and where they get stuck, and use what you learn to drive decisions and direction
  • Build and support shared tooling that other teams depend on, and own its adoption as much as its delivery
  • Instrument agent usage and outcomes to know what improves throughput and quality and what just burns tokens
  • Treat cost, model choice, and reliability as design concerns
  • Evaluate models, vendors, and open-source tools against our needs and make build-vs-buy calls
  • Write design docs, lead technical discussions across teams, and mentor engineers across the org as they adopt agentic workflows

What we're looking for

  • Direct experience driving agentic developer experience efforts, including what was built, how impact was measured, how adoption was driven, and what didn't work
  • Hands-on depth with agentic tooling: daily work with coding agents, agent harnesses, MCP, and skills or prompt design; ability to evaluate agent output and reason about model and token economics
  • A platform mindset: built and supported internal platforms or developer tooling that other engineers build on and rely on, and driven their adoption
  • Backend depth in Go, including owning production backend services with API design, data modeling, and service integration
  • A track record at staff scope: 8+ years of production engineering experience, including technical decisions that spanned multiple teams and accountability for whether they landed
  • Decision-making grounded in users: build direction by listening first, turn the needs of many teams into clear tradeoffs, document reasoning, and bring people along

Your team

Delivery Engineering

Enables CircleCI engineers to deliver quickly, confidently, and securely by providing tools and resources that make standard patterns and best practices simple to adopt and by reducing toil. Current focus is the agentic software development lifecycle. A small, very senior team where everyone shapes where it goes.

Apply

Direct apply at CircleCI

Opens the job posting at CircleCI

About CircleCI

The world's largest continuous integration/continuous delivery (CI/CD) platform

CircleCI is the world's largest continuous integration/continuous delivery (CI/CD) platform, and the hub where code moves from idea to delivery. As one of the most-used DevOps tools - processing more than 3 million jobs a day - CircleCI has unique access to data on how the most effective engineering teams work, and the tools to help software companies successfully leverage the power of AI into their commercial applications.

Key facts

  • 2011
  • downtown San Francisco
  • CI/CD / DevOps software
  • Processes more than 3 million jobs a day
  • Founded in 2011
  • Headquartered in downtown San Francisco with a global, remote workforce
  • Venture-backed

Partners & customers

HingeHuggingFaceSamsungBase10Greenspring AssociatesEleven PrimeIVPSapphire VenturesTop Tier Capital PartnersBaseline VenturesScale Venture PartnersOwl Rock CapitalNext Equity PartnersHeavybitHarrison Metal Capital

What they value

  • We learn fast: we run experiments, accept failure, and scale what works
  • We think like the customer: every decision connects back to the developer sitting in front of a failing build at 2 am
  • We own the outcome: not just our slice of it, but the whole thing