Responsibilities - Own and scale Chalk's technical documentation: user guides, SDK and API docs, conceptual overviews, and example workflows. - Translate complex, low-level systems into elegant, accessible writing, reading production code to document with precision and empathy. - Treat docs as a product. Set the roadmap, define what good looks like, and measure it (time-to-first-success, ticket deflection, agent answer quality, GEO and AEO rankings). - Make Chalk's content LLM-native so Claude, Cursor, and ChatGPT can ship correct, current Chalk code on a developer's behalf. Information architecture, retrieval-friendly chunking, canonical examples, llms.txt, and clean versioning. - Design technical diagrams and educational content (tutorials, deep-dives, video scripts, runnable examples) that close the gap between "read about Chalk" and "ship with Chalk." - Build the feedback loop. Mine support tickets, sales calls, and AI search logs for gaps and close them in days, not quarters. - Keep docs living. Every product change ships with docs. Examples are tested in CI. Nothing rots. - Establish Chalk's technical voice and how we communicate as a company.