Responsibilities

• Launch blog posts and technical announcements written for engineers, not marketing audiences
• API quickstarts, integration guides, and tutorials that end with the developer having done something real
• SDK and API reference documentation that is accurate, complete, and fast to navigate
• Launch benchmark reports with full methodology - structured to be cited by press and AI answer engines
• Technical comparison content written with absolute metrics, not relative claims
• Ongoing benchmark and evaluation content that keeps SubQ visible as the competitive landscape shifts
• Evergreen technical content optimized for search and AI answer engine citation
• Content strategy that treats engineers as the primary reader and rankings as a byproduct
• Structured content that surfaces correctly in LLM-generated answers - not just Google

Requirements

• You've written technical content for a developer-first company. Your portfolio has pieces engineers have actually shared or cited.
• You understand AI infrastructure and LLMs; you can discuss inference tradeoffs and API design.
• You write with conviction; specific claims, sourced numbers, no hedging; absolute metrics land harder.
• You know how to write for search, AI citation, and technical communities; you've done all three.
• You’re comfortable working directly with engineers. Technical accuracy isn’t someone else’s problem - it’s yours.
• You have strong opinions on quality developer content; Stripe and Cloudflare set benchmarks.
• You have experience writing benchmark methodology documentation or ML evaluation content
• You’ve built with LLM APIs in production - not just written about them

Benefits

• Comprehensive health, dental, and vision coverage
• Flexible paid time off
• Equity participation