Senior Software Engineer (Developer Tooling)

TL;DR: We’re seeking a platform-minded software engineer to build and own the developer-facing tools that sit at the heart of how engineers integrate with Cloudsmith. About Cloudsmith Cloudsmith is building the operating system for the modern software supply chain.

We run a global, fully managed, multi-tenant SaaS platform that helps organizations, from startups to Fortune 500 companies, secure, govern, and distribute software artifacts at scale.

Worldwide, our customers use Cloudsmith as a critical infrastructure control plane for CI/CD, developer workflows, security controls, compliance, and software distribution, supporting 30+ formats and ecosystems across languages, containers, and operating systems.

We recently raised our Series C to accelerate Cloudsmith 2.0: deeper artifact intelligence, stronger policy and provenance, faster package-aware delivery, and infrastructure built for engineering teams, as well as the modern AI-driven software factory.

By developers, for developers: we care about craft, architecture, and enterprise scale.

**The Role** In this role, you’ll be responsible for building and maintaining the tools that many of our customers use every single day - in some cases, they’re the only part of Cloudsmith that those engineers ever touch. That means the CLI, Terraform provider, MCP integration, IDE extensions, and more. These are durable, platform-grade interfaces that need to evolve carefully and responsibly alongside the core Cloudsmith platform - built to last, and owned for the long term.

You’ll work closely with Customer Success, Solutions Engineering, and real external customers to make sure what you build reflects how developers actually work in the wild.

If you love building tools that other engineers rely on, think carefully about interface design and ergonomics, and get satisfaction from making complex things feel simple - this role is for you.

**Key Responsibilities**

• Build and maintain Cloudsmith’s developer-facing integrations: including the CLI, Terraform provider, MCP server, and IDE/LSP extensions, treating them as first-class platform products.
• Design interfaces that stand the test of time: You’ll think carefully about versioning, backwards compatibility, and the downstream impact of every change you ship, because thousands of engineers will have these tools embedded in their workflows.
• Own the full software development lifecycle for your work: from design and development through testing, release, and long-term support - aligned with Cloudsmith’s engineering standards and practices.
• Stay close to the platform: You’ll work in lockstep with the broader engineering organization to ensure developer tooling keeps pace with platform evolution, and surface any integration concerns early.
• Turn customer feedback into durable solutions: Working with Solutions Engineering and Customer Success as internal stakeholders, you’ll translate real-world pain points into general-purpose tooling improvements that scale across the entire customer base.
• Champion developer experience: You’ll bring strong opinions about what makes a CLI, SDK, or IDE plugin a joy to use, and advocate for the user - the software engineer - at every step.
• Contribute to a culture of automation: If something can be automated - testing, releases, validation, the works - you’ll help make it so.

Required Experience, Qualities & Skills

• Experience: 3+ years of professional software engineering experience, with a track record of shipping and maintaining production-grade software.
• Strong API and interface design instincts: You understand the cost of a breaking change, know how to version things sensibly, and design with the consumer of your interface front of mind.
• Proficiency in at least one strongly-typed language: (Go, Python, TypeScript, or similar) and comfort picking up others as needed. Cloudsmith’s CLI and tooling surface spans multiple languages and environments.
• Security awareness: You understand secure coding practices, and you’re comfortable thinking about how credentials, tokens, and access patterns flow through the tools you build.
• Familiarity with CI/CD ecosystems and modern DevOps toolchains: the environments your tools will live in.
• Clear, confident written communication: You can write a well-reasoned RFC, a sensible changelog, and a README that developers actually read.
• A genuine empathy for other engineers as users:…