Senior ML Engineer | Kimchi (LLM Inference Optimization)

• 5+ years building real ML systems, with a portfolio that shows depth in inference or training infrastructure (not just model training notebooks).
• Strong Python - production services, not scripts.
• Hands-on experience with at least one of vLLM, SGLang, or TensorRT-LLM, and a working mental model of why an inference engine performs the way it does on a given GPU.
• Fluency with quantization tradeoffs - you've measured quality regressions, not just compression ratios.
• Comfort with distributed systems: collective communication, sharding strategies, and the practical failure modes of multi-GPU and multi-node setups.
• A bias toward measurement. You instrument before you optimize, and you can tell the difference between a real win and a benchmark artifact.
• Self-direction. This role comes with a wide mandate; you should be excited by that, not unsettled by it.

• Competitive salary (depending on the level of experience).
• Enjoy a flexible, remote-first global environment.
• Collaborate with a global team of cloud experts and innovators, passionate about pushing the boundaries of Kubernetes technology
• Equity options.
• Get quick feedback with a fast-paced workflow. Most feature projects are completed in 1 to 4 weeks.
• Spend 10% of your work time on personal projects or self-improvement.
• Learning budget for professional and personal development - including access to international conferences and courses that elevate your skills.
• Annual hackathon to spark new ideas and strengthen team bonds.
• Team-building budget and company events to connect with your colleagues.
• Equipment budget to ensure you have everything you need.
• Extra days off to help maintain a healthy work-life balance.

Throughput. Latency. KV cache utilization.

Move those three numbers in the right direction, and two things happen: customers get faster, cheaper inference, and our margins improve. That's the entire thesis of this role. Every kernel you tune, every quantization scheme you ship, every scheduler tweak you land shows up directly in a customer's p99 and on our P&L.
This is a high-impact seat. It is also a high-autonomy seat as you'll be given the room to lead the technical direction of inference optimization at Kimchi, not execute someone else's roadmap.

The problem: running LLMs in production is a moving target. The "right" model and serving configuration for a workload depend on traffic shape, sequence-length distribution, batch dynamics, GPU SKU, memory bandwidth, quantization tolerance, and a dozen other variables that shift week to week. Most teams pick a model once, over-provision GPUs, and absorb the cost. Kimchi is the system that makes that decision automatically - continuously matching workloads to the most cost-efficient, best-performing LLM and serving configuration on a customer's infrastructure. We're building the optimization layer between the model and the hardware, and we need engineers who understand both sides deeply.

• Push throughput. Continuous batching, speculative decoding, chunked prefill, kernel-level tuning across vLLM, SGLang, and TensorRT-LLM. Find the ceiling on each GPU SKU, then raise it.
• Cut latency. Attack TTFT and TPOT separately. Profile, identify the actual bottleneck (compute, memory bandwidth, scheduling, networking), and fix it - not the bottleneck you assumed.
• Get more out of the KV cache. Paged attention, prefix caching, eviction policies, cache reuse across requests, quantized KV. This is where a lot of the unrealized throughput lives, and it's an area you'll own.
• Quantize without regressing quality. INT8, INT4, FP8 across weights, activations, and KV. Empirical work: measure quality on real workloads, not just perplexity benchmarks.
• Shrink cold starts and memory footprint. Faster init, smarter weight loading, tighter memory accounting - the difference between a model that scales and one that doesn't.
• Scale across nodes. Distributed inference topologies, network-aware placement, checkpointing strategies that don't bottleneck on storage or interconnect.
• Set the technical direction. Decide what we benchmark, what we adopt, and what we build ourselves. Bring the team along with strong writeups and reproducible experiments.

Python; vLLM; SGLang; TensorRT-LLM; PyTorch; CUDA-adjacent tooling; Kubernetes; gRP; ClickHouse; PostgreSQL; GCP Pub/Sub; AWS / GCP / Azure; GitLab CI; ArgoCD; Prometheus; Grafana; Loki; Tempo.