Time since we first saw it
Day 0
Early. Similar jobs usually come down between day 3 and day 18.
From 415 similar postings that came down. Coming down is not always a hire.
sf · San Francisco, California, USA
Actively hiring, first seen by us 8 hours agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Engineering › ResearchFrom the employer’s posting
Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 0
Early. Similar jobs usually come down between day 3 and day 18.
From 415 similar postings that came down. Coming down is not always a hire.
6 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
OPTIONAL • years of Python in production (Typescript a plus). • API platform, iPaaS, or integration-heavy background.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
At Composio, we are building infrastructure that allows agents to communicate with the tools you use for work including Github, Gmail, Notion, Salesforce, etc. We are a small team of engineers wrangling problems from context to search, that help us provide the most capable bridge between your agents and your tools. We raised a $25M Series A from Lightspeed with angels like Guillermo Rauch (CEO of Vercel), Dharmesh Shah (CTO of Hubspot), and Gokul Rajaram. We've 3x'd our ARR this year, and our customers range from your friends in the YC batch to Wabi, Glean, Zoom and many more.
the action layer for AI agents is the least-solved part of the stack. this role works at that frontier: embedded with the customers pushing hardest, turning open research questions into tools their agents use, shipping the code yourself.
THE FRONTIER YOU'LL WORK ON
• turning an 800-endpoint enterprise API into a tool surface a model can navigate. tool granularity, composite tools, description engineering, scope design. no textbook exists; you write it in production.
• building the evals that tell us an agent picked the right tool. the field has no good answer; your harnesses become ours.
• working directly with the engineers defining what agents can do, and feeding what breaks back into the product.
WHAT YOU'LL DO?
• own enterprise accounts end to end: discovery, spec, implementation, QA, release.
• ship production code in our toolkit monorepo and customer SDKs: custom and composite tools, schema and scope changes, per-customer patches.
• turn large enterprise APIs into agent-usable tool surfaces, and build the evals that prove the model picks the right tool.
• QA toolkits, and build the harnesses that make QA repeatable instead of artisanal.
• run weekly customer syncs: the summaries, ETAs, and escalations that keep an engagement coherent.
• operate per-customer tool-patching as self-service, not escalation.
• dogfood Composio on your own workflows.
"MUST HAVES"
if you are very good, nothing is a must per-se
• applied integration engineering
– you ship production code, not demos.
– you live in enterprise APIs and auth: OAuth 2.0, consent models, scope design, multi workspace tokens. you know the edge cases from scars.
– you make architecture calls under pressure and defend them to a customer's principal engineers.
• customer technical ownership
– you've taken a named enterprise account from first call to live.– you turn vague asks into specs, and push back when the ask is wrong.
• ai native
– you have built with the language models.
– you have built for the language models, and treat the agent-tool interface as an open research problem.
• taste - finger feel for good developer experience.
• typist - you explain complex ideas clearly under deadline.
• human - you build trust and admit what you don't know.
OPTIONAL
• years of Python in production (Typescript a plus).
• API platform, iPaaS, or integration-heavy background.
• prior FDE / solutions-architect role selling to big tech.
• frontier output: MCP servers, tool-use evals, agent-tooling writeups.
We file this job under Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, USA
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.