Software Engineer (Early Career)

The company

Our client deploys open source infrastructure into the customer's own cloud account: Langfuse, n8n, Airflow, Dagster, ClickHouse, PostHog and self-hosted vLLM on the customer's own GPUs. One click lands the stack in their AWS, Azure or GCP with HA, backups, audit logging and SSO already on, and the client carries every upgrade, CVE and 4am page from then on. Buyers are teams forced into their own VPC by data residency or compliance, from 20 person AI companies through to regulated enterprises. Deals start with an engineer who is tired of maintaining this themselves, and grow from there.

The role

You make developers care, then go and talk to them.

You own the launches, the writing and the demos that reach teams self-hosting this software today, on Hacker News, Product Hunt, Reddit and X, plus the follow-through that turns a spike into retained deployments. You show up where the pain already is, in the issue trackers and Discords of the projects the client runs, answering real questions long before the product comes up.

You self-host these tools, you break them, and you write the story: upgrade postmortems, migration guides, docs-as-marketing, comparison pages, SEO and GEO, dev-influencer collabs, hackathons.

You take first calls and technical demos every week, work out what is breaking in a team's stack and what is forcing them into their own VPC, and show them exactly where this fits. You source and qualify the accounts worth talking to, keep the CRM useful, run follow-up that does not drop, and hand over warm, well-briefed deals. You own the pipeline, the founder owns the signature.

You own the instrumentation too: one funnel in PostHog and one dashboard both of you trust, so the team knows which plays worked and which ones they are telling themselves worked. That means you own the GTM tooling as well as the plays, including Clay, enrichment and the automations behind them. There is nobody else to hand that to.

Content metrics move within days. Pipeline moves over weeks and deals over quarters, and you will be judged on the full arc, not the first spike.

Nobody arrives fluent in all seven tools. You get there by breaking them.

What the client is looking for

• Experience marketing a developer product: you have grown an open source project, a devtool, or a data or AI-infra product, and you can point at the launches, posts, docs or pages that did it.
• Ability to run a technical sales call: comfortable demoing to engineers, asking the uncomfortable qualifying questions, and following up until you get an answer either way.
• Technical credibility, not necessarily as an engineer: you can stand the stack up yourself with Claude Code, read a stack trace, and explain what broke without a hand-holder. Production experience with this specific software is not required, and the role ships no production code. You do need to be the kind of person who would rather install a thing than read about it.
• Distribution obsession: you have built a launch, a content play or an outbound motion that converted, and you get a genuine kick out of it.
• Ownership and bias for action: you own outcomes, not tasks, and you move without waiting for a roadmap.
• Comfortable owning the GTM stack end to end: PostHog, CRM hygiene, Clay, n8n, enrichment waterfalls.

Preferred

• DevRel, developer-tools marketing, or GTM at a dev-tool, data-infra or AI-infra company.
• Early-stage startup experience, or having founded one.
• Activity in the self-hosting and open source infra community.
• Able to work in person in San Francisco at least three days a week.