DevTool P3/P4 Developer

JOB TITLE :: DevTool P3/P4 Developer (Seven League)

JOB LOCATION :: Remote (EMEA or India time zones)

About the team

The Seven League team takes its name from the fairy tale boots that let you cover seven leagues in a single stride. Our job: make every engineer at CloudBees faster by building tools so good they don't need to ask.

We're a catalyst, not a bottleneck. We build the boots and hand them out.

We work across the full software development lifecycle: pipeline automation, AI-assisted workflows, self-service platforms, and whatever else removes friction. We ship code, not advice.

What you'll do

• Build reusable tooling that eliminates manual processes across the engineering org
• Work with engineering teams across the company to turn "ask me and I'll do it" into "here's a tool you can use anytime"
• Own projects end-to-end: from identifying the friction to shipping the solution
• Talk to the engineers you're building for, incorporate their feedback, iterate
• Participate in code reviews, push the bar, and mentor teammates

What we're looking for

Must have

• 5+ years of software engineering experience
• You reach for code when you see a repetitive process, you love building tools your peers actually use
• Excited about AI-assisted development and what's happening right now. Not watching from the sidelines.
• Strong communication and influencing skills. We work without authority. Adoption is earned, not mandated. If engineers don't use what we build, that's on us.
• Java. You've written production Java, not just read it
• Cloud (AWS or GCP or Azure) and Docker basics
• Collaborative by default. Strong opinions, loosely held. You give direct feedback with care and receive it the same way. The team gets better because you're on it.

Strong plus

• Jenkins. You've built on it as a developer, not just clicked through the UI. Deep knowledge (plugin development, Groovy DSL, internals) is a big bonus.
• You've built software start-to-finish using AI coding agents (Claude Code, Codex, Cursor). Not just autocomplete. Actually shipping things with them.
• Kubernetes

Nice to have

• Go
• Terraform
• Familiarity with other CI/CD ecosystems: GitHub Actions, GitLab CI, CircleCI, Tekton — the more you've touched, the better
• Open source tooling you've shipped that others use

Who this is for

You're a developer who is obsessed with the tooling layer. You've felt the pain of a slow pipeline, a flaky test environment, a deployment that takes five manual steps. Instead of accepting it, you fixed it. Permanently.

You believe the best way to help people is to give them better tools, and get out of their way. If that sounds obvious to you, we'll get along.