zaimler is hiring: Technical Writer in San Mateo

About zaimler AI agents can't reason over data they don't understand. Enterprise data today is fragmented across dozens of systems with no shared context, meaning, or structure, and that's why most enterprise AI is failing. The shift from copilots to autonomous agents is creating an entirely new infrastructure layer, and we're building it. zaimler is the context infrastructure for the agentic era: a platform that automatically discovers domain knowledge, maps relationships, and gives AI agents the semantic understanding to operate with precision at scale. Imagine knowledge graphs that support real-time inference, built for systems that need to reason, not just retrieve. zaimler was founded by Biswajit Das (ex-VP Engineering, Truera), a Data Infra veteran and former Chief Architect at Visa, and Sofus Macskassy (ex-Director of Engineering, LinkedIn), who built one of the largest knowledge graphs in production in the industry at LinkedIn. We're a small, senior team at the seed stage, deploying with major enterprises across insurance, travel, and technology. If you want to build infrastructure that the next decade of AI runs on, we'd love to talk. The Role You'll be zaimler's first technical writer. That means you won't just write docs, you'll decide what the docs strategy looks like, what tooling to use, and how documentation fits into the product and customer experience from day one. Our platform sits at the intersection of knowledge graphs, data infrastructure, and AI agents, and the people using it are senior engineers and data teams at large enterprises. They need documentation that is precise, trustworthy, and written by someone who actually understands the systems behind it. This role touches everything: API references, SDK guides, platform architecture docs, customer onboarding materials, integration guides, and internal engineering documentation. You'll work directly with engineering, product, and GTM to make zaimler's technology accessible and self-serve. What You'll Do Own and build zaimler's documentation from the ground up: define the information architecture, select tooling (docs-as-code, CMS, or otherwise), and establish style and quality standards Write and maintain API references, SDK guides, quickstarts, and platform documentation for a technical audience of engineers and data teams Create customer-facing content including implementation guides, solution briefs, and onboarding materials that accelerate enterprise deployments Develop internal documentation such as architecture decision records, runbooks, and engineering onboarding guides Embed with engineering teams to document new features and platform capabilities as they ship, not after Establish a feedback loop with customers and internal teams to identify gaps, improve clarity, and prioritize what to document next Must-haves 5+ years of experience in technical writing, with a focus on developer-facing documentation for infrastructure, data, or platform products A portfolio that demonstrates clear, precise writing for technical audiences (API docs, architecture guides, developer tutorials) Ability to read code and engage directly with engineers about system design, APIs, and data models. You don't need to be a software engineer, but you need to be technically fluent. Experience building documentation programs or information architecture from scratch, not just contributing to existing doc sets Familiarity with docs-as-code workflows (Markdown, Git, static site generators like Docusaurus, MkDocs, or similar) Strong editorial judgment: you know when to write a quickstart vs. a conceptual guide vs. a reference page, and you can make that call without being told Nice-to-haves Experience documenting knowledge graphs, graph databases, semantic layers, or ML/AI systems Background writing for enterprise audiences where accuracy and trust are critical (financial services, healthcare, infrastructure) Experience with developer relations, content strategy, or technical marketing Familiarity with API documentation tools (Swagger/OpenAPI, Redoc, Stoplight) Working style You're comfortable being the only writer in the room and owning the full docs lifecycle You proactively seek out what needs documenting rather than waiting for a ticket You care about the reader's experience as much as technical accuracy We value builders over résumés. If this role excites you but you don't check every box, we still want to hear from you. zaimler is an equal opportunity employer. #J-18808-Ljbffr In Summary: zaimler is the context infrastructure for the agentic era . It's a platform that automatically discovers domain knowledge, maps relationships and gives AI agents the semantic understanding to operate with precision at scale . The role touches everything: API references, SDK guides, platform architecture docs, customer onboarding materials, integration guides, and internal engineering documentation . En Español: Zaimler es la infraestructura de contexto para la era agencial: una plataforma que descubre automáticamente el conocimiento del dominio, mapea las relaciones y le da a los agentes de inteligencia artificial la comprensión semántica para operar con precisión en escala. Imagina gráficos de conocimientos que soportan la inferencia en tiempo real, construidos para sistemas que necesitan razonar, no solo recuperar. zaimler Das fue fundada por Biswajit (ex-VP Data Engineering, Truera), un veterano e arquitecto jefe de infraestructuras de Visa, y Sofus Macskas (un producto de Roxas-Dex of Engineering), que hace uso automático de la mayor parte de las empresas de ingeniería tecnológica. Nuestra plataforma se encuentra en la intersección de gráficos del conocimiento, infraestructura de datos y agentes de IA, y las personas que lo utilizan son ingenieros senior y equipos de datos de grandes empresas. Necesitan documentación precisa, confiable y escrita por alguien que realmente entienda los sistemas detrás de ella. Este papel toca todo: referencias API, guías SDK, documentos sobre arquitectura de plataformas, materiales para incorporación de clientes, guias de integración y documentación de ingeniería interna. Trabajará directamente con la ingeniería, el producto y GTM para hacer que la tecnología de zaimler sea accesible e autosuficiente. Lo que hará Poseer y construir la documentación de Zaimler desde cero: definir la arquitectura de información, seleccionar herramientas (documentos como código, CMS o lo contrario), y establecer estándares de estilo y calidad Escribir y mantener referencias API, guías SDK, arranques rápidos y documentación plataforma para una audiencia técnica de ingenieros y equipos de datos Crear contenido orientado al cliente incluidas guías de implementación, breves de soluciones y materiales de incorporación que aceleren las implementaciones empresariales Desarrollar documentación interna como registros de decisiones de arquitectura, cuadernos de ejecución y guías integradoras de ingeniería establecidas con los equipos de ingenieria para documentar nuevas características y capacidades de la plataforma a medida que avanzan, no después de Establecer una guía de retroalimentación con equipos de desarrolladores de APIs enfocarse en qué brechas internas se encuentran, dar prioridad a la claridad de datos, identificar y mejorar la capacidad de diseño técnico del sistema AAPI, crear modelos de desarrollo de productos y tutoriales directos para los clientes, escribir un portafolio de proyectos técnicos sobre sistemas de construcción de infraestructuras, diseños de software, maquetas, etc. No necesita ser un ingeniero de software, pero tiene que ser técnicamente fluido. Experiencia en la construcción de programas de documentación o arquitectura de información desde cero, no solo contribuyendo a conjuntos de documentos existentes Familiarización con los flujos de trabajo doc-as-code (Markdown, Git, generadores de sitios estáticos como Docusaurus, MkDocs, u similares) Fuerte juicio editorial: sabe cuándo escribir una guía rápida frente a una página de referencia conceptual, y puede hacer esa llamada sin decirle Niza-a-Have experiencia documentando gráficos de conocimiento, bases de datos gráficas, capas semánticas, o sistemas ML/AI Escribir antecedentes para audiencias empresariales donde la precisión y confianza son críticas (servicios financieros, infraestructura sanitaria, etc.)