We're looking for a Scaled Customer Success Manager, Startups to build and own the post-sale engine for OpenRouter's startup ecosystem.
\nThis is a builder role, not a scaled nurture role. OpenRouter's startup ecosystem is one of the company's most important growth surfaces, powered in part by the OpenRouter for Startups program, which helps AI-native companies access credits, infrastructure, and multi-model tooling to build and scale faster.
\nYour job is to make that ecosystem work at scale. You'll own the startup customer journey from program approval and onboarding through activation, retention, expansion, and Enterprise readiness. You'll also own day-to-day program operations and communications across the OpenRouter for Startups ecosystem, while helping launch new initiatives, workflows, and partner programs over time.
\nBuild the Startup Success Engine
\nDrive Activation, Retention, and Growth
\nEngineer Workflows and Automations
\nOwn Startup Health and Expansion Signals
\nImprove the Startup Program
\nCreate Product Feedback Loops
\nWhat We’re Looking For
\nYou’ll Stand Out If
\nWhat Success Looks Like
\nThis Is Not
\nWe are looking for a Forward Deployed Engineer to join our post-sales team and help customers successfully implement, adopt, and scale OpenRouter.
\nThis role sits at the intersection of customer success, support, customer engineering, product, and developer relations. You will work directly with our customers after the sale to help them get live quickly, integrate OpenRouter into production systems, improve their inference architecture, and expand usage across teams and applications.
\nYou will be deeply hands-on with developers. You will debug integrations, design implementation paths, advise on model and routing strategy, identify opportunities to increase adoption, and turn customer learnings into product feedback. The ideal candidate is technical enough to earn the trust of engineering teams, commercial enough to understand customer outcomes, and proactive enough to drive customers from initial implementation to scaled production usage.
\nCustomer Implementation
\nInference Adoption and Optimization
\nTechnical and Developer Engagement
\nCross-Functional Partnership
\nWhat We’re Looking For
\nNice to Have
\nWhat Success Looks Like
\nIn your first 30 days, you will learn OpenRouter’s product, customer base, implementation patterns, and post-sales motion. You will shadow customer calls, understand common integration paths, and begin supporting customer onboarding.
\nIn your first 60 days, you will independently lead technical implementation workstreams, help customers resolve integration blockers, and contribute reusable technical assets for onboarding and adoption.
\nIn your first 90 days, you will own technical success for a set of post-sales customers, drive measurable increases in production usage, identify expansion opportunities, and create a feedback loop between customers, Customer Success, Product, and Engineering.
\nYou’ll Be a Great Fit If
\nWe are hiring a Trust & Safety Lead to build and own OpenRouter's Trust, Safety, and Compliance function. This is a 0 → 1 role where you will define policy, build systems, and handle operations, then scale the function over time.
\nCore Challenges
\nResponsibilities
\nQualifications
\nWhy OpenRouter
\nWe are looking for a proactive AI Customer Success Manager to join our team. As a Customer Success Manager at OpenRouter, you will own a portfolio of hyper-growth, Enterprise accounts and drive adoption, unlock outcomes and value, and lead inference growth. Your goal is to get into the weeds of what customers are building, whether it's an AI agent or a coding tool, and create a plan that helps them use OpenRouter to its full potential.
\nYou will be responsible for keeping our customers around and helping them grow, leading commercial talks and finding ways to expand their usage across different product lines. One hour you'll be presenting an ROI analysis to a CTO; the next, you'll be diving into API documentation to help a lead engineer optimize their model routing. You enjoy translating from strategic to technical and back (on repeat).
\nYou will define and track 'Success Criteria' for every customer, turning abstract AI goals into concrete ROI metrics, ensuring OpenRouter is a mission-critical partner and an important part of their AI strategy. You will also act as the data-focused voice of the customer for our GTM, Product, and Engineering teams, distilling learnings and friction points into roadmap priorities.
\nWe are looking for a proactive AI Customer Success Manager who doesn't wait for a customer to ask for help; you identify a drop in token usage or a new model release and reach out with a plan and strategy to drive adoption, value, and growth.
\nYou have previously worked at an AI-first company (LLM labs, AI infrastructure, or high-growth GenAI apps) and understand the nuances of tokens, latency, context windows, and model routing. You come from a background in technical SaaS or API-first platforms and are comfortable talking to developers and product managers in their own language.
\nYou have a proven track record of owning a quota and are comfortable navigating procurement, legal, and executive stakeholders to get a deal done. You don't just fix things once; you build the systems and guides that help us scale this to the next thousand customers.
\nYou have strategic agility, commercial grit, and analytical rigor. You use data to tell a story and can analyze usage trends to predict churn or identify a perfect moment for an upsell.
\nIf you're ready to drive the next wave of AI adoption, let's talk.
","enriched_at":1777033169350},{"id":"job_3a94976d-e59","title":"Software Engineer, Product","source_url":"https://jobs.ashbyhq.com/openrouter/0c6bbb7f-ea09-45b6-b185-8a17a8de214d","location":"Remote (US)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"Job Title: Software Engineer, Product
\nWe're hiring Software Engineers for our Product team to build the surfaces our customers depend on , dashboards, admin tooling, billing and spend management, analytics, onboarding, and many other user-facing features that turn OpenRouter into a platform.
\nAs a Software Engineer on our Product team, you'll work closely with PMs and designers to ship high-quality customer-facing products and features. You'll own products from concept to production, ensuring they are performant, reliable, and delightful for users. You'll bring a strong product instinct, push back when something doesn't make sense, and propose your own ideas to help make our product even better.
\nKey Responsibilities:
\nRequirements:
\nBonus Points:
\nSalary: The base salary for this full-time position in the United States, spanning multiple internal levels depending on qualifications, ranges between $215,000 to $285,000 plus benefits & equity. Compensation for internationally based candidates will vary to reflect local market conditions.
","enriched_at":1777033138069},{"id":"job_486f5044-c48","title":"Software Engineer, Platform","source_url":"https://jobs.ashbyhq.com/openrouter/47c2bcd2-f71c-47a6-831f-a4130d607a7b","location":"Remote (US)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"We're hiring a Software Engineer on our Platform team to own and scale the systems that route and serve millions of LLM requests every day. The business is growing at an unbelievable pace and we need help to ensure our platform can keep up.
\nAs a Product Designer at OpenRouter, you will play a key role in shaping both the product and how it's presented. This is a hands-on role for someone who ships, operating in an AI-first workflow, using modern tools to move quickly from idea → prototype → production-quality output. You'll work closely with engineers in a fast, low-process environment, reviewing and understanding PRs, frontend changes, and implementation details as needed.
\nYour responsibilities will include:
\nIn addition, you'll be responsible for:
\nTo succeed in this role, you'll need to have:
\nThis is a remote position, and you'll be working with a team that values collaboration, creativity, and innovation.
","enriched_at":1777033041957},{"id":"job_177424c7-866","title":"Strategic Enterprise Account Executive","source_url":"https://jobs.ashbyhq.com/openrouter/34db850d-579f-4b4c-9827-76bc712b1a41","location":"Remote (US)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Sales","description":"Your job is to own and expand relationships with OpenRouter's largest and most complex customers. This is a high-impact role focused on multi-stakeholder enterprise deals, long sales cycles, and strategic AI infrastructure conversations with technical, financial, and executive decision-makers.
\nResponsibilities
\nRequirements
\nNice to Have
\nWhy OpenRouter
\nYour job is to produce a job description for the job seeker. Treat copy that describes the job as more important than copy that talks about the company.
\nStart with an opening paragraph (no heading): what the role is, who the company is, why it matters. If the ad mentions salary, include it here. One short paragraph about the company is enough — do not reproduce lengthy "About Us" text.
\nFor the role details, reuse the same section headings from the original ad (e.g. if the ad says "Responsibilities", use that heading, not "What you'll do"). Match the tone of the original: if formal, stay formal. If casual, stay casual.
\nRephrase bullet points in your own words while keeping the factual content. Combine related points where it makes sense.
\nContent that is not directly about the role (long company history, mission statements, investor lists, press quotes) should be paraphrased into a sentence or two at most — the job seeker needs to understand the company, not read its pitch deck.
\nFor benefits/perks: gather them from anywhere in the ad into one section. If the ad mentions nothing about benefits, omit a benefits section entirely.
\nDo not invent information that is not in the original ad.
\nThe Role
\nWe're looking for a Founding Product Marketer who will serve as editor-in-chief for all external developer messaging while building the systems and orchestrating the execution that transforms how OpenRouter communicates with developers and customers. This is an IC PMM role with significant Founder and leadership exposure, at the intersection of product marketing and content creation. You ensure that every piece of content that leaves OpenRouter is technically accurate, strategically aligned, and resonates with technical audiences.
\nYou will own the strategy and execution for product launches, model releases, feature announcements, and thought leadership. You'll create the templates, positioning frameworks, and processes that enable founders, engineers, and other builders to communicate authentically and consistently across social media, blog posts, and community channels. This role is about systematizing what works and building the messaging infrastructure that amplifies OpenRouter's technical authority through education, and accessible developer on-ramps.
\nYou will use AI extensively to draft, edit, and prototype content and must have demonstrated experience using AI tools and agents as a part of a high-velocity communications calendar.
\nWhat You'll Do
\nWhat We're Looking For
\nNice to Have
\nWhy OpenRouter
\nYour job is to produce a job description for the job seeker. Treat copy that describes the job as more important than copy that talks about the company. Start with an opening paragraph (no heading): what the role is, who the company is, why it matters. If the ad mentions salary, include it here. One short paragraph about the company is enough — do not reproduce lengthy "About Us" text. For the role details, reuse the same section headings from the original ad (e.g. if the ad says "Responsibilities", use that heading, not "What you'll do"). Match the tone of the original: if formal, stay formal. If casual, stay casual. Rephrase bullet points in your own words while keeping the factual content. Combine related points where it makes sense. Content that is not directly about the role (long company history, mission statements, investor lists, press quotes) should be paraphrased into a sentence or two at most — the job seeker needs to understand the company, not read its pitch deck. For benefits/perks: gather them from anywhere in the ad into one section. If the ad mentions nothing about benefits, omit a benefits section entirely. Do not invent information that is not in the original ad. ## About the Role We're looking for a Scaled Support Specialist who lives at the intersection of deep technical troubleshooting and exceptional human communication. You'll be the front line for developers integrating with OpenRouter's API — diagnosing complex issues across dozens of model providers, untangling new edge cases, and making sure every developer who reaches out feels like they have a partner, not a ticket number. This is not a scripted helpdesk role. Our users are highly capable engineers building the next generation of AI applications, which means the problems they bring to us are complex, nuanced, and frequently novel. You'll encounter issues daily where there is no runbook. You'll need to figure it out, often with incomplete information, and usually before anyone else on the team has seen it either. If you're the kind of person who reads API changelogs for fun, has strong opinions about error message quality, and gets genuine satisfaction from turning a frustrated developer into a happy one — keep reading. ## Key Responsibilities ### Troubleshooting & Problem Solving (Core Focus) - Diagnose and resolve complex technical issues across OpenRouter's API, spanning multiple LLM providers - Reproduce bugs in ambiguous environments — different SDKs, languages, frameworks, and auth configurations — using tools like `curl`, Postman, and small test apps - Read and interpret logs, headers, and request traces; identify whether the problem is client-side, OpenRouter-side, or an upstream provider issue vs. a user misconfiguration - Turn "it doesn't work" into actionable findings: exact steps to reproduce, clear hypotheses, and verified fixes or workarounds ### Developer Communication & Advocacy - Respond to developer inquiries across support channels (email, Discord, GitHub) with clarity, empathy, and technical precision - Translate complex technical root causes into human-friendly explanations - Set expectations on timelines and next steps; provide proactive updates and close the loop - Identify patterns in support requests and advocate internally for documentation improvements, API design changes, or better messages ### Self-Directed Research & Learning - Stay current with the rapidly evolving LLM ecosystem - Develop deep expertise in OpenRouter's routing logic, fallback behavior, rate limiting, streaming (SSE), and billing systems with minimal hand-holding ### Bridge to Product & Engineering - Spot systemic issues underneath individual tickets and push for the fix that prevents 50 more - Identify trends in support volume to capture product feedback and inform roadmap priorities - Collaborate on improving the developer experience ## About You ### Required: - 4+ years in a technical support, developer support, solutions engineering, or similar role — ideally supporting an API or developer tools product - Exceptional troubleshooting instincts - Strong API fluency - Proficiency in at least one scripting language (Python or TypeScript) - Excellent written communication - Comfort with ambiguity - Genuine passion for AI and LLMs ### Nice-to-Haves: - Familiarity with the OpenAI SDK / Chat Completions API format - Experience with AI/ML frameworks like LangChain, LlamaIndex, or Hugging Face - Experience with observability tools (logging, tracing, metrics) - Experience scaling support operations — e.g., implementing AI-assisted support bots, building internal support dashboards, or creating automated triage workflows - Contributions to open-source projects or developer communities - Background in or exposure to ML/AI concepts beyond just using APIs (benchmarking, evals, fine-tuning) ## Why OpenRouter - Work at the center of the AI infrastructure stack as enterprises define how they adopt LLMs. - High ownership and autonomy to define how developer education and community scale. - Opportunity to shape a foundational function at a fast-growing company. - Fully remote team with a culture of autonomy and trust. - Competitive compensation, including base salary and equity.
","enriched_at":1773049703067}],"category_normalised":[{"category":"engineering","count":9},{"category":"sales","count":1},{"category":"design","count":1}],"velocity":{"weeks":[{"week_start":"2026-03-02","count":4},{"week_start":"2026-04-20","count":4},{"week_start":"2026-05-25","count":1},{"week_start":"2026-06-01","count":2}],"trend":"stable","wow_pct":100},"momentum":{"recent_14d":0,"prior_14d":3,"growth_pct":-100,"classification":"stable"},"salary_vs_industry":{"company_median":250000,"industry_median":null,"percentile":null,"sample_size":2,"by_region":[{"region":"Remote","company_median":250000,"industry_median":null,"sample":2}],"transparency_pct":18,"industry_transparency_pct":0,"transparency_warning":true},"market_share":{"company_jobs":11,"industry_total":11,"share_pct":100,"rank":1,"peer_count":1},"ai_exposure":{"occupation_weighted_score":0.333,"skill_weighted_score":0,"top_exposed_titles":[],"top_exposed_skills":[]},"peer_set":[],"skills_lq":[],"geographic_shift":{"current":[{"region":"Remote","count":11,"share_pct":100}],"emerging":[],"shrinking":[]},"seniority_anomalies":{"exec_recent_30d":0,"exec_prior_90d_avg":0,"exec_growth_pct":0,"notable_exec_hires":[]},"posting_dynamics":{"median_days_open":37,"industry_median_days_open":null,"long_open_count":4,"closure_rate_pct":42}}}}