Quick overview
Job description
Telesat (Nasdaq and TSX: TSAT) is a leading global satellite operator, providing reliable and secure satellite-delivered communications solutions worldwide to broadcast, telecommunications, corporate and government customers for over 55 years. Backed by a legacy of engineering excellence, reliability and industry-leading customer service, Telesat has grown to be one of the largest and most successful global satellite operators.
Telesat Lightspeed, our revolutionary Low Earth Orbit (LEO) satellite network, scheduled to begin service in 2027, will revolutionize global broadband connectivity for enterprise and Government users by delivering a combination of high capacity, security, resiliency and affordability with ultra-low latency and fiber-like speeds. Telesat is headquartered in Ottawa, Canada, and has offices and facilities around the world.
The company’s state-of-the-art Satellite fleet consists of 12 GEO satellites, the Canadian payload on ViaSat-1 and one LEO 3 demonstration satellite. For more information, follow Telesat on X and LinkedIn or visit www.telesat.com
The Senior Technical Writer is responsible for developing, maintaining, and improving Engineering Design Documentation across the Lightspeed program. This role serves as the central documentation authority for component-level architecture and design knowledge, ensuring that engineering teams have access to accurate, consistent, and maintainable technical documentation.
The role supports the development of both High Level Design (HLD) and Detailed Design Description (DDD) documentation for key Engineering Segment components including:
-
On-Board Processor Software System
-
User Terminals (UTs) Systems
-
LS LS-BB and ACU Systems
-
System Operations
-
Future Engineering Segment components as required.
The successful candidate works closely with System Architects, Software Architects, Subject Matter Experts (SMEs), Developers, Integration Teams, and Product Owners to transform existing engineering knowledge into structured, maintainable design documentation.
The documentation produced complements existing:
-
Product Requirement Documents (PRDs)
-
Interface Control Documents (ICDs)
-
Technical Requirement Documents (TRDs)
-
Architecture Reviews
-
Confluence content
-
Implementation repositories
-
Capella (MBSE) content
and acts as the authoritative engineering knowledge repository for internal engineering teams.
Key Responsibilities
-
Develop and maintain High Level Design (HLD) documents.
-
Develop and maintain Detailed Design Description (DDD) documents.
-
Create subsystem and component architecture descriptions.
-
Develop logical, functional, and physical architecture views.
-
Capture design rationale and architectural decisions.
-
Work with SMEs to extract undocumented knowledge.
-
Work with SMEs to retire/archive stale documents.
-
Analyze implementation artifacts and source code.
-
Convert engineering discussions into technical documentation.
-
Create and maintain engineering diagrams and models.
-
Ensure documentation remains synchronized with implementation evolution.
-
System context diagrams
-
Functional decomposition diagrams
-
Sequence diagrams
-
State machines
-
Activity diagrams
-
Deployment diagrams
-
Interface diagrams
-
Data flow diagrams
-
Capella/UML component diagrams
-
Capella/UML class diagrams where appropriate
-
Timing and lifecycle diagrams
-
Define documentation standards and conventions.
-
Establish reusable templates.
-
Maintain version control of documentation.
-
Support architecture reviews and design reviews.
-
Ensure traceability between requirements, architecture, interfaces, and implementation.
-
Establish engineering knowledge repositories.
-
Improve discoverability of architectural information.
-
Consolidate information from:
-
Confluence
-
Git repositories
-
Architecture reviews
-
Design reviews
-
ICDs
-
Existing design documentation
-
Drive documentation quality across Engineering segments.
Architecture Documentation Development
Technical Content Development
Modeling and Diagram Development
Produce and maintain:
Documentation Governance
Knowledge Management
Required Qualifications
-
Degree in Engineering, Computer Science, Software Engineering, Telecommunications, or equivalent experience.
-
8+ years technical writing experience.
-
5+ years supporting software-intensive or network-intensive systems.
-
Experience documenting distributed systems.
-
Experience working directly with architects and engineering teams.
-
Telecommunications systems
-
Satellite communications systems
-
Cloud-native systems
-
Embedded software
-
Control systems
-
Network management systems
-
UML
-
SysML
-
Sequence diagrams
-
State machines
-
API documentation
-
Software architecture principles
-
CI/CD concepts
-
Software lifecycle management
-
Confluence
-
Jira
-
GitLab / GitHub
-
Markdown
-
Draw.io
-
Visio
-
Lucidchart
-
Enterprise Architect
-
PlantUML
-
Capella
Education
Experience
Technical Skills
Experience producing documentation for:
Strong working knowledge of:
Tools
Experience with:
Success Metrics
-
Coverage of Engineering Segment components documented
-
Documentation currency with implementation
-
Reduction in SME dependency for system knowledge
-
Documentation quality review results
-
Improved onboarding efficiency
-
Engineering team adoption of HLD/DDD documentation
The role will be measured on:
The successful candidate must be able to work in Canada and obtain clearance under the Canadian Controlled Goods program (CGP).
Haystack's AI agent can fill in and submit this application for you. How AI auto apply works
Will your resume get past this employer's screening? Check your resume against this job, free
