Cloud Engineer

ABOUT THE ROLE Hi, I'm Scott Adair. I lead the Cloud Engineering team at Jane, and I've been here for 2 years. My team is responsible for building and running Shipyard, our internal developer platform that gives product teams the power to deploy and operate their services without waiting on infrastructure. We're building the golden paths, CLI tooling, and Kubernetes workflows that let engineers focus on what they actually care about: shipping great software The work we do sits close to the foundation of everything Jane delivers. Thousands of clinics depend on Jane every day, and our team is part of what makes sure the platform underneath that experience is healthy, observable, and easy to build on. That's the kind of work that has real, visible impact. I've been a tinkerer from the very beginning. From taking apart my first computer on Christmas morning to understand how it worked, to building Jarvis my personal Ai Assistant. I love to build things, and understand how they work. I'm looking for a Cloud Engineer at the L2 level to join the Shipyard team: someone hands-on, genuinely curious about platform engineering, and motivated by making other developers' lives better. If you're the kind of person who asks "how will engineers actually use this?" before you write a single line, this role is for you. https://www.linkedin.com/in/scottie-adair/ WHAT IMPACT WE'RE LOOKING FOR YOU TO MAKE - Build and maintain production infrastructure on AWS EKS using Terraform and Helm, delivering the platform reliability that product teams count on to ship with confidence. - Develop Shipyard's self-service capabilities, from CLI tooling to GitOps pipelines via ArgoCD, so that getting code from a developer's laptop to production is fast, predictable, and low-friction. - Own your on-call responsibilities with care, contributing to runbooks and post-mortems that make every incident shorter than the last and every system a little more observable than before. - Collaborate directly with product managers to understand where platform tooling creates friction, then design and deliver improvements that meaningfully reduce toil for the people depending on Shipyard. - Communicate clearly and consistently, through documentation, code reviews, and team discussions, building the kind of shared understanding that helps a distributed team stay aligned and move fast. WHAT EXPERIENCE WE NEED - Hands-on experience with Kubernetes in production environments, including cluster operations, Helm, RBAC, networking, and debugging workloads. EKS experience specifically is a strong plus. Typically this is someone with 3 to 5 years of infrastructure or platform engineering experience, though we care more about what you've shipped than how long you've been shipping it. - Terraform proficiency that goes beyond syntax: you've written modules, managed remote state, and have a point of view on structure. You understand why infrastructure-as-code exists, not just how to use it. - AWS fluency in core services as well as container orchestration services, with a clear understanding of how these pieces connect to EKS workloads and the engineers who depend on them. - A platform engineering mindset: you've built something other engineers consume, a CLI, a shared module, a pipeline template, and you cared about the experience of using it, not just whether it technically worked. - Comfort with observability concepts beyond basic monitoring (SLIs, SLOs, structured logging, distributed tracing), and experience with scripting in Python or Bash to automate operational tasks. Familiarity with AI coding tools like Cursor or Claude Code as a genuine accelerant, with the judgement to know when not to trust them, is a real plus. If you don't meet every single qualification but are excited about this role, we'd still love to hear from you. MORE ABOUT JANE Jane is a founder-led, high-growth SaaS company born in North Vancouver, British Columbia. We’re now a team of more than 700 people working remo