Member of Technical Staff - Enterprise Platform

Composio builds infrastructure that lets AI agents talk to the tools people work in, GitHub, Gmail, Notion, Salesforce and more. It raised a $25M Series A from Lightspeed with angels including Guillermo Rauch, Dharmesh Shah and Gokul Rajaram, says it tripled ARR at the start of this year, and counts Glean, Zoom and Wabi among customers. This role is the enterprise platform: the primitives enterprise agents run on, meaning governance, auditability, observability, permissions, routing and control planes, plus the secure integration gateway between customer agents and their systems, and multi tenant abstractions for isolation and deployment flexibility. The requirement list is written unusually: it says "if you are very good, nothing is a must per-se", lists capabilities rather than years, and puts multiple years of TypeScript or Go under Optional. Bangalore, small team.

What the posting asks for, and how it frames it. Composio heads its requirement list "Must haves" and then immediately qualifies it with "if you are very good, nothing is a must per-se". The capabilities it lists are:

Core platform engineering: 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.

Enterprise judgement: 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.

AI native: you have built with language models; you have opinions about agents, MCP, tool use and where current systems fail.

Plus two the posting labels directly: "typist", meaning you can write design docs and explain complex infrastructure clearly, and "human", meaning you build trust and admit what you do not know.

Listed as Optional: multiple years writing TypeScript, Go or similar systems languages; experience building enterprise developer platforms inside large organisations; security, compliance or deployment model depth; and having started companies or built large side projects.

The real day to day: evolving the platform primitives enterprise agents run on, covering governance, auditability, observability, permissions, routing and control planes; building the secure integration gateway between customer agents, SaaS tools, internal systems and APIs; designing multi tenant abstractions for isolation, configuration, extensibility and deployment flexibility; turning enterprise onboarding from a services engagement into a repeatable product experience; working directly with customers to understand where agent infrastructure breaks in real deployments; and making security, compliance and reliability first class product capabilities rather than later stage patches.

Location and team: Bangalore, and Composio's own board marks this as not remote. The posting describes a small team of engineers.

⚠️ Years: this posting states no years of experience anywhere, which is why our experience filter cannot place it. Note that it goes further than most and puts "multiple years writing Typescript, Go, or similar systems languages" under Optional rather than required.

Honest fit guidance: do not read the absence of a years bar as an entry level opening. The capability list (multi tenancy, isolation, auth, routing and observability reasoned about "without hand waving", plus systems where the abstractions were the product) describes a senior platform engineer. What the framing does mean is that a strong portfolio can substitute for a conventional CV here in a way it cannot at the enterprise employers on this list. If you have built infrastructure others build on and you have real opinions about agents and MCP, this is a posting where saying so is worth more than your years count.