Solutions Architect at Composio in San Francisco, CA

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 (https://lsvp.com/stories/investing-in-composio-building-the-backbone-of-ai-agent-intelligence/) 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. THE ROLE Our enterprise customers are building real agent systems on top of us. They need someone who can sit in the architecture review, push back on a bad design, and then go write the proof of concept that shows the right way to do it. This is not a slide deck role. You are expected to ship code in customer environments, against their data, with their constraints. WHAT YOU'LL DO? - own the technical relationship with our top accounts. pre sales discovery, architecture design, integration planning, post launch tuning. - build proofs of concept end to end. typescript, python, our sdk, their stack. make the demo real, not theoretical. - diagnose hard customer issues against our platform live. open devtools, read logs, reproduce in a notebook, file a github issue with a repro the eng team can act on. - write reference architectures and reusable code patterns that the rest of the team can hand to the next customer. - partner with engineering on the enterprise roadmap. when five customers ask for the same thing, you are the one who already has the design doc ready. - dogfood Composio. use our product to automate parts of your own workflow. (the product is very good, this is easier than you think.) "MUST HAVES" if you are very good, nothing is a must per-se - core solutions or applied engineering - you have shipped production code, not just demo code - you have owned a customer technical relationship from first call to live deployment - you have made architecture calls under pressure and defended them in front of senior engineers on the customer side - ai native - you have built with the language models - you have built for the language models - you keep up with what the frontier labs ship - taste (https://www.are.na/editorial/notes-on-taste), you have that "finger feel" for what makes a good developer experience - typist, you can write docs well and explain complex ideas clearly - human, you build trust and admit what you don't know OPTIONAL - multiple years of experience writing typescript or python in production - background at a developer tools or infrastructure company - contributions to a major open source project - you have started companies or built large side projects