Technical Content Engineer

Summary

At Claris, clear technical information helps customers turn ideas into working solutions. We're looking for a Technical Content Engineer who brings the practical skills of a software developer to our documentation team, and who will grow into the judgment of an excellent technical writer with support from our editorial team. You'll build and maintain the tools, pipelines, and workflows that make our documentation team faster and more accurate — and you'll author customer-facing content directly as you develop that expertise. This role combines hands-on engineering and automation with technical writing, docs-as-code practices, and thoughtful use of AI.

Minimum Qualifications

3 years of professional experience building and maintaining production software: scripts, integrations, or services in Python, JavaScript/TypeScript, or a comparable language. Experience with Git-based collaborative development, code review, and implementing or debugging CI/CD workflows. Ability to write automated tests, diagnose failures, and explain the maintenance tradeoffs of your own code. Practical experience integrating AI/LLM-based tools into a repeatable workflow, with a way of evaluating output quality and handling failure. Strong written and verbal communication skills, and genuine interest in developing technical-writing craft with team mentorship. Ability to investigate unfamiliar technical behavior, collaborate effectively with engineers and writers, and independently deliver a well-scoped project.

Preferred Qualifications

Experience with docs-as-code environments, static site generators, or CCMS/help-authoring tools. Experience with API documentation, schema-driven reference generation, or automated example/code testing. Experience building or maintaining a search/retrieval system, embeddings pipeline, or MCP-style integration. Prior technical-writing experience or coursework, even if not professional. Familiarity with FileMaker.

Description

You'll work within Documentation & Localization and partner closely with engineering, product, and our team of experienced technical writers. The engineering work is central to this role: you'll design, build, test, and maintain the software systems — CI/CD pipelines, validation tooling, AI-assisted workflows, and integrations — that let our documentation keep pace with a fast-changing product. Alongside that, you'll author and maintain customer-facing documentation in assigned areas as you build your technical-writing craft. The role is designed around an intended long-term balance of approximately 50% engineering and 50% technical content, reviewed across a quarter rather than enforced week to week. In your first year, expect the split to lean more heavily toward engineering while you build out core systems and ramp up on writing craft in parallel.

Responsibilities

ENGINEERING & AUTOMATION: Build, test, and maintain scripts, integrations, and tools that reduce repeated manual work across the documentation lifecycle. Own and evolve our CI/CD pipeline (git-based review, build, validation, and publishing to the Claris Help Center). Develop and maintain automated checks — link validation, terminology, structure, and drift between documented behavior and actual product/codebase. Design, integrate, and evaluate AI-assisted and agentic workflows (e.g., drafting support, semantic search, retrieval) with clear inputs, review controls, and failure handling. Maintain the search/retrieval backend and corpus pipeline that power AI-assisted content discovery; monitor reliability, freshness, and answer accuracy. Document your tools' setup, dependencies, and recovery steps so ownership isn't a single point of failure. TECHNICAL CONTENT Author and maintain customer-facing help, guides, and reference material for assigned product areas, with editorial support and review from senior writers. Validate technical accuracy through product use, API/script exploration, and collaboration with engineers. Partner with writers to improve templates, metadata, and contribution workflows as the docs-as-code environment matures.