Responsibilities

• Plan and publish high-impact content across blog, landing pages, docs, and community.
• Write deep-dive technical articles for developers (model inference, training, architecture breakdowns, benchmarks, deployment patterns).
• Translate complex AI infrastructure and technical concepts into clear, structured content.
• Collaborate with engineers to turn internal benchmarks, experiments, and system design work into publishable metrics-driven product blog posts.
• Create short-cut product guides, quickstart tutorials, integration walkthroughs, and technical documentation.
• Build and maintain a structured keyword/content strategy (clustered by funnel stage).
• Identify and update underperforming pages based on analytics and search trends.
• Contribute to thought leadership around AI infra, MaaS, model optimization, and cost efficiency.
• Growth & Distribution
• Manage our presence across substack, github, and other technical content platforms.
• Turn product releases and infra updates into engaging technical narratives.
• Work cross-functionally with product, engineering, and design to extract ideas worth amplifying.
• Support SEO experiments, landing pages, and growth loops.
• Repurpose long-form technical content into social threads, short posts, and community content.
• Analytics & Iteration
• Track performance across GA4, Semrush, Ahrefs, and social tools.
• Own reporting and feedback loop: what’s working, what’s not, and what to try next.
• Continuously optimize content for traffic quality, developer engagement, and conversion.
• Measure impact across awareness → signup → GTM activation funnel.

Requirements

• 4–6 years of experience in content marketing, growth, or technical writing.
• Experience in AI, infrastructure, dev tools, cloud, or SaaS.
• Strong writing skills: able to break down complex technical topics clearly.
• Comfortable writing for developer audiences.
• Experience with SEO strategy and tooling (Semrush, Ahrefs etc.).
• Familiarity with AI infrastructure, inference workflows, APIs, or developer ecosystems.
• Comfortable in a startup environment: fast-paced, autonomous, iterative