About the role
Overview Inferact's mission is to grow vLLM as the world's AI inference engine and accelerate AI progress by making inference cheaper and faster. Founded by the creators and core maintainers of vLLM, we sit at the intersection of models and hardware, a position that took years to build.
About
the Role We're looking for a Developer Relations Engineer to help make vLLM the default way developers understand, build, and scale AI inference. This is not a generic DevRel role. We're looking for a inference systems educator-builder: someone who can understand vLLM as a deep LLM inference systems project, teach hard technical concepts clearly, and create public artifacts that help practitioners build better systems. You'll write technical deep dives, build demos, create tutorials, contribute to docs and examples, host workshops, and help developers understand topics like KV cache, continuous batching, prefix caching, prefill and decode, quantization, GPU serving, latency versus throughput, and model-server tradeoffs across vLLM and adjacent systems. Your work will shape how the broader AI infrastructure community learns, adopts, and builds with vLLM. Skills and
Qualifications Minimum
qualifications: Bachelor's degree or equivalent experience in computer science, engineering, machine learning, systems, or similar. Strong technical understanding of LLM inference systems, model serving, GPU inference, distributed runtimes, scheduling, batching, quantization, or related infrastructure. Ability to credibly explain systems concepts such as KV cache, PagedAttention, continuous batching, prefill / decode scheduling, prefix caching, speculative decoding, tensor parallelism, data parallelism, or latency versus throughput tradeoffs. Experience with vLLM or adjacent inference technologies such as SGLang, TensorRT-LLM, TGI, LoRAX, Ray Serve, FlashInfer, BentoML, Baseten-style serving platforms, or similar systems. A strong public portfolio of technical artifacts, such as blogs, tutorials, workshops, courses, OSS docs, benchmark posts, architecture explainers, conference talks, demos, or runnable repositories. Ability to write and teach for practitioners without sounding like a content marketer. Strong engineering judgment, product taste, and ability to turn raw technical material into useful developer education. Preferred