Founding Developer Relations

LiteLLM•San Francisco, CA

12d

About The Position

LiteLLM is the open-source AI gateway used by developers and enterprises to access, manage, and govern LLMs through a unified interface. Teams use LiteLLM to route requests across model providers, control spend, monitor usage, implement security policies, and reliably operate AI applications in production. We are looking for our first Developer Relations hire to help more developers discover LiteLLM, understand what they can build with it, and successfully deploy it in production. LiteLLM has a large and growing technical community. Developers discover the project through GitHub, documentation, search, technical content, and recommendations from other engineers. Developers need to quickly understand how LiteLLM fits into their stack, see credible examples of it solving real problems, and get from their first request to a production deployment. They also need clear ways to share feedback, contribute to the project, and learn about new capabilities. You will help us build that developer journey. This is LiteLLM’s first dedicated Developer Relations role. You will establish how we educate developers, engage with the community, support product launches, and turn developer feedback into better documentation, examples, and product decisions.

Requirements

Experience in Developer Relations, Developer Advocacy, software engineering, solutions engineering, or another highly technical developer-facing role.
Can write working software and are comfortable building examples in Python.
Can read an unfamiliar codebase, debug integrations, reproduce issues, and communicate clearly with engineers.
Exceptional technical communicator who can make complex infrastructure concepts understandable without oversimplifying them.
Enjoy talking with developers and are genuinely curious about how they build and operate software.
Strong product instincts and notice where APIs, workflows, examples, or documentation create unnecessary friction.
Can create across multiple formats, including sample applications, written tutorials, technical talks, workshops, and video.
Comfortable being a visible external representative of a technical product and open-source project.
Operate with high ownership and do not need an existing playbook to begin shipping useful work.
Care about whether your work changes developer behavior, improves implementations, and produces meaningful product learning.
Can move quickly without compromising technical accuracy.
Can write working software and are comfortable building examples in Python.
Can read an unfamiliar codebase, debug integrations, reproduce issues, and contribute technical fixes.
Exceptional technical communicator. Can explain a complex infrastructure concept without oversimplifying it.
Enjoy talking to developers and are genuinely curious about how they build software.
Strong product instincts and notice where workflows, APIs, or documentation create unnecessary friction.
Comfortable producing across formats, including written tutorials, sample applications, presentations, workshops, and videos.
Operate with high ownership and do not wait for someone else to define the playbook.
Analytical and care about whether your work drives adoption, activation, and successful deployments.
Can move quickly while maintaining a high bar for technical accuracy.

Nice To Haves

Experience with developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.
Familiarity with LLM application architecture and the challenges of operating AI systems in production.
Experience with AI model providers, gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.
Meaningful contributions to an open-source project.
Experience building a technical audience through writing, videos, workshops, talks, or community participation.
Experience establishing Developer Relations at an early-stage company.
Experience working with platform engineers, infrastructure teams, or enterprise developers.
An existing body of technical work you can show us, such as applications, tutorials, talks, videos, documentation, or open-source contributions.
Worked on developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.
Understand LLM application architecture and the challenges of operating AI systems in production.
Experience with model providers, AI gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.
Maintained or contributed meaningfully to a successful open-source project.
Built a technical audience through writing, videos, workshops, or community participation.
Created developer programs or content from scratch at an early-stage company.
Previously worked directly with enterprise developers or platform-engineering teams.

Responsibilities

