Voices of Oxide (Interview)

What It Covers

Oxide Computer Company engineers discuss their custom server rack architecture, including Hubris operating system development, self-service update system challenges, and design philosophy. The team covers technical decisions around Rust, firmware development, and building hardware from first principles.

Key Questions Answered

• •Firmware Architecture: Oxide runs 64-70 instances of Hubris operating system across every rack component, from sub-50-cent microcontrollers to service processors. Each compute sled contains two copies minimum—one for service processing and one for root of trust security—because no single chip currently provides both required feature sets.
• •Update System Complexity: Self-service updates replace hundreds of software components across 32 sleds, 2 switches, and power controllers while maintaining system availability. The process takes approximately two hours and requires careful orchestration to avoid intermediate states where incompatible software versions communicate, using a plan-execute pattern for safety validation.
• •Rust Type Safety Benefits: The team uses Dropshot to generate OpenAPI specs from code and Progenitor to generate clients, ensuring API changes that break backwards compatibility fail at compile time rather than runtime. This approach catches incompatible enum variants and schema changes before deployment, eliminating entire classes of upgrade failures.
• •Uniform Compensation Model: Oxide pays all employees identical salaries regardless of role, with equity varying only by join date. This eliminates negotiation stress and prevents the $100,000 salary gaps common at companies like Google, where managers discover significant pay disparities among same-level team members after promotion cycles.
• •Design System Integration: The company uses a single UI design system across web console, marketing website, and physical hardware, maintaining consistent colors and elements. Industrial design decisions prioritize manufacturability at scale over prototype aesthetics, avoiding the common trap where mass production compromises initial design quality through cost-cutting measures.