• WHAT WE NEED YOU TO BRING TO THE TABLE:Developer empathy. You approach and write docs to increase an integrating engineer’s efficiency. You can produce clear, accurate content, not just tooling around it
• You can write code without AI as a crutch. You write scripts, debug error output, and ship working solutions independently
• Comfort with JavaScript/TypeScript. Our tooling uses it throughout
• Fluency with CI/CD pipelines
• Experience working with or reading OpenAPI 3.x specifications
• Clear understanding of what makes documentation machine-readable, not only human-readable
• Practical experience with AI tools, especially Claude. You use them daily and know how to prompt for useful output
• A preference for correctness over volume. You know when to automate and when automation produces noise
• 
  

You bring most of the following:

• A degree or vocational qualification in technical communication, aerospace, mechanical or electrical engineering, or a comparable field. Part 66 license holders with documentation experience are also welcome.
• Experience in technical writing, technical authoring or technical documentation, ideally for complex products.
• Aviation experience is a strong plus, but not a must. We will support you in growing into the regulatory environment (CS-23, Part 21, Part 145).
• Familiarity with one or more of the following is an advantage: S1000D, ATA iSpec 2200, ASD-STE100 (Simplified Technical English), DITA, editorial / CCMS systems (e.g. Schema ST4, Arbortext, Cortona3D), Adobe FrameMaker, CAD viewers.
• Structured, accurate working style and the ability to explain complex topics clearly.
• Good English skills (working language for technical publications). German is a strong plus; if you don't speak it yet, we will support you in learning.