Composio

Member of Technical Staff, Enterprise Product at Composio (San Francisco, CA)

Composio· San Francisco, CA·

Role details

Work type
Onsite
Employment
Full-Time

Job description

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 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. Enterprise Product sits where the hardest customer workflows become durable product. You will work directly with enterprise customers and FDE, turn ambiguous asks into product primitives, and ship the code that makes the next customer easier than the last.

WHAT YOU'LL WORK ON

  1. Turn large enterprise APIs into agent-usable tool surfaces: tool granularity, composite tools, descriptions, scopes, auth, and evals.
  2. Productize repeated FDE work into self-service patching, QA harnesses, deployment paths, admin controls, docs, and guardrails.
  3. Make enterprise deployments repeatable across hosted, VPC, on-prem, regulated, and BYOK environments.
  4. Build the product layer that lets Composio scale from bespoke enterprise engagements to repeatable enterprise motion.

WHAT YOU'LL DO

  • Own enterprise product surfaces end to end: discovery, spec, design, implementation, QA, release, adoption, and iteration.
  • Ship production code across toolkits, SDKs, auth and scope flows, admin surfaces, deployment tooling, and customer-facing enterprise features.
  • Work with FDE, customers, and core engineering to convert field pain into crisp product requirements and shipped primitives.
  • Build evals and QA loops that prove enterprise workflows are reliable, not just demo-ready.
  • Write the specs, docs, launch notes, and customer-facing updates that make the work easy to adopt.

"MUST HAVES"

if you are very good, nothing is a must per se

  • Product-minded engineer: you turn messy workflows into clean product, then ship the code.
  • Enterprise integration depth: OAuth, consent, scopes, service accounts, webhooks, rate limits, and strange API behavior do not scare you.
  • Customer ownership: you can take a named customer or product surface from first conversation to live usage.
  • AI native: you have built with language models, built for language models, and have opinions on agents, MCP, evals, and tool choice.
  • Systems judgment: you think in rollout paths, rollback paths, security exposure, version skew, and maintainability.
  • Clear writer: your specs, docs, and customer updates earn trust under deadline.

OPTIONAL

  • Python in production; TypeScript a plus.
  • API platform, iPaaS, developer tools, infra, or integration-heavy background.
  • Prior FDE, solutions architect, sales engineer, or enterprise product engineering role.
  • Kubernetes, Helm, Temporal, Postgres, Replicated, cloud secret managers, or packaged self-hosted delivery.
  • Security and compliance exposure: SOC 2, Vanta-style programs, questionnaires, CVE triage, or RCAs.

Why work at Composio

  • Culture highlights: The team is building infrastructure that “shapes AI’s future” and solving hard, unsolved problems in distributed self-improving systems. Emphasis on elegance, autonomy, and collective intelligence.
  • Remote/hybrid/office policy: Not explicitly defined, but HQ is in San Francisco with offices in the US, India, Canada, Nepal, and Colombia. Hybrid/remote likely depending on role.
  • Notable perks or engineering culture: Engineers work on cutting-edge LLM infrastructure, distributed systems, and developer tools. The blog highlights a focus on “hard problems no one’s cracked yet” and a commitment to creating “systems that feel magical.” Open roles include Member of Technical Staff (Research Engineer, Product Eng, Enterprise Platform), Growth Engineer, and Founding BDR – indicating a fast-scaling, high-impact environment.

Application questions