Composio

Forward Deployed Research Engineer

San Francisco, California, United States · On-site · FullTime

Apply on the employer’s site ↗See how well you match this job

You apply directly with the employer. ROLIVA does not submit applications from this page and is not the employer.

About the role

Description from the employer’s posting. Check the employer’s page for the current version.

EmployerComposio
LocationSan Francisco, California, United States
Work styleOn-site
Employment typeFullTime
Employer posted3 months ago

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.

Show full description

• 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.

See how well you match this job Apply on the employer’s site ↗

Check your resume against this job Free, no sign-up. Nothing you paste is stored.

Staying safe while you apply

Never pay to apply, interview or accept an offer. ROLIVA never asks you for payment to apply to a job.
Apply only through the official “Apply on the employer’s site” button, on the employer’s own site, and check that a recruiter’s email uses that employer’s own domain rather than a free email address.
Be cautious of an offer made with no real interview, or pressure to decide quickly or share financial details early.

Does something look wrong with this listing? Use “Report broken link” in the role details, or read ROLIVA’s full job-safety guidance ↗.

Preparing for this role with ROLIVA

Check the fit.
Compare the requirements with the experience you have confirmed, including gaps.
Prepare honestly.
Build interview stories and application drafts from your own evidence.
Keep track.
Save the role and record your own application status and follow-ups.

Create a free workspace or log in.