GTM Engineer

ElasticDash runs open source inside the customer's own cloud account: Langfuse,
n8n, Airflow, Dagster, ClickHouse, PostHog, plus self-hosted vLLM on their own
GPUs. One click lands it in their AWS, Azure or GCP with HA, backups, audit
logging and SSO already on. We carry every upgrade, CVE and 4am page after that.

Our customers are banks and world-leading SaaS companies. Enterprise only. The
team is small enough that accounts like those are yours in the first month.

Role Description: The GTM Engineer role is a full-time position based in San
Francisco, in person with the founder at least three days a week. In this role,
you make developers care and then go and talk to them. You own the launches, the
writing and the demos that put us in front of every team that self-hosts open
source and can't afford to babysit it, 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 is, in the issue trackers and Discords of the projects we
run, answering real questions before we ever mention ourselves. 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 and hackathons. You take first calls and technical demos every week,
understand what's breaking in a team's stack and what's forcing them into their
own VPC, and show them exactly where ElasticDash fits. You source and qualify
the accounts worth talking to, keep the CRM clean enough to be genuinely useful,
run follow-up that doesn't drop, and hand over warm, well-briefed deals: you own
the pipeline, the founder owns the signature. You own the numbers too, with one
funnel in PostHog and one dashboard we both trust, so we always know which plays
worked and which ones we're telling ourselves worked. Nobody arrives fluent in
all eight tools; you'll get there by breaking them. This is not a marketing-ops
job and it is not a pure content job. We ship weekly, iterate live with users,
and you'll see your work move real numbers within days.

• Experience marketing a developer product: you've 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: you're 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 up the stack yourself with Claude Code, read a stack trace, and explain what broke without a hand-holder. You do not need to have run this software in production before, and you do not need to ship production code for this role. You do need to be the kind of person who'd rather install a thing than read about it.
• Distribution obsession: you've built a launch, a content play or an outbound motion that actually converted, and you get a genuine kick out of it.
• Strong sense of ownership and bias for action: you own outcomes, not tasks; you move fast, make pragmatic decisions, and thrive in ambiguity without waiting for a roadmap.
• Preferred: DevRel, developer-tools marketing, or GTM at a dev-tool, data-infra or AI-infra company.
• Preferred: fluency in the modern GTM stack, living in PostHog and comfortable with Clay, n8n and enrichment waterfalls.
• Preferred: early-stage startup experience (or having founded one), or activity in the self-hosting and open source infra community.
• Ability to work in person in San Francisco at least three days a week and collaborate in a fast-paced startup environment.