Composio
Technical Support Engineer
Remote (US: PST or EST) · Remote (restrictions not stated) · FullTime
Apply on the employer’s site ↗See how well you match this job
You apply directly with the employer. ROLIVA does not submit applications from this page and is not the employer.
About the role
Description from the employer’s posting. Check the employer’s page for the current version.
- EmployerComposio
- LocationRemote (US: PST or EST)
- Work styleRemote (restrictions not stated)
- Employment typeFullTime
- Employer posted
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
Show full description
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
Check your resume against this job Free, no sign-up. Nothing you paste is stored.
Staying safe while you apply
- Never pay to apply, interview or accept an offer. ROLIVA never asks you for payment to apply to a job.
- Apply only through the official “Apply on the employer’s site” button, on the employer’s own site, and check that a recruiter’s email uses that employer’s own domain rather than a free email address.
- Be cautious of an offer made with no real interview, or pressure to decide quickly or share financial details early.
Does something look wrong with this listing? Use “Report broken link” in the role details, or read ROLIVA’s full job-safety guidance ↗.
Preparing for this role with ROLIVA
- Check the fit.
Compare the requirements with the experience you have confirmed, including gaps.
- Prepare honestly.
Build interview stories and application drafts from your own evidence.
- Keep track.
Save the role and record your own application status and follow-ups.
At a glance
- Work styleRemote (restrictions not stated)
- Employment typeFullTime
- Employer posted
- Added to ROLIVA
- Last checked
Skills in this posting
Skills ROLIVA found in the employer’s own description above. A mention is not a requirement.