Solutions Software Engineer

Do you love making software that solves real customer problems? At Oxide, it’s our mission to love our customers:
We recognize that our customers take a risk on us, and we love them for it. We work to deliver products that they will love in turn – and if and when our products fall short, our love for our customers trumps our own ego. Our customers depend on the integrations we build to successfully deploy, operate, and use Oxide.

As our customer base grows, so does the surface of integrations we need to build and maintain. We’re seeking a solutions software engineer with deep experience in Go or Rust and broad experience with cloud native and on-premises infrastructure to own the integrations between Oxide and the third‑party systems our customers rely on.

• Use your Go or Rust expertise to develop, document, and maintain seamless integrations with customer and third‑party systems (e.g., SDKs, Kubernetes integrations, IaC plugins, Open Telemetry components).
• Own integration issues from report to resolution, working directly with customers to understand their environment and unblock them, whether the root cause is in our code, a third‑party system, or the interaction between them.
• Understand the use cases of current and prospective customers to discover new integration opportunities and propose enhancements to existing integrations.
• Collaborate with current and potential software partners (e.g., platform providers, application providers, service providers) to ensure their offerings work well on, and with, Oxide.
• Contribute changes to Oxide when a current or future integration requires it, providing a better customer experience and a strong foundation for future work.
• Run your own workloads on Oxide to learn the product, develop customer empathy, and provide feedback to shape the overall product roadmap.

• Are comfortable context switching across different codebases, APIs, and ecosystems, often within the same day.
• Have broad experience with public cloud providers (e.g., AWS, GCP, Azure) and on‑premises infrastructure providers (e.g., VMware, Nutanix, Proxmox).
• Have deep experience with Kubernetes, including deploying and operating clusters and extending Kubernetes via controllers and plugins.
• Have demonstrated experience developing, extending, or integrating with container platforms (e.g., Open Shift, Rancher, Omni).
• Are experienced with infrastructure‑as‑code tooling, including building or contributing to providers and plugins (e.g., Terraform, Open Tofu, Pulumi, Ansible).
• Have experience with enterprise storage and networking technologies (e.g., S3‑compatible APIs, SMB, iSCSI, NVMe‑oF, VPCs, HAProxy, Metal
  
  LB).
• Have worked with observability platforms and understand how to instrument systems for operators (e.g., Open Telemetry, Prometheus, Grafana, Datadog, Honeycomb).
• Enjoy reading and writing technical documentation, tailoring it to the audience — whether that’s a customer, a teammate, or a future contributor.
• Are very comfortable at a Unix terminal.
• Don’t mind coworkers getting really excited about decades‑old computers.

• Listen to Solutions Software Engineering with Matthew Sanabria to learn about our approach to engineering the integrations that customers need.
• Watch the following Cloud Field Day presentations to understand the product, its value, and see a demonstration of the integrations built by fellow Solutions Software Engineers.
  • What is the Oxide Cloud Computer?
  • What Does Oxide Value Mean to Oxide Computer Company?
  • Oxide Integrations:
    Empowering Platform Teams and Developers with Oxide Computer
• Browse our public Requests for Discussion to get a flavor for how we work. A few relevant RFDs:
  • RFD 493 Initial Kubernetes Integrations
  • RFD 574 Packer Plugin
• Listen to, or watch, Inside Oxide on Changelog & Friends to learn about the expansion of the company and team.
• Listen to Hiring Processes with Gergely Orosz to familiarize yourself with the Oxide hiring process.
• Listen to some of our episodes of Oxide and Friends. A few recommendations:
  • RTO or GTFO on our perspective on the rash…