Responsibilities

• Build the answer layer. Create problem-shaped, docs-adjacent content that earns citations in LLM answers and holds up under a developer’s scrutiny.
• Own the editorial loop for the AEO scanner. Partner with growth engineering on the scanner, choose the prompts E2B is losing, identify the gaps, ship content to close them, and measure whether citation share moves.
• Publish credible comparison and migration content. Evaluate real alternatives using transparent benchmarks and enough technical depth to earn engineers’ trust.
• Turn customer outcomes into technical proof. Develop case studies from top accounts and sequence them with account-expansion plays so the right evidence lands when a buyer needs it.
• Run the editorial calendar as a test backlog. Prioritize work by expected impact, not publishing frequency.
• Operate an experiment loop. Define the hypothesis, metric, cohort, and review date for each piece. Rewrite once when a test misses, then retire it if it still fails.
• Audit and prune the library quarterly. Remove or improve content that doesn’t earn citations, influence qualified pipeline, or strengthen the answer layer.

Requirements

• 4–7 years creating technical content for a developer audience.
• The ability to read code and write credibly about sandboxing, isolation, runtime security, and adjacent infrastructure topics without relying on hand-waving.
• A strong editorial point of view. You know when a topic deserves a deep technical argument and when a piece should not be published at all.
• Experience connecting content to a real measurement model across citations, qualified pipeline, conversion, and revenue influence.
• Comfort partnering directly with engineers, growth, sales, and customers to uncover evidence and turn it into useful content.
• A bias toward ownership and experimentation. You form hypotheses, ship, measure, learn, and make decisive calls about what happens next.
• The judgment to stop work that isn’t earning its place. Traffic alone is not the deliverable.

Preferred

• Experience running an SEO or AEO (answer-engine optimization) program.
• You can read simple code and write about sandboxing, isolation, and runtime security without a ghostwriter;
• Experience building technical comparison, migration, or developer-education content for a B2B infrastructure company.
• A track record of tying content programs to pipeline in a high-growth startup.

Benefits

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