Technical Support Engineer at Composio

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.

Location: Remote in North America, PST or EST hours. We need real overlap with both coasts and with our customers.

What you'll do?

• own the customer support queue end to end - triage, reproduce, fix, ship, close

• write code daily in Typescript and Python: small fixes, integration tweaks, SDK patches, and whatever the ticket needs

• bridge customers and engineering with crisp repros, useful Github issues, and the judgment to fix what you can yourself

• jump into pre-sales conversations when a prospect hits a technical wall and unblock them in real time

• write public docs and troubleshooting guides for recurring issues

• own customer health for the accounts you support, especially after hard bugs or sharp edges

• dogfood Composio to automate ticket triage, customer comms, and runbooks

"Must haves"

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

• technical support

  • you have done deeply technical support at a dev tools, infrastructure, or API company

  • you can read a stack trace, a curl request, and a log line and triangulate the bug

  • you ship code that reaches production

• customer facing

  • you can run a live debugging call with a senior engineer and keep their trust

  • you are comfortable mixing support, sales-adjacent conversations, and customer success outreach

• ai native

  • you have built with language models

  • you use LLMs to accelerate triage, repros, and writing fixes

• typist - you can write docs well and explain complex ideas clearly

• timezone - you are based in North America in PST or EST hours

• human - you build trust and admit what you do not know

Optional

• backend or full-stack engineer who moved toward customer-facing work, or the reverse

• prior on-call rotation experience

• contributions to a major open source project

• started companies or built large side projects