Enterprise Product Engineering Lead

At Composio, we are building infrastructure that allows agents to communicate with the tools you use for work including Github, Gmail, Notion, Salesforce, and 500+ more. We are a small team wrangling problems from auth to orchestration, building the most capable bridge between your agents and your tools. We raised a $29M 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’d our ARR, our customers range from your friends in the YC batch to AWS, Glean, Zoom and many more.

Why are we looking to hire for this role?

Enterprise is getting reshaped by agents—most companies just don’t know it yet. Our enterprise motion today runs on founder time. Every customer call, every design doc, every scope negotiation flows through the co-founders and Head of Engineering. We need someone who owns enterprise product end-to-end—not as a middleman between customers and eng, but as the person who decides what gets built, defends the technical tradeoffs, and ships it. This is the person who takes us from 5 enterprise customers to 50 and gets us to $20M in enterprise revenue.

What you’ll do?

Own every enterprise customer touchpoint—weekly syncs, pre-sales technical validation, POC support—and make product calls in real time without escalating · live in the codebase enough to write design docs, estimate build complexity, and call out when a customer request is architecturally wrong · triage enterprise requests against the backlog, sequence tradeoffs, and commit to timelines you can defend · push back on customers when their ask doesn’t make sense—and do it in a way that builds trust · set the enterprise quality bar: features can ship slower than PLG, but nothing ships broken · build the enterprise playbook, escalation paths, and processes we don’t have yet · work daily with Head of Revenue, Head of Engineering, and solutions team to translate customer pain into engineering priorities.

“Must haves” if you are very good, nothing is a must per-se

you’ve shipped product and can hold your own in an architecture discussion—engineers need to respect your judgment · you’ve made hard product calls under pressure: killed a feature mid-build, told a strategic customer their approach was wrong, shipped a v1 that deliberately left things out · you carry enough confidence that enterprise buyers and senior engineers both trust you in the room · you think in systems and tradeoffs, not feature requests · you’ve probably started something, sold something, or run a P&L · developer tools or infrastructure background · enough engineering to navigate a codebase, estimate timelines, and have a technical opinion that holds up

How to apply

Email [email protected] — send us your resume and a short note on a product decision you owned that a customer disagreed with. If you are exceptional and we want to work together, we expect pay to not be an issue