Build and maintain runnable demos, sample applications, integrations, and reference architectures for real LiteLLM use cases.
Create technical guides, videos, workshops, launch demos, and deep dives that make complex capabilities understandable and immediately usable.
Engage directly with developers through GitHub, community channels, livestreams, meetups, conferences, and other technical forums.
Partner with Product and Engineering on launches so new capabilities ship with strong examples, documentation, and a clear technical story.
Identify recurring questions and points of friction, then turn them into better documentation, examples, product feedback, issues, or code contributions where appropriate.
Explore the wider AI developer ecosystem and build useful examples with the models, frameworks, tools, and platforms LiteLLM users care about.
Use developer feedback and adoption data to decide which educational resources, integrations, and community initiatives will have the greatest impact.
Represent LiteLLM publicly through technical talks, workshops, videos, podcasts, and conversations with the developer community.
Create high-quality tutorials, demos, sample applications, reference architectures, videos, and technical deep dives.
Develop educational resources around the problems developers are actively trying to solve.
Explain LiteLLM capabilities such as model routing, fallbacks, cost controls, observability, authentication, guardrails, MCP, and production deployment.
Keep examples and technical content accurate as LiteLLM and the wider AI ecosystem evolve.
Improve the path from reading about a capability to successfully implementing it.
Build genuine relationships with developers using, evaluating, and contributing to LiteLLM.
Participate in GitHub discussions, community channels, technical forums, and open-source conversations.
Help developers get unstuck while identifying patterns that should become durable resources or product improvements.
Support contributors and power users and create opportunities for them to share what they have built.
Represent LiteLLM at relevant conferences, meetups, workshops, livestreams, podcasts, and community events.
Build a structured feedback loop between the developer community and LiteLLM’s Product and Engineering teams.
Identify recurring points of confusion, missing integrations, documentation gaps, and product friction.
Reproduce technical issues and distinguish between documentation, usability, and product problems.
Turn developer feedback into clear product recommendations, issues, examples, and documentation improvements.
Contribute technical fixes directly when they are within scope, while partnering with Engineering on larger product changes.
Own the developer-facing execution for major product and open-source launches.
Work with Product and Engineering to understand what is shipping, who it is for, and why it matters.
Produce the demos, sample code, tutorials, documentation, and technical explanations developers need to try new capabilities.
Ensure launches show working implementations rather than only announcing features.
Evaluate whether launches result in meaningful developer understanding and adoption.
Establish LiteLLM’s initial Developer Relations priorities and operating rhythm.
Determine where technical content, integrations, community engagement, and events can have the greatest impact.
Define practical measures of success based on developer adoption, successful implementations, community participation, and product learning.
Build repeatable systems for turning product releases and developer questions into useful technical resources.
Help define how the Developer Relations function should evolve as LiteLLM grows.
Become a hands-on LiteLLM user and develop a deep understanding of the product, codebase, documentation, and community.
Build several production-quality example applications covering LiteLLM’s most important use cases.
Audit the developer journey from initial discovery through successful production deployment.
Identify the highest-impact gaps in our documentation, examples, onboarding, and technical storytelling.
Meet developers, contributors, customers, and internal teams to understand how LiteLLM is being used and where people struggle.
Establish a repeatable process for supporting developer-facing product launches.
Ship an initial set of tutorials, demos, or integrations based on the needs you uncover.
Create a system for turning recurring community questions into documentation, examples, or product feedback.
Propose a focused Developer Relations roadmap for the following six months.
Build and publish a working reference application using LiteLLM, MCP, and several model providers.
Create the technical launch materials for a major new feature.
Rewrite a confusing section of the documentation after watching developers struggle with it.
Reproduce an issue reported by a community member and submit a pull request to fix it.
Explain a new routing, security, or observability capability through a technical deep dive.
Host a workshop or livestream showing developers how to deploy LiteLLM in production.
Analyze developer activation data and identify where people are dropping out of the onboarding process.
Turn repeated questions from GitHub and community channels into documentation, examples, or product improvements.
Create tutorials, guides, demos, reference architectures, videos, and technical deep dives.
Translate complex product capabilities into clear explanations and working examples.
Build content around the problems developers are actively trying to solve, not generic thought leadership.
Develop repeatable content for important use cases such as model routing, fallbacks, cost controls, observability, guardrails, MCP, authentication, and enterprise deployment.
Keep technical content accurate as the product evolves.
Own the developer-facing story for major product and open-source releases.
Partner with engineering and product to understand what is shipping and why it matters.
Produce launch demos, sample code, documentation, changelog content, and technical announcements.
Make sure developers can try new capabilities immediately instead of only reading about them.
Measure whether launches drive meaningful adoption.
Engage directly with developers using and evaluating LiteLLM.
Answer technical questions and help users get unstuck.
Build systems that help community knowledge compound rather than leaving useful answers buried in individual threads.
Identify, support, and recognize contributors and power users.
Create opportunities for developers to share what they have built with LiteLLM.
Represent LiteLLM at relevant conferences, meetups, podcasts, workshops, and technical communities.
Build a structured feedback loop between developers and the product and engineering teams.
Identify recurring points of confusion, missing integrations, documentation gaps, and product friction.
Reproduce technical issues and distinguish documentation problems from product problems.
Turn community feedback into clear, actionable product recommendations.
Contribute code and documentation fixes directly when appropriate.
Own the path from discovering LiteLLM to running a successful production deployment.
Define and measure the developer funnel, including discovery, first successful request, deployment, continued usage, and contribution.
Experiment with technical content, examples, integrations, events, and community programs.
Focus on durable adoption and developer success rather than impressions or follower counts.
Develop a DevRel strategy that can eventually support a larger team.
Become a hands-on LiteLLM user and build several production-quality example applications.
Develop a deep understanding of the product, codebase, documentation, user community, and most common adoption paths.
Audit the complete developer journey from first discovery through production deployment.
Identify the highest-impact documentation, onboarding, and technical-content gaps.
Establish baseline metrics for developer activation and engagement.
Ship a set of high-quality tutorials and examples for LiteLLM’s most important use cases.
Create a repeatable developer-facing launch process with the product and engineering teams.
Build a system for turning recurring community questions into documentation and product improvements.
Propose the longer-term Developer Relations roadmap based on what you learn.