{"schemaVersion":"jobsearcher.job.v1","id":"c3d19021bac723d2c51c5c0e","url":"https://jobsearcher.com/jobs/c3d19021bac723d2c51c5c0e","canonicalUrl":"https://jobsearcher.com/jobs/c3d19021bac723d2c51c5c0e","title":"Founding Developer Relations","description":"LiteLLM is the open-source AI gateway used by developers and enterprises to access, manage, and govern LLMs through a unified interface.\nTeams use LiteLLM to route requests across model providers, control spend, monitor usage, implement security policies, and reliably operate AI applications in production.\nWe 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.\n\nWhy We’re Hiring\nLiteLLM has a large and growing technical community. Developers discover the project through GitHub, documentation, search, technical content, and recommendations from other engineers.\nDevelopers 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.\nYou will help us build that developer journey.\nThis 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.\n\nWhat This Job Actually Is\nThis is a hands-on technical individual-contributor role.\nYou will spend much of your time building with LiteLLM and turning what you learn into resources that help other developers succeed. You should be equally comfortable opening a code editor, explaining an infrastructure concept, and talking with developers about where they are getting stuck.\nIn a typical month, you will:\nBuild and maintain runnable demos, sample applications, integrations, and reference architectures for real LiteLLM use cases.\nCreate technical guides, videos, workshops, launch demos, and deep dives that make complex capabilities understandable and immediately usable.\nEngage directly with developers through GitHub, community channels, livestreams, meetups, conferences, and other technical forums.\nPartner with Product and Engineering on launches so new capabilities ship with strong examples, documentation, and a clear technical story.\nIdentify recurring questions and points of friction, then turn them into better documentation, examples, product feedback, issues, or code contributions where appropriate.\nExplore the wider AI developer ecosystem and build useful examples with the models, frameworks, tools, and platforms LiteLLM users care about.\nUse developer feedback and adoption data to decide which educational resources, integrations, and community initiatives will have the greatest impact.\nRepresent LiteLLM publicly through technical talks, workshops, videos, podcasts, and conversations with the developer community.\nThis is not a traditional social-media or event-marketing role, and it is not a frontline support position.\nYou will help individual developers, but the goal is to turn what you learn into resources and improvements that help the entire community. You will not be measured by content volume or impressions alone. The best outcome might be a runnable example that unlocks an important use case, an explanation that becomes the canonical resource for a difficult topic, or a pattern of feedback that leads us to improve the product.\nBecause this is a founding role, you will also help define our Developer Relations priorities, operating cadence, and measures of success. You will shape the function while continuing to ship technical work yourself.\n\nWhat You’ll Own\nTechnical Education\nCreate high-quality tutorials, demos, sample applications, reference architectures, videos, and technical deep dives.\nDevelop educational resources around the problems developers are actively trying to solve.\nExplain LiteLLM capabilities such as model routing, fallbacks, cost controls, observability, authentication, guardrails, MCP, and production deployment.\nKeep examples and technical content accurate as LiteLLM and the wider AI ecosystem evolve.\nImprove the path from reading about a capability to successfully implementing it.\nDeveloper Community\nBuild genuine relationships with developers using, evaluating, and contributing to LiteLLM.\nParticipate in GitHub discussions, community channels, technical forums, and open-source conversations.\nHelp developers get unstuck while identifying patterns that should become durable resources or product improvements.\nSupport contributors and power users and create opportunities for them to share what they have built.\nRepresent LiteLLM at relevant conferences, meetups, workshops, livestreams, podcasts, and community events.\nProduct Feedback\nBuild a structured feedback loop between the developer community and LiteLLM’s Product and Engineering teams.\nIdentify recurring points of confusion, missing integrations, documentation gaps, and product friction.\nReproduce technical issues and distinguish between documentation, usability, and product problems.\nTurn developer feedback into clear product recommendations, issues, examples, and documentation improvements.\nContribute technical fixes directly when they are within scope, while partnering with Engineering on larger product changes.\nProduct Launches\nOwn the developer-facing execution for major product and open-source launches.\nWork with Product and Engineering to understand what is shipping, who it is for, and why it matters.\nProduce the demos, sample code, tutorials, documentation, and technical explanations developers need to try new capabilities.\nEnsure launches show working implementations rather than only announcing features.\nEvaluate whether launches result in meaningful developer understanding and adoption.\nDeveloper Relations Strategy\nEstablish LiteLLM’s initial Developer Relations priorities and operating rhythm.\nDetermine where technical content, integrations, community engagement, and events can have the greatest impact.\nDefine practical measures of success based on developer adoption, successful implementations, community participation, and product learning.\nBuild repeatable systems for turning product releases and developer questions into useful technical resources.\nHelp define how the Developer Relations function should evolve as LiteLLM grows.\n\nYour First 90 Days\nDuring your first 90 days, you will:\nBecome a hands-on LiteLLM user and develop a deep understanding of the product, codebase, documentation, and community.\nBuild several production-quality example applications covering LiteLLM’s most important use cases.\nAudit the developer journey from initial discovery through successful production deployment.\nIdentify the highest-impact gaps in our documentation, examples, onboarding, and technical storytelling.\nMeet developers, contributors, customers, and internal teams to understand how LiteLLM is being used and where people struggle.\nEstablish a repeatable process for supporting developer-facing product launches.\nShip an initial set of tutorials, demos, or integrations based on the needs you uncover.\nCreate a system for turning recurring community questions into documentation, examples, or product feedback.\nPropose a focused Developer Relations roadmap for the following six months.\n\nWho You Are\nYou have experience in Developer Relations, Developer Advocacy, software engineering, solutions engineering, or another highly technical developer-facing role.\nYou can write working software and are comfortable building examples in Python.\nYou can read an unfamiliar codebase, debug integrations, reproduce issues, and communicate clearly with engineers.\nYou are an exceptional technical communicator who can make complex infrastructure concepts understandable without oversimplifying them.\nYou enjoy talking with developers and are genuinely curious about how they build and operate software.\nYou have strong product instincts and notice where APIs, workflows, examples, or documentation create unnecessary friction.\nYou can create across multiple formats, including sample applications, written tutorials, technical talks, workshops, and video.\nYou are comfortable being a visible external representative of a technical product and open-source project.\nYou operate with high ownership and do not need an existing playbook to begin shipping useful work.\nYou care about whether your work changes developer behavior, improves implementations, and produces meaningful product learning.\nYou can move quickly without compromising technical accuracy.\n\nNice to Have\nExperience with developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.\nFamiliarity with LLM application architecture and the challenges of operating AI systems in production.\nExperience with AI model providers, gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.\nMeaningful contributions to an open-source project.\nExperience building a technical audience through writing, videos, workshops, talks, or community participation.\nExperience establishing Developer Relations at an early-stage company.\nExperience working with platform engineers, infrastructure teams, or enterprise developers.\nAn existing body of technical work you can show us, such as applications, tutorials, talks, videos, documentation, or open-source contributions.\n\nWhat Success Looks Like\nWithin six months:\nDevelopers can understand LiteLLM’s major capabilities and reach a successful implementation faster.\nLiteLLM has a growing collection of credible, production-oriented examples and reference architectures.\nMajor launches consistently include strong technical education, sample code, demos, and documentation.\nRecurring community questions are systematically converted into durable resources or product improvements.\nProduct and Engineering have a clearer, evidence-based understanding of what developers need.\nMore developers are building publicly with LiteLLM, contributing to the project, and helping other community members.\nLiteLLM has a focused Developer Relations strategy with clear priorities and practical measures of impact.\nThe Developer Relations function operates as a repeatable system rather than a collection of one-off activities.\n\nWhy Join LiteLLM?\nWork on open-source infrastructure at the center of the rapidly evolving AI developer ecosystem.\nHelp developers solve real production problems involving reliability, security, cost, observability, and governance.\nWork directly with the founders and engineering team.\nEstablish LiteLLM’s Developer Relations function from the beginning.\nShape both how developers understand LiteLLM and how the product evolves.\nMove quickly and see your work used by developers around the world.\nReceive competitive compensation, equity, health, dental, and vision benefits, and a 401(k) plan with company match. the open-source AI gateway that gives developers one interface for accessing and managing LLMs, embedding models, image-generation models, MCP tools, and other AI services.\nEngineering teams use LiteLLM to route traffic across providers, control costs, enforce security policies, monitor usage, and reliably operate AI applications in production.\nWe are looking for our first Developer Relations hire to help more developers discover LiteLLM, successfully deploy it, and become active members of the community.\n\nThe Problem You’ll Solve\nLiteLLM has a large and rapidly growing technical community. Developers find us through GitHub, documentation, search, technical content, recommendations from other engineers, and their own need for better control over production AI traffic.\nDevelopers need to quickly understand what LiteLLM does, see how it fits into their stack, deploy it successfully, and learn how to use its expanding product surface. They also need a clear way to share feedback, contribute to the project, and understand what we are building next.\nYou will own that developer journey.\nYour job is to make LiteLLM easy to discover, easy to understand, and easy to adopt, while building a tight feedback loop between our developer community and the product team.\n\nWhat This Job Actually Is\nThis is a deeply technical and highly hands-on role.\nOn any given week, you might:\nBuild and publish a working reference application using LiteLLM, MCP, and several model providers.\nCreate the technical launch materials for a major new feature.\nRewrite a confusing section of the documentation after watching developers struggle with it.\nReproduce an issue reported by a community member and submit a pull request to fix it.\nExplain a new routing, security, or observability capability through a technical deep dive.\nHost a workshop or livestream showing developers how to deploy LiteLLM in production.\nAnalyze developer activation data and identify where people are dropping out of the onboarding process.\nTurn repeated questions from GitHub and community channels into documentation, examples, or product improvements.\nYou will not simply promote work produced by other teams. You will understand the product deeply enough to teach it, challenge it, and help improve it.\n\nWhat You’ll Own\nTechnical Content and Education\nCreate tutorials, guides, demos, reference architectures, videos, and technical deep dives.\nTranslate complex product capabilities into clear explanations and working examples.\nBuild content around the problems developers are actively trying to solve, not generic thought leadership.\nDevelop repeatable content for important use cases such as model routing, fallbacks, cost controls, observability, guardrails, MCP, authentication, and enterprise deployment.\nKeep technical content accurate as the product evolves.\nProduct Launches\nOwn the developer-facing story for major product and open-source releases.\nPartner with engineering and product to understand what is shipping and why it matters.\nProduce launch demos, sample code, documentation, changelog content, and technical announcements.\nMake sure developers can try new capabilities immediately instead of only reading about them.\nMeasure whether launches drive meaningful adoption.\nDeveloper Community\nEngage directly with developers using and evaluating LiteLLM.\nAnswer technical questions and help users get unstuck.\nBuild systems that help community knowledge compound rather than leaving useful answers buried in individual threads.\nIdentify, support, and recognize contributors and power users.\nCreate opportunities for developers to share what they have built with LiteLLM.\nRepresent LiteLLM at relevant conferences, meetups, podcasts, workshops, and technical communities.\nDeveloper Feedback\nBuild a structured feedback loop between developers and the product and engineering teams.\nIdentify recurring points of confusion, missing integrations, documentation gaps, and product friction.\nReproduce technical issues and distinguish documentation problems from product problems.\nTurn community feedback into clear, actionable product recommendations.\nContribute code and documentation fixes directly when appropriate.\nDeveloper Growth\nOwn the path from discovering LiteLLM to running a successful production deployment.\nDefine and measure the developer funnel, including discovery, first successful request, deployment, continued usage, and contribution.\nExperiment with technical content, examples, integrations, events, and community programs.\nFocus on durable adoption and developer success rather than impressions or follower counts.\nDevelop a DevRel strategy that can eventually support a larger team.\n\nWhat You’ll Do in the First 90 Days\nBecome a hands-on LiteLLM user and build several production-quality example applications.\nDevelop a deep understanding of the product, codebase, documentation, user community, and most common adoption paths.\nAudit the complete developer journey from first discovery through production deployment.\nIdentify the highest-impact documentation, onboarding, and technical-content gaps.\nEstablish baseline metrics for developer activation and engagement.\nShip a set of high-quality tutorials and examples for LiteLLM’s most important use cases.\nCreate a repeatable developer-facing launch process with the product and engineering teams.\nBuild a system for turning recurring community questions into documentation and product improvements.\nPropose the longer-term Developer Relations roadmap based on what you learn.\n\nWho You Are\nYou have experience in Developer Relations, Developer Advocacy, solutions engineering, software engineering, or another highly technical developer-facing role.\nYou can write working software and are comfortable building examples in Python.\nYou can read an unfamiliar codebase, debug integrations, reproduce issues, and contribute technical fixes.\nYou are an exceptional technical communicator. You can explain a complex infrastructure concept without oversimplifying it.\nYou enjoy talking to developers and are genuinely curious about how they build software.\nYou have strong product instincts and notice where workflows, APIs, or documentation create unnecessary friction.\nYou are comfortable producing across formats, including written tutorials, sample applications, presentations, workshops, and videos.\nYou operate with high ownership and do not wait for someone else to define the playbook.\nYou are analytical and care about whether your work drives adoption, activation, and successful deployments.\nYou can move quickly while maintaining a high bar for technical accuracy.\n\nBonus Points\nYou have worked on developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.\nYou understand LLM application architecture and the challenges of operating AI systems in production.\nYou have experience with model providers, AI gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.\nYou have maintained or contributed meaningfully to a successful open-source project.\nYou have built a technical audience through writing, videos, workshops, or community participation.\nYou have created developer programs or content from scratch at an early-stage company.\nYou have previously worked directly with enterprise developers or platform-engineering teams.\n\nWhat Success Looks Like\nWithin six months:\nDevelopers can understand LiteLLM’s major capabilities and get to a successful implementation faster.\nImportant launches consistently include strong documentation, sample code, demos, and developer education.\nRecurring community questions are systematically converted into durable resources or product fixes.\nLiteLLM has a measurable developer funnel and a clear understanding of where adoption succeeds or stalls.\nMore developers are building publicly with LiteLLM, contributing to the project, and helping other community members.\nProduct and engineering teams have a reliable, evidence-based view of what developers need.\nDeveloper Relations has become a repeatable company function rather than a collection of one-off activities.\n\nWhy Join LiteLLM?\nWork on open-source infrastructure at the center of the rapidly evolving AI developer ecosystem.\nHelp developers solve real production problems involving reliability, security, cost, observability, and governance.\nWork directly with the founders and engineering team.\nOwn the Developer Relations function from the beginning.\nShape both how LiteLLM is understood and what the product becomes.\nMove quickly and see your work used by developers around the world.\nReceive competitive compensation, equity, health, dental, and vision benefits.\nCompensation Range: $150K - $220K","company":"Litellm","rawCompany":"litellm","city":"Millbrae","state":"CA","isRemote":false,"isActive":false,"createdAt":"2026-08-05T14:36:10.102Z","occupations":[{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1221.00","title":"Computer and Information Research Scientists","slug":"computer-and-information-research-scientists"},{"code":"15-1254.00","title":"Web Developers","slug":"web-developers"}],"industries":[{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Founding Developer Relations","description":"LiteLLM is the open-source AI gateway used by developers and enterprises to access, manage, and govern LLMs through a unified interface.\nTeams use LiteLLM to route requests across model providers, control spend, monitor usage, implement security policies, and reliably operate AI applications in production.\nWe 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.\n\nWhy We’re Hiring\nLiteLLM has a large and growing technical community. Developers discover the project through GitHub, documentation, search, technical content, and recommendations from other engineers.\nDevelopers 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.\nYou will help us build that developer journey.\nThis 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.\n\nWhat This Job Actually Is\nThis is a hands-on technical individual-contributor role.\nYou will spend much of your time building with LiteLLM and turning what you learn into resources that help other developers succeed. You should be equally comfortable opening a code editor, explaining an infrastructure concept, and talking with developers about where they are getting stuck.\nIn a typical month, you will:\nBuild and maintain runnable demos, sample applications, integrations, and reference architectures for real LiteLLM use cases.\nCreate technical guides, videos, workshops, launch demos, and deep dives that make complex capabilities understandable and immediately usable.\nEngage directly with developers through GitHub, community channels, livestreams, meetups, conferences, and other technical forums.\nPartner with Product and Engineering on launches so new capabilities ship with strong examples, documentation, and a clear technical story.\nIdentify recurring questions and points of friction, then turn them into better documentation, examples, product feedback, issues, or code contributions where appropriate.\nExplore the wider AI developer ecosystem and build useful examples with the models, frameworks, tools, and platforms LiteLLM users care about.\nUse developer feedback and adoption data to decide which educational resources, integrations, and community initiatives will have the greatest impact.\nRepresent LiteLLM publicly through technical talks, workshops, videos, podcasts, and conversations with the developer community.\nThis is not a traditional social-media or event-marketing role, and it is not a frontline support position.\nYou will help individual developers, but the goal is to turn what you learn into resources and improvements that help the entire community. You will not be measured by content volume or impressions alone. The best outcome might be a runnable example that unlocks an important use case, an explanation that becomes the canonical resource for a difficult topic, or a pattern of feedback that leads us to improve the product.\nBecause this is a founding role, you will also help define our Developer Relations priorities, operating cadence, and measures of success. You will shape the function while continuing to ship technical work yourself.\n\nWhat You’ll Own\nTechnical Education\nCreate high-quality tutorials, demos, sample applications, reference architectures, videos, and technical deep dives.\nDevelop educational resources around the problems developers are actively trying to solve.\nExplain LiteLLM capabilities such as model routing, fallbacks, cost controls, observability, authentication, guardrails, MCP, and production deployment.\nKeep examples and technical content accurate as LiteLLM and the wider AI ecosystem evolve.\nImprove the path from reading about a capability to successfully implementing it.\nDeveloper Community\nBuild genuine relationships with developers using, evaluating, and contributing to LiteLLM.\nParticipate in GitHub discussions, community channels, technical forums, and open-source conversations.\nHelp developers get unstuck while identifying patterns that should become durable resources or product improvements.\nSupport contributors and power users and create opportunities for them to share what they have built.\nRepresent LiteLLM at relevant conferences, meetups, workshops, livestreams, podcasts, and community events.\nProduct Feedback\nBuild a structured feedback loop between the developer community and LiteLLM’s Product and Engineering teams.\nIdentify recurring points of confusion, missing integrations, documentation gaps, and product friction.\nReproduce technical issues and distinguish between documentation, usability, and product problems.\nTurn developer feedback into clear product recommendations, issues, examples, and documentation improvements.\nContribute technical fixes directly when they are within scope, while partnering with Engineering on larger product changes.\nProduct Launches\nOwn the developer-facing execution for major product and open-source launches.\nWork with Product and Engineering to understand what is shipping, who it is for, and why it matters.\nProduce the demos, sample code, tutorials, documentation, and technical explanations developers need to try new capabilities.\nEnsure launches show working implementations rather than only announcing features.\nEvaluate whether launches result in meaningful developer understanding and adoption.\nDeveloper Relations Strategy\nEstablish LiteLLM’s initial Developer Relations priorities and operating rhythm.\nDetermine where technical content, integrations, community engagement, and events can have the greatest impact.\nDefine practical measures of success based on developer adoption, successful implementations, community participation, and product learning.\nBuild repeatable systems for turning product releases and developer questions into useful technical resources.\nHelp define how the Developer Relations function should evolve as LiteLLM grows.\n\nYour First 90 Days\nDuring your first 90 days, you will:\nBecome a hands-on LiteLLM user and develop a deep understanding of the product, codebase, documentation, and community.\nBuild several production-quality example applications covering LiteLLM’s most important use cases.\nAudit the developer journey from initial discovery through successful production deployment.\nIdentify the highest-impact gaps in our documentation, examples, onboarding, and technical storytelling.\nMeet developers, contributors, customers, and internal teams to understand how LiteLLM is being used and where people struggle.\nEstablish a repeatable process for supporting developer-facing product launches.\nShip an initial set of tutorials, demos, or integrations based on the needs you uncover.\nCreate a system for turning recurring community questions into documentation, examples, or product feedback.\nPropose a focused Developer Relations roadmap for the following six months.\n\nWho You Are\nYou have experience in Developer Relations, Developer Advocacy, software engineering, solutions engineering, or another highly technical developer-facing role.\nYou can write working software and are comfortable building examples in Python.\nYou can read an unfamiliar codebase, debug integrations, reproduce issues, and communicate clearly with engineers.\nYou are an exceptional technical communicator who can make complex infrastructure concepts understandable without oversimplifying them.\nYou enjoy talking with developers and are genuinely curious about how they build and operate software.\nYou have strong product instincts and notice where APIs, workflows, examples, or documentation create unnecessary friction.\nYou can create across multiple formats, including sample applications, written tutorials, technical talks, workshops, and video.\nYou are comfortable being a visible external representative of a technical product and open-source project.\nYou operate with high ownership and do not need an existing playbook to begin shipping useful work.\nYou care about whether your work changes developer behavior, improves implementations, and produces meaningful product learning.\nYou can move quickly without compromising technical accuracy.\n\nNice to Have\nExperience with developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.\nFamiliarity with LLM application architecture and the challenges of operating AI systems in production.\nExperience with AI model providers, gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.\nMeaningful contributions to an open-source project.\nExperience building a technical audience through writing, videos, workshops, talks, or community participation.\nExperience establishing Developer Relations at an early-stage company.\nExperience working with platform engineers, infrastructure teams, or enterprise developers.\nAn existing body of technical work you can show us, such as applications, tutorials, talks, videos, documentation, or open-source contributions.\n\nWhat Success Looks Like\nWithin six months:\nDevelopers can understand LiteLLM’s major capabilities and reach a successful implementation faster.\nLiteLLM has a growing collection of credible, production-oriented examples and reference architectures.\nMajor launches consistently include strong technical education, sample code, demos, and documentation.\nRecurring community questions are systematically converted into durable resources or product improvements.\nProduct and Engineering have a clearer, evidence-based understanding of what developers need.\nMore developers are building publicly with LiteLLM, contributing to the project, and helping other community members.\nLiteLLM has a focused Developer Relations strategy with clear priorities and practical measures of impact.\nThe Developer Relations function operates as a repeatable system rather than a collection of one-off activities.\n\nWhy Join LiteLLM?\nWork on open-source infrastructure at the center of the rapidly evolving AI developer ecosystem.\nHelp developers solve real production problems involving reliability, security, cost, observability, and governance.\nWork directly with the founders and engineering team.\nEstablish LiteLLM’s Developer Relations function from the beginning.\nShape both how developers understand LiteLLM and how the product evolves.\nMove quickly and see your work used by developers around the world.\nReceive competitive compensation, equity, health, dental, and vision benefits, and a 401(k) plan with company match. the open-source AI gateway that gives developers one interface for accessing and managing LLMs, embedding models, image-generation models, MCP tools, and other AI services.\nEngineering teams use LiteLLM to route traffic across providers, control costs, enforce security policies, monitor usage, and reliably operate AI applications in production.\nWe are looking for our first Developer Relations hire to help more developers discover LiteLLM, successfully deploy it, and become active members of the community.\n\nThe Problem You’ll Solve\nLiteLLM has a large and rapidly growing technical community. Developers find us through GitHub, documentation, search, technical content, recommendations from other engineers, and their own need for better control over production AI traffic.\nDevelopers need to quickly understand what LiteLLM does, see how it fits into their stack, deploy it successfully, and learn how to use its expanding product surface. They also need a clear way to share feedback, contribute to the project, and understand what we are building next.\nYou will own that developer journey.\nYour job is to make LiteLLM easy to discover, easy to understand, and easy to adopt, while building a tight feedback loop between our developer community and the product team.\n\nWhat This Job Actually Is\nThis is a deeply technical and highly hands-on role.\nOn any given week, you might:\nBuild and publish a working reference application using LiteLLM, MCP, and several model providers.\nCreate the technical launch materials for a major new feature.\nRewrite a confusing section of the documentation after watching developers struggle with it.\nReproduce an issue reported by a community member and submit a pull request to fix it.\nExplain a new routing, security, or observability capability through a technical deep dive.\nHost a workshop or livestream showing developers how to deploy LiteLLM in production.\nAnalyze developer activation data and identify where people are dropping out of the onboarding process.\nTurn repeated questions from GitHub and community channels into documentation, examples, or product improvements.\nYou will not simply promote work produced by other teams. You will understand the product deeply enough to teach it, challenge it, and help improve it.\n\nWhat You’ll Own\nTechnical Content and Education\nCreate tutorials, guides, demos, reference architectures, videos, and technical deep dives.\nTranslate complex product capabilities into clear explanations and working examples.\nBuild content around the problems developers are actively trying to solve, not generic thought leadership.\nDevelop repeatable content for important use cases such as model routing, fallbacks, cost controls, observability, guardrails, MCP, authentication, and enterprise deployment.\nKeep technical content accurate as the product evolves.\nProduct Launches\nOwn the developer-facing story for major product and open-source releases.\nPartner with engineering and product to understand what is shipping and why it matters.\nProduce launch demos, sample code, documentation, changelog content, and technical announcements.\nMake sure developers can try new capabilities immediately instead of only reading about them.\nMeasure whether launches drive meaningful adoption.\nDeveloper Community\nEngage directly with developers using and evaluating LiteLLM.\nAnswer technical questions and help users get unstuck.\nBuild systems that help community knowledge compound rather than leaving useful answers buried in individual threads.\nIdentify, support, and recognize contributors and power users.\nCreate opportunities for developers to share what they have built with LiteLLM.\nRepresent LiteLLM at relevant conferences, meetups, podcasts, workshops, and technical communities.\nDeveloper Feedback\nBuild a structured feedback loop between developers and the product and engineering teams.\nIdentify recurring points of confusion, missing integrations, documentation gaps, and product friction.\nReproduce technical issues and distinguish documentation problems from product problems.\nTurn community feedback into clear, actionable product recommendations.\nContribute code and documentation fixes directly when appropriate.\nDeveloper Growth\nOwn the path from discovering LiteLLM to running a successful production deployment.\nDefine and measure the developer funnel, including discovery, first successful request, deployment, continued usage, and contribution.\nExperiment with technical content, examples, integrations, events, and community programs.\nFocus on durable adoption and developer success rather than impressions or follower counts.\nDevelop a DevRel strategy that can eventually support a larger team.\n\nWhat You’ll Do in the First 90 Days\nBecome a hands-on LiteLLM user and build several production-quality example applications.\nDevelop a deep understanding of the product, codebase, documentation, user community, and most common adoption paths.\nAudit the complete developer journey from first discovery through production deployment.\nIdentify the highest-impact documentation, onboarding, and technical-content gaps.\nEstablish baseline metrics for developer activation and engagement.\nShip a set of high-quality tutorials and examples for LiteLLM’s most important use cases.\nCreate a repeatable developer-facing launch process with the product and engineering teams.\nBuild a system for turning recurring community questions into documentation and product improvements.\nPropose the longer-term Developer Relations roadmap based on what you learn.\n\nWho You Are\nYou have experience in Developer Relations, Developer Advocacy, solutions engineering, software engineering, or another highly technical developer-facing role.\nYou can write working software and are comfortable building examples in Python.\nYou can read an unfamiliar codebase, debug integrations, reproduce issues, and contribute technical fixes.\nYou are an exceptional technical communicator. You can explain a complex infrastructure concept without oversimplifying it.\nYou enjoy talking to developers and are genuinely curious about how they build software.\nYou have strong product instincts and notice where workflows, APIs, or documentation create unnecessary friction.\nYou are comfortable producing across formats, including written tutorials, sample applications, presentations, workshops, and videos.\nYou operate with high ownership and do not wait for someone else to define the playbook.\nYou are analytical and care about whether your work drives adoption, activation, and successful deployments.\nYou can move quickly while maintaining a high bar for technical accuracy.\n\nBonus Points\nYou have worked on developer infrastructure, APIs, observability, security, cloud platforms, or open-source software.\nYou understand LLM application architecture and the challenges of operating AI systems in production.\nYou have experience with model providers, AI gateways, agent frameworks, MCP, Kubernetes, or enterprise AI platforms.\nYou have maintained or contributed meaningfully to a successful open-source project.\nYou have built a technical audience through writing, videos, workshops, or community participation.\nYou have created developer programs or content from scratch at an early-stage company.\nYou have previously worked directly with enterprise developers or platform-engineering teams.\n\nWhat Success Looks Like\nWithin six months:\nDevelopers can understand LiteLLM’s major capabilities and get to a successful implementation faster.\nImportant launches consistently include strong documentation, sample code, demos, and developer education.\nRecurring community questions are systematically converted into durable resources or product fixes.\nLiteLLM has a measurable developer funnel and a clear understanding of where adoption succeeds or stalls.\nMore developers are building publicly with LiteLLM, contributing to the project, and helping other community members.\nProduct and engineering teams have a reliable, evidence-based view of what developers need.\nDeveloper Relations has become a repeatable company function rather than a collection of one-off activities.\n\nWhy Join LiteLLM?\nWork on open-source infrastructure at the center of the rapidly evolving AI developer ecosystem.\nHelp developers solve real production problems involving reliability, security, cost, observability, and governance.\nWork directly with the founders and engineering team.\nOwn the Developer Relations function from the beginning.\nShape both how LiteLLM is understood and what the product becomes.\nMove quickly and see your work used by developers around the world.\nReceive competitive compensation, equity, health, dental, and vision benefits.\nCompensation Range: $150K - $220K","datePosted":"2026-08-05T14:36:10.102Z","dateModified":"2026-08-05T14:36:10.102Z","hiringOrganization":{"@type":"Organization","name":"Litellm","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Millbrae","addressRegion":"CA","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"c3d19021bac723d2c51c5c0e"},"url":"https://jobsearcher.com/jobs/c3d19021bac723d2c51c5c0e"}}