Posted 13 Apr 2026 (205 days ago) · Job 2935 · Read from the employer's Ashby board, last checked 5 Nov 2026, 08:25 UTC

Member of Technical Staff (AI Inference Engineer)

Perplexity · San Francisco, California; Palo Alto, California; New York City, New York

Apply on Perplexity’s siteAsk about this jobApply opens the employer’s own application. Nothing is sent from here.

What the posting says

Each fact carries its state:Statedfound in the postingConflictstwo statements disagree, both quotedNot mentionedthe posting does not say

PayStated
$220,000–$485,000 a year
Employment typeStated
Full time

Not mentioned in this posting

“Not mentioned” means the posting does not say. It is not a no. You could ask the recruiter.

Work arrangementNot mentioned
The posting does not say
ShiftNot mentioned
The posting does not say
ExperienceNot mentioned
The posting does not say
EducationNot mentioned
The posting does not say
Visa sponsorshipNot mentioned
The posting does not say

Requirements, each with its sentence from the posting

These are the employer’s words. The index does not judge whether you meet them.

  • No requirement has been itemised for this posting yet. The employer’s words are in the full posting below.
Read the full posting as the employer wrote it

We build and run the inference engine behind every Perplexity query and deploy dozens of model architectures at scale with tight latency and cost budgets. Our stack is Rust, Python, CUDA, and CuTe DSL - and we need another engineer to join us.

What you will work on

Examples of real work the team does:

  • New models support. Support transformer-based retrieval, text-generation, and multimodal models in our inference infrastructure, from weight loading, request scheduling and KV-cache management to support in API Gateway.

  • GPU kernels migration to CuTe DSL. Port our in-house CUDA kernels to NVIDIA's CuTe DSL so they run on GB200 today and are portable to Vera Rubin racks tomorrow.

  • Rust-native serving runtime. Develop our internal Rust-based inference server to solve all Python pains and keep up with rapidly growing traffic.

  • Performance optimisation. Profile and fix bottlenecks from network ingress through continuous batching and GPU kernel interleaving.

  • Reliability and observability. Build dashboards, alerts, and automated remediation so we catch regressions before users do. Respond to and learn from production incidents.

Who we're looking for

  • Deep experience with GPU programming and performance work (CUDA, Triton, CUTLASS, or similar). Any other deep systems programming experience is a plus.

  • You understand modern LLM architectures and are able to bring them up reliably in a production environment.

  • You've built and operated production distributed systems under real load - ideally performance-critical ones.

  • Comfortable working across languages and layers: Rust for the serving runtime, Python for model code, CUDA/CuteDSL for kernels.

  • You own problems end-to-end. You can read a research paper on Monday, write a kernel on Wednesday, and debug a production incident on Friday.

  • Self-directed. You do well in fast-moving environments where the path forward isn't laid out for you.

Good if you touched any of

  • ML compilers and framework internals: PyTorch internals, torch.compile, custom operators.

  • Distributed GPU communication: NCCL, NVLink, InfiniBand, RDMA libraries, model/tensor parallelism.

  • Low-precision inference: INT8/FP8/FP4 quantization, mixed-precision serving.

  • Profiling and debugging tools: Nsight Compute/Systems, CUDA-GDB, PTX/SASS analysis.

  • Container orchestration: Kubernetes, GPU scheduling, autoscaling inference workloads.

Qualifications

  • 3+ years of professional software engineering experience with meaningful work on ML inference or high-performance systems.

  • Familiarity with at least one deep learning framework (PyTorch, JAX, TensorFlow).

  • Understanding of GPU architectures (memory hierarchy, warp scheduling, tensor cores).

  • Understanding of common LLM architectures and inference optimization techniques (e.g. quantization, speculative decoding, prefill-decode disaggregation).

The posting text is reproduced as the employer wrote it; the index adds nothing to it.