Engineering Manager

LiteLLM•San Francisco, CA

13d•$250,000 - $300,000

About The Position

LiteLLM is seeking an Engineering Manager to lead the team building the leading OSS AI gateway. This role involves owning team outcomes, processes, and productivity, including engineering productivity, code quality, release health, hiring, and managing the open-source community. The manager will hold engineers accountable to their metrics, maintain high quality while shipping fast, and handle enterprise relationships during escalations. This position offers director-level scope with a direct line to the Head of Engineering, reporting to the founder/CTO. The role tackles complex challenges such as managing over 100 provider integrations, handling day-zero model launches, and overseeing an ongoing Rust migration.

Requirements

Been an EM before, with a track record of managing and shipping through a team
Metrics-driven: has stood up reliability or productivity metrics (on-time ship rate, regressions per release, MTTR) and used them to find root causes
Has kept quality high on a fast-moving production system, with evidence of driving an incident or regression rate down (e.g. took P0s from X to Y)
Root-cause and incident management: can point to incidents they ran postmortems on and the recurrence rate dropping after
Process design: built tracking, review cadences, or release processes from scratch, with before/after numbers to show impact
Goal-setting and accountability: has improved a team's on-time delivery or commitment-hit rate
Customer-facing when it counts: has owned enterprise escalations and can show trust or retention held up after
Hiring and scaling: has filled a defined headcount plan and can speak to time-to-hire and quality bar
CS/engineering degree or equivalent hands-on engineering background
Worked at a startup, familiar with messy codebases and doing rewrites

Nice To Haves

Did this at an open-source company
Scaled the eng team at a fast-growing startup

Responsibilities

Hold engineers accountable to the metrics they set for themselves, and own the team's goals so they ship what they commit to
Keep release health high as the team moves fast: stand up tracking, run root-cause on what slips through, own a weekly quality sync
Drive well-architected, consistent code patterns across the team
Own the technical roadmap with the CTO, including the Rust migration, and keep big changes gradual rather than overnight rewrites
Own enterprise escalations end to end: a clear plan, crisp updates, and a fast path to resolution
Analyze capacity needs, define the roles, and hire the engineers when more capacity is needed
Look out for the open-source community and protect open-source adoption as the team scales