composio22d ago

Member of Technical Staff - Enterprise Platform

India·Bangalorefull-timelead

OtherMember Of Technical Staff

2 views0 saves0 applied

Apply Now

Quick Summary

Overview

About Composio We're building the learning infrastructure that transforms AI agents into true digital workers. While today's agents can reason and plan, they fail to do meaningful work because they lack real experience operating in apps.

Key Responsibilities

Agent infrastructure platform: The foundational layer that enterprise AI agents run on — governance, observability, and control planes for MCP-powered agent ecosystems.

Requirements Summary

You've built platforms at genuine scale — not just high user counts, but high complexity: many customer types, deployment models, and integration surfaces You think in abstractions and primitives.

Technical Tools

hubspotab-testingsaas

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 some incredible angels like Guillermo Rauch (CEO of Vercel), Dharmesh Shah (CTO of Hubspot), Gokul Rajaram. Beginning of this year we 3x our ARR, our customers range from your friends in the YC batch to Wabi, Glean, Zoom and many more.

Responsibilities

~1 min read

→
evolve the platform primitives enterprise agents run on - governance, auditability, observability, permissions, routing, and control planes
→
build the secure integration gateway between customer agents, SaaS tools, internal systems, and APIs
→
design multi-tenant abstractions for isolation, configuration, extensibility, and deployment flexibility
→
turn enterprise onboarding from a services engagement into a repeatable product experience
→
work directly with customers to understand where agent infrastructure breaks in real deployments
→
make security, compliance, and reliability first-class product capabilities rather than later-stage patches

Requirements

~1 min read

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

you have built systems where the abstractions were the product
you can reason about multi-tenancy, isolation, auth, routing, and observability without hand waving
you know how to ship reliable systems while the product is still changing fast

you understand deployment flexibility, security, admin tooling, and compliance as product problems
you can separate one-off customer requests from primitives that should exist for every customer