Software Engineer, Mithril

• The profile we're hiring for is a generalist with strong backend instincts — someone who has shipped and maintained production systems at real scale, and is comfortable owning features across the full stack when needed
• Strong Python backend skills — you've built and maintained production APIs at real scale, not just prototypes
• Proven experience with distributed systems; comfortable with messaging systems (RabbitMQ, Kafka) and RPC methods (gRPC, protobuf, tRPC)
• Fluency with relational databases: schema design, query optimization, and migrations in production environments
• Ability to own a feature end-to-end — from design doc through backend API, database migration, feature flag rollout, and monitoring
• Strong debugging instincts: calm and systematic when triaging production incidents, with a bias toward durable fixes
• Comfortable in small teams where ownership is high and process is lightweight
• We emphasize that candidates need not fulfill every expectation listed to be eligible for this position. Our objective is to cultivate a diverse team encompassing a spectrum of backgrounds, experiences, and skill sets

Desirable

• We are at an inflection point: transitioning from bare-metal operations to a cloud-native, multi-provider platform with a differentiated auction and flexibility model. You would be joining at the moment the platform is being built, not inherited
• You will work across Mithril's three core engineering areas — Consumption (the developer-facing product, billing, and API surface), Platform (the orchestration and marketplace engine), and Supply (integrations with cloud providers and capacity management)
• You will own meaningful slices of each, shipping features end-to-end against a product that handles real revenue and business-critical customer workloads
• This is not a single-domain role. You'll move between backend systems, marketplace logic, and customer-facing surfaces — with direct exposure to the architectural decisions shaping how Mithril scales
• Most early-stage engineering roles at infrastructure companies are either deep in systems (little product surface) or deep in product (little systems exposure). At Mithril, you'll work across both: the orchestration engine that manages GPU capacity across providers, and the developer-facing surfaces that customers use to reserve, bid, and consume that capacity
• The systems you build will handle real money, real workloads, and real market dynamics — spot auctions, reservation pricing, and capacity allocation across a heterogeneous supply base. If you want to understand how GPU infrastructure markets actually work and build the systems that run them, this is that role
• Build and maintain backend Python APIs powering Mithril's reservation, bidding, billing, and usage surfaces — including usage visualization and the billing platform
• Write and maintain database migrations, design relational schemas for complex multi-entity models (orders, allocations, grants, quotas), and optimize queries for performance
• Own features end-to-end: from design doc through backend API, database migration, feature flag rollout, and monitoring
• Design and implement orchestration primitives for flexible reservations: pause/return credits, reservation extensions, capacity algorithm updates, and the auction model connecting spot and reserved capacity
• Contribute to operational maturity — quota systems, financial controls, fraud prevention, and inventory management automation — so Mithril can scale supply sources without scaling headcount linearly
• Contribute to supply-side integrations, bringing GCP, Nebius, and OCI resources under Mithril management through the Mithril API
• Build tooling to give operators visibility into managed capacity and surface supply constraints early
• Build consumption tooling to help developers make better decisions: reservation calculators, bid modeling, cost dashboards, and CLI extensions
• Work across the client frontend to ship customer-facing features including usage graphs, billing views, and reservation management UIs
• Participate in on-call rotations, triage production incidents, and contribute to operational runbooks and automation that reduce toil over time