> Markdown version of [/jobs/ext/3627401-senior-staff-software-engineer-cloud-availability-platform](https://www.wearedevelopers.com/jobs/ext/3627401-senior-staff-software-engineer-cloud-availability-platform). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Staff Software Engineer, Cloud Availability Platform - **Company:** Crusoe's Inc - **Location:** Sunnyvale, CA, United States - **Experience:** Expert - **Salary:** $250,000.0 - $300,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Systems Engineering, Intelligent Platform Management Interface, Cloud Computing, Programming Tools, Distributed Systems, Firmware, InfiniBand, Python (Programming Language), Role-Based Access Control, Software Engineering, Graphics Processing Unit (GPU), Control Structures, Mttr, Agentic-AI, Event Driven Architecture, Build Management, Kubernetes, Bare Metal, Front End Software Development, Api Gateway, Api Management - **Published:** October 8, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=9f4aaa1b94a254f0 ## About the Role * 10+ years building distributed systems, control planes, or infrastructure platforms. * Strong software engineering skills in Go, Python, or Rust. * Experience building platforms other engineers consume: public or internal APIs, SDKs, or developer tooling with real adoption. * Depth in at least one of: workflow/orchestration engines (Temporal or similar), event-driven architectures, graph data models, policy/rules engines, or reconciliation-based control loops (Kubernetes operator patterns). * Experience running what you build: you have carried a pager for a platform other teams depend on. * Systems thinking across the hardware/software boundary. Bonus experience * Internal developer platforms: API gateways, service catalogs, Backstage-style portals, micro frontend architectures. * GPU or bare-metal fleet infrastructure: DCGM, Redfish/IPMI, firmware lifecycle. * High-cardinality observability platforms (per-GPU telemetry at fleet scale). * InfiniBand or RoCE fabrics. * AI agents applied to infrastructure triage and autonomous remediation. ## Description * Agents on every site and host that collect telemetry and execute commands. * A distributed infra graph: Models system connections down to the rack, fabric, power, and cooling layers. By integrating these connections with telemetry signals, the platform can precisely trace events to identify their blast radius and root cause. * A reconciliation core: workflow engine, policy engine, and state reconciler that continuously close the gap between intended state and reality, exposed through the API gateway. * Domain services: Services spanning provisioning, firmware upgrade, validation, deployment, repair and RMA, capacity, power and thermal, and Day-2 operations. Built once, run fleet-wide, consumable by any team through APIs and SDKs. We operate on a continuous autonomy loop-sense, correlate, reason, act, learn-incorporating guardrails that evolve from recommendation to full automation. We treat every recurring manual intervention as a signal to engineer the next automation. You'll thrive here if you * Want to build a platform, not integrate one. This is core distributed-systems engineering: event buses, graph models, reconciliation loops, policy evaluation. * Treat internal engineers as customers and sweat API ergonomics, docs, and onboarding the way product teams sweat UX. * Like owning a hard abstraction and defending it as ten teams build on top of you. * Believe the interesting problems are where physical infrastructure meets software: a firmware counter, a thermal event, and a scheduling decision are one problem, not three. * Measure yourself by what stops paging humans, and by how fast another team ships on your platform. What you'll do * Design and build core platform services: RBAC, tenancy, the workflow engine, policy engine, and state reconciler that drive fleet actions safely at scale. * Design the public face of the platform: the API gateway, resource model, and versioned API contracts that fleet, SRE, and product teams build against. * Build SDKs, workflow templates, and golden paths that make the platform self-serve, plus the developer portal and micro frontend framework that let teams bring their own UI surfaces. * Build the inventory and topology graph as the fleet's source of intended truth, and the pipelines that keep it honest against reality (metadata drift is one of our top verified incident root causes; you will kill it). * Build site, GPU, and network agents and the event bus that moves fleet telemetry and commands reliably. * Deliver the platform roadmap: pilot site on the foundation layer, first site deployed entirely through the platform, zero-downtime firmware upgrades, first fully automated RMA, then 100K+ GPUs on platform with MTTD under 60 seconds and MTTR under 30 minutes. * Work with embedded engineers from fleet and production engineering who bring the operational scar tissue, and turn it into services other teams extend.