Your 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.
XML job scraping automation by YubHub
