Verified Tech Jobs & Hiring Companies, Updated Every 24 Hours

About OpenRouter OpenRouter is the leading AI routing and infrastructure layer that enterprises use to access, manage, and optimize the best large language models across providers—without lock-in, capacity constraints, or unnecessary cost. We power the most advanced AI teams in the world by giving them the flexibility to move fast, scale confidently, and stay future-proof as models evolve. As enterprise adoption of AI accelerates, OpenRouter sits at the center of how organizations operationalize LLMs across research, product, and production workloads. About the Role We're hiring a Software Engineer on our Ori, to build out our family of products for putting any model to work in your terminal, in Slack, and on your desktop. Ori is built to answer the question from large buyer ICP, we are building the client side products for massive enterprise adoption of OpenRouter beyond the engineering organization. Ori is small team built the current product in a few months. You'll work with that team, which is led by one of our co-founders, alongside product, design and the platform teams Ori is built on. This is a hands-on IC role with broad surface area and little process between you and shipping. What You'll Do Build and ship across every Ori surface: the ori CLI and its harness integrations. Make model fungibility real in any harness. That means model switching, provider fallbacks, tool and prompt settings tuned to each model, and respecting org guardrails, all without extra auth for the user. Build the agent runtime underneath. That includes sandboxed agents that never see their own credentials, secrets management, session management and compaction, and skills that agents can learn, share and inherit across models. Take agents from a laptop to the cloud: deploy, fork and shut down agents on command, with agent state that is version-controlled and auditable. Own quality end to end, from install, auth and CLI UX to reliability, observability and evals. Ori is heavily dogfooded internally, so you'll use what you build every day. Feed the gaps Ori exposes back into OpenRouter's API and SDKs, so the whole ecosystem can build multi-model agents on the same primitives. What We're Looking For 5+ years shipping production software, with real ownership of developer tools, CLIs, agent products or the infrastructure behind them. Daily fluency with coding agents like Claude Code, Codex, OpenCode, Pi or Hermes, and specific opinions about what makes an agent loop, a harness or a tool integration good. A solid grasp of how agents work under the hood: tool calling, context management, prompt caching, evals, and the cost, latency and quality tradeoffs between models. Good systems judgment for running agents safely: sandboxing, process isolation, secrets, and reliability across many users. High agency and a bias toward action. You talk to users, prototype, ship and iterate on a small team with fluid boundaries. Product taste for developer tools. You notice interaction details and care how the first five minutes feel. Nice to Have Built or maintained an open-source agent harness, CLI or developer tool. Experience with multi-agent systems, agent skills or memory, or eval and benchmarking tools.Shipped a Slack app or a native macOS app.Existing user of OpenRouter or Ori, or active side projects in AI tooling. If you don't think you meet all of the criteria above but are still interested in the job, please apply. Nobody checks every box, and we're looking for someone excited to join the team.

About OpenRouter OpenRouter is the leading AI routing and infrastructure layer that enterprises use to access, manage, and optimize the best large language models across providers—without lock-in, capacity constraints, or unnecessary cost. We power the most advanced AI teams in the world by giving them the flexibility to move fast, scale confidently, and stay future-proof as models evolve. As enterprise adoption of AI accelerates, OpenRouter sits at the center of how organizations operationalize LLMs across research, product, and production workloads. About the Role The Provider Ecosystem team owns the supply side of OpenRouter: every model, endpoint, and provider the router can send a request to. That means hundreds of providers, thousands of endpoints, and millions of requests a day, in a model landscape that changes every week. You’ll be at the front of the industry. Labs and inference providers want to reach OpenRouter’s users, so this team gets early access to novel inference offerings, often through exclusive and stealth launches, and gets them live on day zero. This is a hands-on leadership role reporting to the VPE. You’ll grow the team, stay deep in the code, and be OpenRouter’s technical face to the labs and providers we partner with. What You'll Do Lead the team: hire and grow strong engineers, set the roadmap, stay hands-on in code reviews and incidents, and advocate for the team with leadership. Core Provider: own provider adapters, the endpoint lifecycle, and routing. Be the technical counterpart for top providers, run day-zero and stealth launches, and work with GTM, BD, and legal to get providers from signed NDA to live in weeks, not months. Multi-Modal: lead the expansion beyond text into image, video, audio, and embeddings, plus realtime and batch inference. Benchmarks: own evals and inference quality, and turn that data into routing decisions and direct feedback that makes providers better. What We're Looking For 4+ years of engineering management experience, including at least one environment where you built or scaled a team during a period of rapid growth. Strong technical foundation in distributed systems, API design, and LLM inference. You understand how inference is served (streaming, tool calling, prompt caching, quantization, throughput and latency trade-offs), how provider APIs differ from each other, and what it takes to route millions of requests across hundreds of heterogeneous endpoints. Hands-on and comfortable staying that way. You write code, use AI-assisted development tools, and lead by example in a team where everyone ships. Comfortable being externally facing. You can sit across from a model lab’s engineering team, negotiate an integration, and represent OpenRouter’s technical requirements without a PM in the room. Data-driven about quality. You want benchmarks, evals, and production telemetry deciding which provider gets traffic, not vibes. Proven ability to recruit and retain strong engineers. Ideally, you’ve built teams people want to join and you bring a network of talent with you. High agency and clear communication. You don’t wait for direction, you identify what matters, make a plan, and drive it forward. You speak up when you disagree and back it with substance. Pragmatic about what a lean engineering org actually needs versus what a 500-person org would do. You optimize for speed and clarity, not process. Nice to Haves Experience at an inference provider, model lab, or GPU cloud, or building products on top of many LLM APIs at once. Experience with our stack: TypeScript, Cloudflare Workers, Postgres, ClickHouse, GCP, or Vercel. Background in evals, benchmarking, or routing and load-balancing systems. Experience shipping multimodal APIs (image, video, speech, embeddings) or realtime and batch inference. Experience running vendor security and compliance reviews (NDA, DPA, SOC 2) as part of a partner onboarding process. Existing user of OpenRouter, or active side projects in AI infrastructure or developer tooling. If you don't think you meet all of the criteria below but still are interested in the job, please apply. Nobody checks every box, and we're looking for someone who is excited to join the team.

