Developer

About The Role

Hi, I'm Chris, and I lead the Delivery Engineering team at Jane. I've spent most of my career leading engineering and delivery teams, from large-scale cloud transformations at CA Technologies to R&D in regulated healthcare, and these days I do it from a small farm in Prince Edward Island.

Delivery Engineering is a small, senior team with an outsized job. We build and run the pipelines that take code from our codebase all the way to production for the many teams working in a shared codebase. We don't own the product's tests or features; we build the orchestration that extracts, builds, ships, and safely deploys code, and we provide the hooks that make sure every quality check runs when it should. When I started, deploying was a manual, multi-hour process. Today it's a couple of clicks, and we've grown throughput from a handful of deployments a day to dozens, with plenty of room still ahead.

Here's where you come in. Our supported window mostly covers Pacific hours today, and I want to widen it. I'm looking for a senior engineer in the Eastern time zone or further east, ideally in Canada (Atlantic or the UK also work well), who's comfortable with an earlier start so more teams have more of the day to deploy while supported. You'll split your time between keeping delivery healthy for the teams that depend on us and project work to remove manual steps, optimize throughput, and make the whole system faster and more reliable. Our roadmap flexes with the needs of other teams, so comfort with ambiguity matters. If you like small teams, big leverage, and quietly making everyone else's work better, I'd love to meet you.

What Impact We're Looking for You to Make

• Take extreme ownership of delivery for the many teams that depend on our pipelines, keeping code flowing to production reliably and unblocking teams quickly when issues arise.

• Extend our supported delivery window by working from the Eastern time zone or further east, giving more teams more opportunity to deploy safely across more of the day.

• Drive throughput up by removing manual steps from the pipeline, tuning and optimizing our orchestration, and helping us stay ahead of fast-growing deployment demand.

• Lead thoughtful change management, recognizing that a change to how delivery works changes how every team ships, and preparing people for that change rather than just shipping it.

• Enable other engineers to deliver better over time through clear communication, guidance, and strong design. People will come to you with questions, and you'll leave them more capable.

• Use AI as a core part of how you work, leaning on agentic coding tools to research, design, and generate the deterministic pipeline code we need, so your time goes to thinking and design rather than hand-writing every line.