What you'll own

• Positioning and messaging. What E2B is, who it's for, why it wins, and how that changes as the agent market changes. This is the foundation everything else in marketing sits on, and it doesn't exist yet.
• Launches. Every product release goes through you: the narrative, the assets, the sequencing, the distribution. You set the launch cadence and hold engineering to it.
• The content engine. Technical articles, comparison and migration pages, customer stories, launch content, the website. You write the first flagship pieces yourself, and you run the technical writer and video producer who scale it from there.
• Pricing, packaging, and competitive. Usage-based pricing for infrastructure is a product marketing problem. You own the packaging story and the competitive positioning that sales and self-serve both rely on.
• Sales enablement for the enterprise motion. Decks, one-pagers, objection handling, proof points. Built once, used everywhere.
• A budget. Paid programs, sponsorships, tooling, freelancers. You propose it, you own it.
• The function. You're the first person in it and we expect you to grow it as E2B grows.

What's already in place

Two growth engineers and a data scientist who own instrumentation, attribution, and the self-serve funnel, so what you ship will be measurable. A customer base that includes the companies most developers in this space want to learn from, and case-study material we've never written up. A community and ecosystem lead being hired alongside you.

What we've learned so far

Our buyers are engineers who trust benchmarks and code over adjectives. Comparison pages and docs-adjacent content convert better than anything else we've tried. Increasingly, developers find tools through LLM answers rather than search, and we think content should be built with that in mind. Treat these as inputs, not a plan; the plan is yours.

First 90 days

Write the positioning doc, with input from founders, sales, and the ten customers who know us best. Ship two customer stories and two flagship technical pieces. Run one launch end to end. Give us a content and launch calendar for the following two quarters with a clear argument for why it's the right one.

How we'll judge year one

Whether E2B can be explained in a sentence by someone who isn't us. Launch cadence and reach. Growth in content-attributed signups and enterprise pipeline that cites something we published. Whether the writer and video producer are shipping work you're proud of.

Who you are

• 5+ years in product or developer marketing for a technical product, with at least one stretch where you were the only marketer and it worked.
• You write. Not "manage writers." Your portfolio has technical pieces you drafted yourself for a developer audience, and you can read code well enough to write about sandboxing, isolation, and runtime security without a ghostwriter.
• You've done positioning from scratch and launched products that engineers adopted.
• You understand usage-based pricing for infrastructure, or you've done pricing work somewhere close enough to learn fast.
• You've been the number two on a product marketing team and want to be the one deciding.
• You're comfortable being measured. Traffic isn't the deliverable; signups and pipeline are.

Nice to have

Experience with agent frameworks, model infrastructure, or sandboxes. Familiarity with answer-engine or SEO programs. A track record tying content to pipeline at a high-growth startup.

What it's like to work at E2B

We're a fast-growing startup with in-person (4 days on-site, 1 day WFH) offices in San Francisco and Prague, Czech Republic. We already generate 8-figure revenue and work directly with top-tier AI companies like Manus, Genspark, Lindy, Groq, Artificial Analysis and other exciting teams pushing the frontier of AI.

We offer healthcare, vision, and dental insurance, unlimited PTO, 401k, and a variety of perks for in-office employees.