About OpenRouter OpenRouter is the leading AI routing and infrastructure layer that enterprises use to access, manage, and optimize the best large language models across providers—without lock-in, capacity constraints, or unnecessary cost. We power the most advanced AI teams in the world by giving them the flexibility to move fast, scale confidently, and stay future-proof as models evolve. As enterprise adoption of AI accelerates, OpenRouter sits at the center of how organizations operationalize LLMs across research, product, and production workloads. About the Role We’re hiring a Software Engineer on our Trust & Safety team to own the detection, enforcement, and review systems that keep abuse, fraud, malicious users and illegal content off the platform. Millions of LLM requests and a large volume of payments flow through OpenRouter every day, and maintaining the safety, integrity, and trust of our platform is a priority. You’ll build the systems that detect abuse and fraud, the heuristics for automated action and abuse mitigation, the tooling our reviewers act through, and the guardrails that keep us from acting on the wrong account. You will be responsible for proactive abuse-prevention architecture for a new layer of the AI stack while the abuse patterns are still being invented. The threat model changes quickly, and the systems you build have to catch novel abuse without adding friction for the legitimate developers and enterprises who use our platform. Done well, this work protects millions of daily requests, our provider relationships, and the trust that enterprises place in OpenRouter. This is a hands-on IC role with broad surface area spanning the inference path, the payments path, internal review tooling, and the data platform underneath all of it. There is little process between you and shipping, and your work has direct consequences for real users, so the bar for judgment is high. What You’ll Do Build and operate technical systems across signup, payments, and usage to detect abuse and fraud early. Own the technical enforcement pipeline end to end, from detection proposing a candidate to a human reviewing it to restrictions landing across our systems. Build the internal tools that support investigation and enforcement decision-making. This involves building case queues, evidence summaries, bulk review and enactment, and alerting mechanisms to trigger investigations. Ship technical solutions for content safety on the inference path: illegal content detection and reporting, the KYC systems or external intelligence sources to allow us to more efficiently and proactively detect and stop fraud and abuse. Help make abuse uneconomical by building systems, tools, and heuristics for quick detection and scalable enforcement. Help investigate incidents directly in the data and build the analytics plane so we can quickly establish what happened, size the pattern, and separate real abuse from a false-positive cluster. Build defensible monitoring for risk, abuse spikes, and fraud, all while reducing false positives. Set the technical direction for how we prevent abuse as the platform grows and evolves, and define the patterns other engineers build against. Work with data scientists on feature exploration and training of risk and abuse ML models What We’re Looking For 4+ years building and operating production systems, ideally including work in trust & safety, fraud, payments risk, security, or anti-abuse. Proficient in React, TypeScript, Next.js, and JS runtimes. Ability to write SQL against large event datasets and reason about base rates, precision and recall, and the cost of a wrong decision. Sound judgment when working with incomplete evidence. High agency and a bias toward action; spotting problems, iterating, and shipping without waiting for tickets. AI-forward in your workflow, using coding agents often, finding interesting ways to automate your work, and holding opinions about what works and what doesn't. Comfortable in a small, fast-moving environment where boundaries between teams are intentionally fluid. Discretion and resilience, since parts of this role may involve reviewing or discussing disturbing content and handling sensitive user data. Strong written and verbal communication, able to explain incident findings, detection rules, and systems to a range of audiences. Motivated by adversarial problems, where the counterparty adapts to whatever you ship and the work keeps evolving. Nice to Haves Experience with payments fraud tooling (Stripe Radar, chargeback and dispute flows, crypto payment risk), or with identity and KYC systems. Experience with LLM-specific abuse: jailbreaks, prompt injection, key theft and resale, shared or scraped credentials, automated account farming. Experience operating large scale analytical datastores (e.g. ClickHouse, BigQuery) and observability platforms. Familiarity with the reporting and compliance obligations that come with hosted AI, including illegal content reporting and model provider policy requirements. Existing user of OpenRouter, or active side projects in AI products/infrastructure or developer tooling. If you don’t think you meet all of the criteria below but still are interested in the job, please apply. Nobody checks every box, and we’re looking for someone who is excited to join the team.