SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Composio is building the AI-native automation layer for software teams through SDKs, runtimes, and platform tooling that enable developers to compose, evaluate, and operate agentic workflows and AI-powered products.
You will join a small, high-leverage team as an Associate Product Manager focused on the toolkit ecosystem. This role starts operations-heavy: you will run the operations that get apps live on Composio, maintain toolkit health, and automate as much of that work as possible. Over 6-8 months, as workflows and automations mature, the role shifts toward owning ambiguous product problems across the platform—triggers, tools, skills, auth, governance, and toolkit-level issues like rate limits and MCP hosting. This is founder-mode ownership of a product line rather than a traditional PM role with a dedicated engineering team; you will solve problems using agents and a small ops team.
Key responsibilities include:
- Owning the toolkit supply number: how many apps are live on Composio and their health
- End-to-end operations for new apps: research, setup, QA, and launch
- Improving existing toolkits with the product team and clearing blocking issues
- QA and support for every toolkit you bring live; quality is your responsibility
- Building, running, and scaling the ops playbook: SOPs, small tools, AI agents before humans
- Defining and tracking metrics for the function: supply, health, pipeline status
- Shipping product solutions for non-engineering problems across the platform as the ops layer matures
You should have shipped things independently—a side project, tool, micro-business, or system still running in production. You've run real operations with quality bars, not just executed inside someone else's process. You use AI tools daily and can point to specific things you built or automated with them in the last month. You pick work by impact, not interestingness, and have no ego about manual work that isn't automated yet. You can hold technical conversations with engineers without a translator and are comfortable owning problems without a clear owner.
REQUIREMENTS:
- 2-4 years of experience; growth rate matters more than seniority level
- Technical floor: can explain APIs and integrations, reads API docs, writes enough code to build small tools and automations (not an engineer; infra-level work is not the job)
- AI-native automation instinct: default response to repeated work is "how do I automate this?" backed by recent, specific evidence of things built or automated with AI
- Dirty-work appetite: happily run manual processes while automation is being built
- Process maturity: designed or owned a pipeline with throughput, SLAs, or quality bars; left systems running behind you
- Product instinct: take vague problems, figure out what's broken, decide what to build or fix without waiting for specs or dedicated engineering teams
- Organized ownership: routines, follow-ups, nothing dropped; clear communication in writing and in person
- High agency in uncertainty: given a goal with no playbook and no owner above you, define the problem and start before permission
- Operating maturity: this role carries a number from week one; needs someone who has owned outcomes before
NICE-TO-HAVE:
- Founder or early-stage experience
- Experience with SaaS integrations, API products, or developer-facing products
- Built things with agents or LLM workflows beyond personal use
- Engineering-adjacent path: studied engineering and moved into non-technical work, or non-CS background with things built on the side
- High-throughput ops backgrounds (delivery, marketplace, physical ops) alongside the AI-native bar
