S&S Technical Writer

We need to output HTML fragment with sections: About the role? The posting includes Job Description, Meet The Team, Your Working Environment, How We Care For You (benefits), Your Challenges (responsibilities), Additional Responsibilities, Education, Experience, Licensure/Certifications, Travel Required, Citizenship, Clearance, Qualified Skills, etc. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID. Remove boilerplate (EEO, accommodations, notices). Keep substantive info. We need sections only if content present. Let's extract: About the role: Could be Job Description paragraph: "The Support & Services (S&S) Technical Writer is responsible for creating, editing, and maintaining technical documentation, including manufacturing work instructions, user manuals, software guides, system specifications, and other forms of technical content. This role involves working closely with subject matter experts (SMEs), engineers, manufacturing, and product teams to gather information and ensure documentation is accurate, clear, and accessible for the target audience." Also Meet The Team: description of Flexrotor Program. Your Working Environment: description of location. These could be part of About the role? Might be separate sections but allowed headings limited. We can combine into About the role. Responsibilities: Your Challenges section lists Technical Writing 50%, Project Management 30%, Technical & Operational Integration 20%, Additional Responsibilities. We can put those under Responsibilities. Requirements: Education, Experience, Licensure/Certifications, Travel Required, Citizenship, Clearance. Qualifications maybe similar to Requirements? But we can treat Requirements as education/experience etc. Qualifications maybe skills? Actually we have Skills section: Qualified Skills (Knowledge, Skills, Demonstrated Capabilities) includes required and preferred. We can map Skills to Skills heading. Benefits: How We Care For You includes Financial Rewards, Work/Life Balance, Health & Welfare. Pay: Not explicitly given; only "Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan and the ability to participate in an Employee Stock Ownership Plan (“ESOP”)" That's compensation details, could be considered Pay. The rule: only create Pay section if posting actually states them. It does state competitive base salary etc. So we can include Pay. Schedule: Not given; maybe not. Travel Required is 10% Domestic and International, but that's not schedule. No explicit schedule like full-time, part-time. So we omit Schedule. We must not include placeholder like "N/A". For Licensure/Certifications Required N/A Preferred N/A - we should omit that section because it's just N/A. So we can drop Licensure/Certifications. We need to preserve all substantive info; we can include Travel Required under Requirements maybe as a bullet. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title. No markdown. Let's craft:

  About the role

  The Support & Services (S&S) Technical Writer is responsible for creating, editing, and maintaining technical documentation, including manufacturing work instructions, user manuals, software guides, system specifications, and other forms of technical content. This role involves working closely with subject matter experts (SMEs), engineers, manufacturing, and product teams to gather information and ensure documentation is accurate, clear, and accessible for the target audience.

  The Airbus Helicopters Flexrotor Program offers one of the most sophisticated small tactical unmanned aerial systems (STUAS) with vertical take-off and landing (VTOL). It can be used day or night by US and allied forces for a diverse range of intelligence, surveillance, target acquisition and reconnaissance (ISTAR) on land and at sea.

  Nestled in the heart of the spectacular Columbia River Gorge in Bingen, WA, our workplace offers innovation and the ability to contribute to game-changing solutions while enjoying the flexibility to spread your wings. Whether it's solving complex challenges, or celebrating victories, you’ll be part of a cohesive crew that thrives on innovation and the beauty that the Northwest has to offer!

  Responsibilities

  • Technical Writing (50%): Develop clear, accurate, and user-friendly work instructions and external customer-specific documentation including operations and maintenance manuals for the Flexrotor Unmanned Aircraft System (UAS). Write and edit technical documents such as operations and maintenance field manuals, manufacturing work instructions, and system documentation. Collaborate with engineers, developers, training, and product teams to gather technical information and clarify requirements. Organize and manage content in a consistent, easy-to-follow structure and format in accordance with aerospace writing standards. Contribute to cross-functional projects to provide feedback on the usability of products based on user documentation.
  • Project Management and customer documentation (30%): Lead cross-functional teams, including subject matter experts (SMEs), instructors, contractors, and stakeholders, to gather input and validate course content. Execute multiple projects simultaneously driven by business needs. Define deadlines and deliverables, track and report appropriately to ensure timely completion of high-quality documentation. Maintain customer documentation up to date (Service Bulletin, Operator manual, Software manual, Maintenance manual).
  • Technical & Operational Integration (20%): Collaborate with engineering and technical teams to stay updated on the latest Flexrotor UAS technologies and operational procedures. Develop documentation structure and ways of working for both manufacturing and operation of the aircraft in tandem. Translate complex technical data and operational tactics into accessible documentation materials for diverse audiences. Work with technical communications, content management systems (CMS), unmanned aerial systems, and military or aviation operations to guarantee technical documents are comprehensive, current, and aligned with both regulatory standards and operational requirements.
  • Additional Responsibilities: Other duties as assigned.

  Requirements

  • Education: Required Bachelor’s degree in Technical Communication, English, Journalism, Aerospace or equivalent experience. Preferred Master’s degree in Technical Communication, English, Journalism, Aerospace or equivalent experience.
  • Experience: Required Minimum 5 years of hands-on experience in technical writing. Ability to explain complex technical information clearly and concisely, creating manufacturing documentation and/or operational manuals such as user manuals, software documentation, system specifications, API documentation. Preferred Experience within unmanned aerial systems.
  • Travel: 10% Domestic and International.
  • Citizenship: Authorized to work in the US, able to work in US without current or future need for visa sponsorship.
  • Clearance: None.

  Skills

  • Required: Strong proficiency in writing and editing technical content. Excellent project management skills, with the ability to manage complex projects and meet deadlines. Exceptional analytical and problem-solving abilities, with keen attention to detail. Ability to work collaboratively with diverse teams and adapt to evolving project requirements. Experience with Simplified Technical English (STE) or similar. Ability to navigate and drive deliverables in sometimes unclear working environments. Keen awareness for detail. Communication Skills: Ability to communicate effectively in verbal and written form in English. Ability to explain complex technical concepts in a simple and user-friendly manner. Outstanding written and verbal communication skills, with the ability to convey complex information clearly and concisely. Technical Systems Proficiency: Experience with content management systems (CMS) like Madcap Flare, Heretto, Paligo, or Adobe FrameMaker. Knowledge of FAA regulations and standards related to UAS operations and training.
  • Preferred: Experience developing technical content for unmanned aerial systems or related aviation fields. Experience with HTML/XML or other markup languages.

  Benefits

  • Financial Rewards: Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan and the ability to participate in an Employee Stock Ownership Plan (“ESOP”).
  • Work/Life Balance: Paid time off including personal time, holidays and a generous paid parental leave program.
  • Health & Welfare: Comprehensive insurance coverage including medical (traditional and high-deductible health plans), prescription, dental, vision, life, disability, Employee Assistance Plan (“EAP”) and other supplemental benefit coverages.

  Pay

  Competitive base salary, incentive compensation which may include profit sharing schemes, retirement savings plan and the ability to participate in an Employee Stock Ownership Plan (“ESOP”).

  We have duplicated Pay content also in Benefits; but we can keep both as they are distinct sections. However rule: do not repeat content? Not explicitly prohibited but we should avoid duplication. The Pay section could be omitted because it's already covered in Benefits Financial Rewards. But the rule says include Pay section only if posting actually states them. It does state competitive base salary etc. However we already have that in Benefits. To avoid duplication, we could keep Pay section brief referencing same info, but that repeats. Better to omit Pay section and rely on Benefits for compensation. However the instruction: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay may be thin. Since Pay is essentially same as Financial Rewards, we could omit Pay and keep Benefits. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, but we already have Benefits. It's okay to have Benefits only. Pay is not required if we already captured in Benefits. I'd drop Pay section to avoid duplication. Thus final sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check we didn't miss any substantive info: "Complexity of the Role", "Level Of Decision Making", "Impact of Decisions", "Job Dimensions", "Nature Of Contacts", "Level of Influence", "Frequency of Communications", "Physical Requirements". Those are substantive details about the role; they could be included under About the role or Responsibilities? They describe the role's complexity, decision making, impact, dimensions, contacts, influence, frequency, physical requirements. They are important. We should incorporate them somewhere, maybe under About the role as additional paragraphs, or under Responsibilities? They are not duties but role characteristics. Could be part of About the role. We need to preserve ALL substantive information. So we must include those details. Let's extract them: Complexity of the Role: This role will sometimes be undefined, requiring high levels of self-motivation. The successful person will in some cases have to motivate teams to use processes and documentation that are not yet mature, gather feedback and then update and adapt accordingly. The decisions being made will help to streamline and standardize the way of working in the operations and manufacturing system on the Flexrotor program. Level Of Decision Making: Strategic Decisions: Defines the target audience for the technical documentation including end-users, system administrators, developers, and internal teams. Influences documentation delivery methods and how they will impact the accessibility and impact on the end-user. Defines the applicable level of detail that is to be included in the documentation and how detailed a document should be depending on various user groups. Understanding when and how to act on user feedback to ensure that the documentation evolves in a way that meets users’ changing needs. Prioritize collaboration with cross-functional teams to ensure technical accuracy. Tactical Decisions: Develops and refines technical documentation. Prioritizing documentation based on product importance, user feedback, or release schedules to ensure that the most relevant and needed content is created and made available to users in a timely manner. Ensuring that the documentation is accessible in different languages through localization solutions. Balances competing priorities to ensure timely updates and continuous improvement of technical documentation. Operational Decisions: Manages day-to-day documentation updates, ensuring accuracy, relevance, and compliance with FAA, DoD, and other regulatory standards. Resolves issues related to documentation effectiveness