Staff Software Engineer, Model Infrastructure

Harvey Harvey · AI Frontier · San Francisco, CA · Engineering

Staff Software Engineer on the Model Infrastructure team to lead the design and development of systems powering AI requests, focusing on a reliable, scalable, observable, and efficient platform for AI inference, model control, and provider integration.

What you'd actually do

  1. Lead the design and implementation of Harvey's Model Infrastructure platform.
  2. Build systems to ensure high availability, low latency, and operational excellence for AI inference.
  3. Design and improve Harvey's Unified Model Controller (UMC) and Model Selector platform to automatically detect model degradations and intelligently route traffic based on reliability, latency, quality, compliance, and cost.
  4. Develop systems for model provisioning, capacity management, failover, and traffic engineering across multiple AI providers.
  5. Integrate new model providers and maintain provider APIs and SDKs, enabling Harvey to rapidly adopt emerging frontier models.

Skills

Required

  • 7+ years of software engineering experience building large-scale distributed systems.
  • Experience designing and operating highly available production services.
  • Strong programming skills in Go, Java, Python, Rust, or C++.
  • Deep understanding of distributed systems, cloud infrastructure, networking, and observability.
  • Experience leading technical projects across multiple engineering teams.
  • Ability to balance long-term architecture with pragmatic execution.
  • Strong communication and collaboration skills.
  • Passion for building foundational platforms that enable other engineering teams.

Nice to have

  • Experience with AI infrastructure, LLM serving, or machine learning platforms.
  • Experience with model routing, inference gateways, or policy-based serving systems.
  • Experience working with OpenAI, Anthropic, Azure OpenAI, Fireworks, Baseten, or open-source LLMs.
  • Experience with Kubernetes, cloud infrastructure, and service mesh technologies.
  • Experience with large-scale observability and SRE best practices.
  • Experience with data infrastructure technologies such as Kafka, Spark, Flink, Airflow, or Iceberg.
  • Familiarity with GPU infrastructure or model training platforms.

What the JD emphasized

  • highly reliable
  • scalable
  • observable
  • efficient
  • high availability
  • low latency
  • operational excellence
  • model degradations
  • intelligently route traffic
  • reliability
  • latency
  • quality
  • compliance
  • cost
  • failover
  • traffic engineering
  • rapidly adopt emerging frontier models
  • health dashboards
  • alerting
  • token usage analytics
  • cost reporting
  • end-to-end telemetry
  • model launches
  • experimentation
  • proactive monitoring
  • production AI workloads
  • infrastructure efficiency
  • capacity planning
  • utilization optimization
  • cost visibility
  • infrastructure foundation
  • model evaluation
  • training
  • deployment
  • cross-functional technical initiatives
  • mentor engineers
  • Model Reliability & Operations
  • Automated failover and recovery
  • Capacity provisioning
  • Operational tooling and incident automation
  • Unified Model Controller (UMC)
  • Policy-based model routing
  • Intelligent Model Selector
  • Traffic management
  • Reliability and latency optimization
  • Provider Platform
  • Multi-provider architecture
  • API and SDK integrations
  • Rapid adoption of new frontier models
  • Observability & Cost Platform
  • Token usage analytics
  • Cost attribution
  • Latency and reliability dashboards
  • Capacity forecasting
  • Utilization optimization
  • AI Platform Foundation
  • Infrastructure supporting model evaluation
  • Model deployment and operations
  • Future model training platform
  • Agent infrastructure
  • large-scale distributed systems
  • highly available production services
  • distributed systems
  • cloud infrastructure
  • networking
  • observability
  • technical projects
  • foundational platforms

Other signals

  • building a platform
  • high availability
  • low latency
  • operational excellence
  • model routing
  • multi-provider architecture
  • observability