> Markdown version of [/jobs/ext/4648993-software-engineer-member-of-technical-staff-platform](https://www.wearedevelopers.com/jobs/ext/4648993-software-engineer-member-of-technical-staff-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). --- # Software Engineer - Member of Technical Staff (Platform) - **Company:** MITHRIL LTD., INC. - **Location:** San Francisco, CA, United States - **Salary:** $170,000 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Cloud Computing, Relational Databases, Software Design Documents, Programming Tools, Distributed Systems, Fraud Prevention and Detection, Protocol Buffers, Enterprise Messaging Systems, Query Optimization, RabbitMQ, Prometheus, Linux Containers, Software Engineering, Systems Integration, TypeScript, WebSocket, Datadog, Graphics Processing Unit (GPU), Real Time Systems, Docker Swarm, ReactJS, Grafana, Backend, Event Driven Architecture, Database Migration, Kubernetes, Apache Kafka, Front End Software Development, Hardware Infrastructure, Terraform, Marketplace, Oracle Cloud Infrastructure, Grpc - **Published:** November 9, 2026 - **Apply:** https://www.careerbuilder.com/job-details/software-engineer-member-of-technical-staff-platform-san-francisco-ca--3fd20bfb-8374-4a35-b7c5-039049d1f021 ## About the Role Software Engineering, Startup, Artificial Intelligence (AI), Funding, GPU (Graphics Processing Unit), Scientific Research, Venture Capital, Cloud Computing, Capacity Management, Application Programming Interface (API), 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., * Experience with marketplace and billing systems - especially variable-usage, auction-based, or complex reservation models. * Familiarity with Kubernetes, AWS infrastructure, or cloud provider APIs (GCP, OCI, Nebius). * Familiarity with Linux containers and container orchestration (Docker Swarm, Nomad). * Comfort working across the stack - Python backend and TypeScript/React frontend. * Experience with developer tools or CLIs (bonus: SkyPilot or similar frameworks). * Proficiency with infrastructure-as-code (Terraform, Kustomize) or observability tooling (Grafana, Prometheus). * Background in real-time systems: SSE, WebSockets, or event-driven architectures. * Prior experience at a startup where you wore multiple hats and shipped across domains. ## Description 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. What Makes This Role Different 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. Core Responsibilities Backend & API * 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. Platform & Marketplace * 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. Supply Integrations * 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. Consumption & Developer Tooling * 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. Operations * Participate in on-call rotations, triage production incidents, and contribute to operational runbooks and automation that reduce toil over time.