Back to jobs

AI Engineer, Developer Relations

sf · San Francisco, California, USA

Actively hiring, first seen by us 8 hours ago
Pay
Pay not listed
Work setting
On-site — work setting source
Location type: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
GTM — team source

What you’ll work on

Full posting
  • You'll own how the AI community meets Composio.

From the employer’s posting
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. Our customers range from your friends in the YC batch to Wabi, Glean, Zoom and many more. We're hiring our developer-facing voice: someone technical enough to build the demo, and funny enough that people actually stop scrolling to watch it. You'll own how the AI community meets Composio. What you'll do?
Apply at Composio

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 2026today
Recorded sightings
2
Last seen by us
Nov 19, 2026
Employer says posted
Jul 8, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 2 and day 14.

From 955 similar postings that came down. Coming down is not always a hire.

Composio is hiring

6 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

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. Our customers range from your friends in the YC batch to Wabi, Glean, Zoom and many more.

We're hiring our developer-facing voice: someone technical enough to build the demo, and funny enough that people actually stop scrolling to watch it. You'll own how the AI community meets Composio.


What you'll do?

  • Build in public. Ship demos, prototypes, and technical content that show what's actually possible with Composio - across whatever format fits: X threads, short-form video, YouTube, a livestream, a podcast appearance. If it shows what agents plus tools can do, you make it, and you narrate it as you go.

  • Own our voice. Run our presence on X and LinkedIn, and grow your own account as a technical voice people in the AI community actually follow.

  • Show up in the real world. Represent Composio at SF meetups, hackathons, and developer conferences. Build genuine relationships with the people building agents, and share your learnings with the world.

  • Bias towards action. Ship the narrow, signal-generating version today - the post, the demo, the two-minute video - read what lands, then either double down or kill it. Don't wait for permission to try something.

  • Work across the company. Partner with product, engineering, and marketing to turn what you're hearing from developers into shipped product and better positioning.

What we're looking for

The hard-to-teach part is taste and timing: knowing what developers find genuinely cool versus what reads as marketing, and producing quality content developers actually want to engage with. Technical credibility is required - you build with our API and ship demos - but it's the foundation here, not what sets you apart. That part is the taste and the humor.

  • You can actually build. You've written real code, you can wire up an API and our SDK, and you can ship an interesting demo.

  • You genuinely like being public. Posting, filming, speaking, being on camera - this energizes you rather than drains you. You can make a technical thing legible and exciting to a scrolling developer.

  • Opinionated, with a high bar. You have strong views on what makes content good, and you hold yourself — and us — to them. You'd rather kill a mediocre post than ship it, and you'll push the whole company to be better too.

  • Comfortable across formats. You'd rather film a two-minute demo than write a press release. Text, video, audio, stage - you move between them without losing your voice.

  • AI-native. You build with LLMs and keep up with what's happening in the ecosystem.

  • Owner. You take a goal, decide what to make, ship it, measure whether it landed, and flex across all of the above - without waiting for a content calendar to tell you what to post.

  • Human. You build trust and admit what you don't know.

Strong preference for

  • Based in SF (or open to relocation)

  • An existing audience or a track record of building in public

  • Hands-on experience with agents, LLMs, MCP, and the modern AI dev stack

Bonus points

  • A presence in the AI community through open source, writing, or building in public

About the role

We file this job under AI Engineer, by the work the posting describes.

AI engineers build products on top of AI models that already exist, most often large language models: they connect a model to a company's data and tools and ship the assistants, agents and search features people use.

Postings ask for strong Python or TypeScript, experience with model APIs, retrieval and agent frameworks, and ways to test whether the model's answers are good enough.

An ML engineer trains and serves models; an AI engineer usually starts from a model someone else trained and builds the product around it, though titles often mix the two.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

San Francisco, California, USA

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.