About The Position

This role involves serving as the Editor-in-Chief for the Satellite Operations Handbook. The primary responsibility is to gather documentation and inputs from various subsystem teams, such as power, thermal, AOCS, TT&C;, payload, FDIR, and the ground segment. These inputs will be integrated into a single, coherent, and fluid text. The Technical Writer will interview subsystem engineers to identify and resolve any gaps or ambiguities, and to verify the technical accuracy of all sections. The role requires rewriting engineering source material into clear, unambiguous, procedure-grade language suitable for operators during real-time operations. The handbook will be structured across the mission lifecycle, including nominal operations, contingency and FDIR response, and subsystem reference sections. Additionally, the Technical Writer will be responsible for maintaining revision and configuration control, organizing and running formal review cycles with engineering and operations stakeholders, and establishing and enforcing a style guide, templates, and terminology consistency among all contributors.

Requirements

  • Proven long-form technical authorship — a PhD thesis, published research, or prior authorship of operations manuals, handbooks, flight rules, or procedures.
  • Working knowledge of satellites and space systems — able to read, understand, and interrogate subsystem engineering documentation.
  • Fast learner with a synthetic mind: able to compress many inconsistent sources into one clear narrative.
  • Excellent written English.

Nice To Haves

  • Background in satellite operations, spacecraft systems engineering, or mission analysis.
  • French language skills (Montreal-based team).
  • Familiarity with documentation and requirements tools (DOORS, Confluence) and ECSS/NASA documentation culture.
  • Experience authoring training materials or certifying operations personnel.

Responsibilities

  • Act as editor-in-chief of the Satellite Operations Handbook: gather documentation and inputs from subsystem teams (power, thermal, AOCS, TT&C;, payload, FDIR, ground segment) and integrate them into one coherent, fluid text.
  • Interview subsystem engineers to close gaps, resolve ambiguities, and verify the technical accuracy of every section.
  • Rewrite engineering source material into clear, unambiguous, procedure-grade language suitable for use by operators in real-time operations.
  • Structure the handbook across the mission lifecycle: nominal operations, contingency and FDIR response, and subsystem reference sections.
  • Maintain revision and configuration control; organize and run formal review cycles with engineering and operations stakeholders.
  • Establish and enforce a style guide, templates, and terminology consistency across all contributors.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service