Sr. Technical Writer

Archetype AI

Archetype AI

Marketing & Communications, IT
Europe
Posted on Jan 16, 2026

About Archetype AI

Archetype AI is developing the world's first AI platform to bring AI into the real world. Formed by an exceptionally high-caliber team from Google, Archetype AI is building a foundation model for the physical world, a real-time multimodal LLM for real life, transforming real-world data into valuable insights and knowledge that people will be able to interact with naturally. It will help people in their real lives, not just online, because it understands the real-time physical environment and everything that happens in it.

Supported by deep tech venture funds in Silicon Valley, Archetype AI is currently pre-Series A, progressing rapidly to develop technology for their next stage. This presents a unique and once-in-a-lifetime opportunity to be part of an exciting AI team at the beginning of their journey, located in the heart of Silicon Valley.

Our team is headquartered in Palo Alto, California, with team members throughout the US and Europe.

We are actively growing, so if you are an exceptional candidate excited to work on the cutting edge of physical AI and don’t see a role that exactly fits you below you can contact us directly with your resume via jobs

About the Role

We’re hiring a self-directed Senior Technical Writer to own the developer documentation experience for the Archetype Platform, from the first successful API call to production-grade usage. You’ll work directly with Engineering, Product, AI Research and Customer Success to turn evolving code, internal references, and architecture into clear, accurate, maintainable developer docs that enterprise teams can actually execute against.

This is a high-ownership role with direct customer impact: your work will reduce onboarding friction, shorten time-to-first-success, and prevent support churn by ensuring our Quickstart, API guides, cookbooks, and troubleshooting stay correct and up-to-date as the platform ships. If you’ve built docs that developers trust and you can keep runnable examples in sync with releases, then this role is built for you.

Top success factors

  • Exceptional developer-facing writing with minimal guidance; strong judgment on structure and clarity

  • Ability to build and maintain runnable Quickstart + cookbook examples (Python) that stay current and working across releases

  • Process mindset to keep docs current (release hooks, review cadence, feedback + analytics loop)

Core Responsibilities

  • Own developer documentation for the platform (Quickstart, API reference, cookbooks, troubleshooting).

  • Convert internal inputs (code, diagrams, PRDs, tribal knowledge) into accurate docs with clear “happy path” and “debug path.”

  • Create and maintain runnable Python examples while keeping examples in sync with releases via a docs-as-code workflow.

  • Establish a lightweight docs intake → prioritization → review cadence with Engineering, Research, Product, and Customer Success.

  • Use feedback and basic analytics to identify gaps; publish a monthly doc health report with prioritized fixes.

  • Support customer onboarding by observing sessions and folding real friction back into documentation improvements.

Minimum Qualifications

  • 5–8+ years creating developer documentation for APIs/SDKs/platforms.

  • Strong docs-as-code workflow (Git, PRs, Markdown; any modern doc stack).

  • Able to read and lightly modify Python; comfortable with REST APIs (curl/Postman, auth flows, schemas, error handling).

  • Experience documenting complex systems such as API auth, deployments, data pipelines, or ML/AI platforms.

  • Proven ability to operate independently in a small, fast-moving team and drive docs from ambiguity to shipped output.

Preferred / Nice-to-Have Skills

  • Prior experience documenting ML platforms, developer tooling, edge/IoT systems, or “systems that touch the physical world.”

  • Experience setting up doc testing automation (link checking, build verification, example execution) or content linting.

  • Open-source docs contributions or developer community content.