Drimva

ByteDance

Software Engineer - Compute Infrastructure (Orchestration & Scheduling)

San Jose, California · Full-time · Posted Oct 28, 2026

Experience
2+ years of relevant industry experience; Ph.D. degree and strong publication records can be an exception.
Education
B.S./M.S. degree in Computer Science, Computer Engineering, or a related area; Ph.D. degree and strong publication records can be an exception.

About the job

Build and optimize Kubernetes-based compute infrastructure, scheduling systems, and platforms for large-scale AI/ML and LLM workloads.

What you'll do

  • Enhance global Kubernetes cluster management for performance, scalability, and resilience.
  • Design unified scheduling for diverse workloads and heterogeneous resources.
  • Develop AI-assisted scheduling and compute platforms for efficient ML/LLM training and inference.

What they ask for

  • B.S./M.S. in Computer Science, Computer Engineering, or a related area, with 2+ years of relevant industry experience; Ph.D. with strong publication records can be an exception.
  • Solid understanding of at least one of: Unix/Linux environments, distributed and parallel systems, high-performance networking systems, or large-scale software systems.
  • Experience designing, architecting, and building cloud or ML infrastructure, such as resource management, allocation, job scheduling, or monitoring.
  • Familiarity with Docker and Kubernetes; proficiency in at least one of Python, Go, C++, Rust, or Java.

Nice to have

  • Experience with large-scale cluster management systems such as Kubernetes, Ray, Yarn, or Mesos.
  • Experience in resource-efficiency management, job scheduling, application scaling, workload co-location, or isolation; public-cloud and ML-service experience is also preferred.

Tools

Kubernetes, Docker, Ray, Yarn, Mesos, Python, Go, C++

AI focus

Use AI models to optimize workload performance and resource utilization, and build compute platforms for ML and LLM training and inference.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)