CircleCI: Senior Software Engineer

The useful part

The interfaces that developers use to understand and trust that work don't exist yet. We think like the customer: every decision connects back to the developer sitting in front of a failing build at 2 am. Where you land depends on where your strengths create the most leverage, and we figure that out together.

How it works

• The through line across all of it is the same: full-stack ownership, a high bar for craft, and work that directly shapes how tens of thousands of developers experience CircleCI every day.
• It's not a productivity layer on top of engineering, but the default starting point for how problems get approached and solved.
• We learn fast: we run experiments, accept failure, and scale what works.
• You might own the CI pipeline experience, deploy and release tooling, notification infrastructure, monetization flows, AI agent surfaces, or the foundational web platform.

What to take from it

When the problem is complex or the answer isn't obvious, you're the person who leads the design discussion, writes the ADR, and makes the call. Pipelines run autonomously, generate fixes, and surface results that need human judgment.

Example or evidence

• They write code, trigger builds, interpret failures, and propose fixes.

Details worth keeping

Remote, Ontario, Canada About CircleCI Engineering CI/CD has been solved. At CircleCI, our guiding principles aren't posters on a wall. Team-Agnostic Placement We don't hire for a team.