Technical Support Engineer

• 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
• 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
• 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
• backend or full-stack engineer who moved toward customer-facing work, or the reverse
• prior on-call rotation experience

None flagged.