Technical Content

You own everything a technical builder reads or watches about Mindee outside the product UI: API reference, guides, SDK docs, tutorials, sample projects, videos, changelog, and technical talks. You also own how that content is consumed by machines: AI coding agents, our in-product assistant, and no-code platforms. You are the single owner of technical content quality, freshness and machine-readability.

The position sits between Product and Marketing and carries objectives from both. You report to Product so you sit next to the roadmap and know what ships before it ships. You work daily with Marketing on distribution and with Engineering on accuracy.

What you will be responsible for

1. Visibility among technical builders

• Produce technical content that developers actually search for and share: guides, comparisons, benchmarks, integration tutorials, open-source contributions around docTR

• Represent Mindee at meetups and conferences, and on developer-oriented channels (YouTube, podcasts, communities)

• Turn product releases into technical narratives that reach the right audience

2. Onboarding

• Own the first-hour experience: quickstarts, SDK setup, sample repos, first-call-to-production paths for each major use case

• Measure where new users get stuck and fix it with content or product feedback

• Maintain a library of ready-to-run examples across our SDKs and no-code integrations

3. Retention and expansion

• Document advanced capabilities so existing users go deeper: validation rules, enrichment, environments, fraud detection, and whatever ships next

• Produce release-driven content (changelog, migration guides, “what’s new” videos) that keeps active accounts current

• Feed the in-product assistant with accurate, structured documentation it can rely on

4. AI-native documentation and developer experience

• Make Mindee the easiest document API for an AI agent to integrate: llms.txt, MCP server documentation, self-contained copy-paste examples, structured schemas, ready-to-use agent skills and prompts

• Own the integration experience on no-code and automation platforms (n8n, Make, Zapier and equivalents): templates, guides, listings

• Run the loop: watch how humans and agents actually integrate Mindee, find the friction, fix it with content or elevate it to Product as a DX issue

5. Quality and freshness

• Every piece of technical content is accurate against the current product, or it is removed

• Build the process for this: docs reviewed at feature spec time, updated at release, audited on a schedule

• Define and track the metrics: docs coverage, time-to-first-call (human and agent-assisted), support tickets caused by documentation gaps, content-attributed signups and activations

Objectives you will be measured on

From Product:

• Time-to-first-successful-API-call for new signups, including integrations done through AI coding agents

• Share of features shipped with complete documentation at release

• Reduction in support and sales-engineering load attributable to documentation

From Marketing:

• Organic traffic and signups from technical content

• Reach and engagement of technical videos, talks and community presence

• Mindee’s presence and accuracy in the answers AI assistants give about document extraction

• Content-attributed activation and expansion

Why this role?

• You own a function, not a queue of tickets. The scope is yours to define and defend

• Direct line to the roadmap and to the people who build the product

• A real technical audience with an existing community

• A company that runs on product-led growth, where your work shows up in