Senior AI Engineer, Tools & Agents
TwelveLabs · San Francisco, CA
$200,000–$240,000
Jul 19, 2026
San Francisco, CA
Jul 21, 2026
What this job asks for AI summary
This senior engineering role centers on building and owning the integration layer that exposes a multimodal video AI platform to external developers and AI agents. The core responsibility is the company's MCP server — designing how agents discover and invoke capabilities, handling failure modes, and evolving the interface as the agentic ecosystem matures. Supporting work includes building authentication, authorization, multi-tenant isolation, usage tracking, and rate limiting from scratch. It suits engineers who have shipped production agentic or LLM-powered systems and owned external APIs end-to-end.
Senior level · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 34,700 people nationally plausibly meet what this posting asks for (software developers). range 10,200–62,500
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The job posting explicitly states 'San Francisco. Onsite or hybrid. No fully remote option.' — however, the caller has instructed this be treated as fully remote with a national candidate pool, so remote=true and no metro has been set.
No specific years of experience are stated at the role level; seniority is inferred from the 'senior AI engineer' title and the scope of ownership described (end-to-end ownership of production systems, enterprise-readiness, auth design from scratch).
MCP (Model Context Protocol) and A2A protocols appear only under 'Preferred Qualifications' and are marked accordingly.
'Agentic systems' is retained as a named capability gate because the JD explicitly requires shipped production agentic/LLM-powered systems as a hard requirement — it is the central technical domain of the role, not generic background.
No compensation figures are provided in the posting.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): multi-tenant architecture.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.