Robotics Technical Writer (1 year contract)

BeeX is building the world's most advanced Hovering Autonomous Underwater Vehicles (HAUVs).

BeeX specialises in providing autonomous robotics solutions to safeguard underwater infrastructure in the maritime, energy and defense sectors, reducing over 90% of carbon emissions. We are pioneering Autonomous Robotics-as-a-Service (ARaaS) on a global scale, supported by decades of operational experiences in harsh waters. With unprecedented efficiency, we strive to provide our customers with a one-point solution for asset integrity management -- protecting assets they value, making sure they stay safe.

We are currently preparing to launch a new underwater vehicle. We need an experienced technical writer to create the end-user manual and training materials that will ship with the product and support our customer onboarding and internal support teams.

You'll work directly with our engineering and operations team to translate technical specs, product functionality and dive workflow into clear, accurate, easy-to-follow documentation for operators on the customers’ teams. This is not a transcription role: you will own the documentation set end to end, from deciding how it should be structured, to validating that a real operator can follow it in the field.

• Structure it for the operator. Design the information architecture across the full document set (manual, quick start guide, checklists, training), organised around how operators actually work (e.g. mission planning, pre-dive, launch, dive, recovery, post-dive) rather than how the vehicle is engineered.

• Understand the user first. Shadow workshop and field operations, interview operators and SMEs, and identify where first-time users get stuck, before and while writing.

• Propose, don’t just follow. Recommend the document hierarchy, navigation, formats and media (text, diagrams, photos, video, checklists) best suited to each task, and push back on content that doesn’t serve the operator.

• Set the standards. Define templates, terminology, and a consistent convention for warnings, cautions and notes that engineering and future writers can reuse.

• Validate usability. Run walkthroughs with a first-time operator and our ops team, and revise based on where they hesitate or make mistakes.

• Leave it maintainable. Set up version control and a simple update process so documentation can keep pace with hardware and software revisions after handover.

The contents listed below are indicative. The final structure, sequencing and format of each deliverable will be proposed by you and agreed with us at the start of the engagement.

1. Documentation Architecture & Outline

• Proposed structure and navigation across all deliverables, based on operator workflow and user interviews

• Style sheet: terminology, templates, and warning/caution/note conventions

• Reviewed and agreed with BeeX before full drafting begins

• Product overview and specifications

• Safety warnings and precautions

• Unboxing and what's in the box

• Setup and assembly instructions

• Charging and battery care

• Operation: powering on/off, controls, diving procedures

• Maintenance, cleaning, and storage

• Troubleshooting / FAQ

• Warranty and compliance information

3. Quick Start Guide

• Condensed 1–2 page version for in-box printing

4. Training Materials

• Slide deck with videos as needed

• For new operators from customers, distributors, and internal teams

5. Pre-Dive / Post-Dive Safety Checklist

• Short-form operational checklist for safe use

• Engineering specifications and CAD renders

• Existing internal notes/drafts

• Access to a subject matter expert (SME) on our team for questions/interviews

• Access to the product in workshop and field scenarios to obtain product photos and video footage

• Brand style guide

• Proven experience writing user manuals or instructional guides for physical/hardware products (consumer electronics, marine, robotics, or similar preferred)

• Ability to translate technical/engineering input into clear, non-technical language

• Demonstrated ownership of a documentation set end to end, including defining its structure, information architecture and standards, not only writing to a given outline

• Strong user-centred mindset: experience observing or testing with end users and restructuring content based on how it is actually used

• Strong portfolio of similar work (please share samples)

• Comfortable working from source material and interviewing SMEs directly

• Experience with [Word / Google Docs / InDesign / Figma — specify tools]

• Background in marine robotics, ROV, drone, or outdoor/adventure gear documentation

• Instructional design or e-learning experience

• Familiarity with task-based / minimalist documentation approaches (e.g. DITA, Simplified Technical English) and safety-message conventions (e.g. ANSI Z535.6, ISO 3864)

• 2–3 samples of user manuals or technical documentation you've written (hardware products preferred)

• Your estimated timeline and rate for a project of this scope

• Any relevant experience with marine, robotics, or outdoor hardware products

• A short outline (half a page is fine) of how you would approach structuring the documentation for a field operator of an underwater vehicle