Principal Software Engineer, Chainguard

• 12+ years designing, building, and operating infrastructure for language ecosystems or developer platforms, (build systems, package registries, or CI/CD serving widely-used libraries or services) with demonstrated Principal-level scope: setting technical direction across multiple teams, not just owning a single system
• Direct experience standing up or significantly extending platform support for a language ecosystem- i.e. you've done the "onboard a new toolchain/packaging model into an existing platform" problem before, ideally including .NET (NuGet), Go (modules), or Rust (Cargo)
• Strong proficiency in Go, with the judgment to know when a new ecosystem's idioms should bend the platform and when the platform should hold its ground
• A track record of automating away manual remediation steps. You can point to a workflow you took from "engineer does this by hand" to "system does this reliably," including the judgment calls about where automation is safe and where a human checkpoint still matters
• Deep background in CI/CD, agentic pipelines, cloud-native infrastructure, and IaC: containers (Docker/OCI, Kubernetes), Terraform, and pipeline tooling (GitHub Actions, Argo, Tekton, or equivalents) with experience running these at scale across heterogeneous ecosystems
• Demonstrated ability to diagnose and resolve deep toolchain, compiler, and packaging failures across multiple ecosystems, and to turn one-off fixes into systemic prevention
• Excellent written communication in a remote, distributed environment. Principal-level influence here happens mostly through docs, RFCs, and review, not just code
• A Principal ownership mindset: you set direction other engineers build against, you're comfortable being the person who has to make the ecosystem-generalization call with incomplete information, and you actively shape both the roadmap and engineering culture

Desirable

• At Chainguard, we think the best platform work is invisible: the libraries just appear, the builds just work, and the CVEs quietly regret their life choices
• Chainguard's Libraries organization runs the secure, reliable factory that continuously builds, verifies, and serves open-source libraries to customers and internal teams across multiple ecosystems
• We're expanding that factory to new inbound ecosystems, while raising the bar on how much of the remediation and build lifecycle runs without a human in the loop
• As a Principal Software Engineer on the Libraries Platform team, you'll set technical direction for that expansion
• This is a strategic, cross-organizational platform role: you're not just operating the existing factory, you're deciding how it generalizes to ecosystems it wasn't originally built for, and how much of the remediation pipeline - from CVE detection through patch, rebuild, verification, and release - can become fully automated rather than engineer-mediated
• Your decisions will shape the platform's architecture for years and influence how every ecosystem team builds on top of it
• Own the technical strategy for multi-ecosystem scaling. Define the architecture that lets the Libraries Platform onboard new language ecosystems (.NET, Go, Rust) without re-deriving core services per ecosystem: generalizing package indexing, build orchestration, and metadata services so they're ecosystem-agnostic where possible and cleanly extensible where not
• Drive end-to-end remediation automation. Lead the redesign of CVE remediation workflows to close the loop from detection to verified, released fix with minimal manual intervention, rebuild triggering, SBOM and provenance regeneration, policy verification, and rollout, across all supported ecosystems
• Push the frontier on novel patch generation. Set the direction for agentic/AI-driven systems that synthesize security fixes when no upstream patch exists yet — not just selecting or backporting existing ones — and design the guardrails (automated validation, regression testing, provenance, and human checkpoints) that make machine-generated patches safe to ship across ecosystems
• Set platform-wide technical direction, spanning the package index, build/packaging pipelines, registry mirrors, and orchestration tooling that serve external customers and internal ecosystem teams at scale
• Make foundational build vs. buy and sequencing calls for bringing .NET, Go, and Rust online, identifying what's genuinely novel about each ecosystem's toolchain, packaging, and dependency model, and what can reuse or extend existing platform primitives
• Partner at the org level with Ecosystem teams (Java, JavaScript, Python/AI/ML, and new-language leads), Platform, Delivery, Sustaining, and Security to align the platform roadmap with where the business is taking on new ecosystem risk and commitments
• Raise the technical bar across the org: mentor Staff and Senior Engineers, drive design reviews for the biggest architectural bets, and write the docs and RFCs that let other teams build correctly on the platform without you in the room
• Own reliability and scalability at the platform level: define SLOs for the expanded remediation pipeline, and lead incident response and postmortems for the platform's most consequential failures
• Get hands-on when it matters: dig into toolchain, compiler, and dependency-resolution problems specific to new ecosystems (e.g., NuGet, Go modules, Cargo) when they threaten the pipeline's reliability or timeline