Technical Writer

Make Orcher’s architecture, controls and evidence understandable to the engineers, security reviewers and operators who must trust it. Enterprise infrastructure is judged through its documentation long before it is trusted in production. For Orcher, words such as identity, verification, evidence, boundary and control must describe exact system behavior—not aspirations. You will own the technical record across product documentation, architecture explanations, control descriptions, deployment guides, API references and evidence-package guidance. You will work from code, design documents, demonstrations and interviews with engineers, then test every explanation against what the system can substantiate. The audience ranges from an engineer integrating a system of record to a security architect evaluating process boundaries and an executive asking what can be proven after an action commits. Your work should let each reader answer the next important question without marketing overstatement or hidden ambiguity. What you will do

Build and maintain the documentation architecture for Orcher and its seven components Write precise explanations of directive identity, runtime verification, data boundaries, cost controls, observability and immutable evidence Create deployment guides, integration tutorials, API examples, troubleshooting paths and evidence-export guidance Interview engineers and inspect product behavior so documentation reflects the shipped system Develop claim-review and release-documentation practices that keep public material synchronized with product changes Edit research and customer-facing technical material for accuracy, structure and useful qualification Identify product friction through documentation work and advocate for clearer interfaces and defaults

What we look for

Exceptional technical writing with a portfolio covering infrastructure, security, data or developer products Ability to read code, APIs, architecture diagrams and technical design documents independently Discipline about the difference between a control, a signal, a claim and evidence Skill adapting one technical truth for engineering, security, audit and executive audiences Strong interviewing, information architecture and editorial judgment

Experience

4+ years in technical writing, documentation engineering, security content or a closely related role Owned a documentation set or major technical publication from source investigation through release Experience with docs-as-code, API documentation and enterprise security review material

Education

Degree in a technical, scientific, communications or writing discipline, or an equivalent portfolio of rigorous work A portfolio of published technical or compliance writing is accepted in place of a degree.

Compensation and benefits

Equity with a standard four-year vest and early-stage upside Health, dental and vision coverage Research, books and professional-development budget Company-provided hardware Direct access to the engineers and founding team shaping the product 401(k) with company contribution and an annual learning budget.
#J-18808-Ljbffr