Technical Publications Analyst

We need to output HTML fragment with sections: h3 headings for sections present. We need to include only sections with real content. The posting includes Position Summary (maybe we treat as About the role?), Essential Duties and Responsibilities (Responsibilities), Minimum Qualifications, Skills, Education And Experience (Qualifications/Skills), Preferred Qualifications And Skills (maybe also Qualifications), Supervisory Responsibilities (None) - we should not include if content is just "None" (placeholder). Language Skills (maybe Skills). Physical Activities And Requirements (maybe Schedule? Not exactly; but it's about physical requirements; we could treat as maybe "Physical Requirements" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to these headings. The posting does not mention Benefits, Pay, Schedule. So we should not include those sections. We can include About the role (position summary). Responsibilities (essential duties). Qualifications (minimum qualifications). Skills (maybe separate but could combine). The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills. We can include About the role, Responsibilities, Qualifications, Skills. Requirements maybe same as Qualifications? But we can include Qualifications and Skills separate. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal notices, acknowledgment, etc. Also remove "Supervisory Responsibilities None" (since it's placeholder). Language Skills maybe part of Skills. Physical Activities maybe not needed. We need to preserve all substantive information. So we need to include all duties, qualifications, skills, preferred qualifications, etc. We'll put them under appropriate sections. We need to use

for section headings. Use

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

  for prose. We need to decide how to structure: For About the role: a paragraph summarizing position summary. For Responsibilities: list each duty as

• . For Qualifications: maybe list minimum qualifications as
• . For Skills: list skills as
• . Preferred qualifications could be under Qualifications or Skills? Could add another section "Preferred Qualifications" but not in allowed headings. We could incorporate preferred qualifications into Qualifications section as additional bullet points, maybe label as "Preferred". But we must not invent headings not allowed. So we can put preferred qualifications under Qualifications as bullet points with note "Preferred". Or we could create a separate section "Qualifications" and include both minimum and preferred. That's acceptable. We must not include sections with filler like "commensurate with experience". Not present. We need to ensure we don't include any boilerplate like "Acknowledgment", "EEO Statement", "Legal Notices". Remove them. Now craft HTML. Let's extract duties: - Issues and tracks revisions to all company-controlled manuals assigned to aircraft. - Maintains and updates manuals status reports for Maintenance and Flight Operations Department, and aircraft audit lists for crew use. - Organizes and maintains company’s manuals servers with all master manuals. This includes company-generated and manufacturer-issued documents. - Responsible for auditing manufacturer-provided data for currency and completeness. - Assists in ordering company controlled materials as needed. - Maintains and updates Tech Pubs open action items in the Safety Management database. - Ensures all manual revision requests are supported by approved Manual Change Request forms. - Responsible for contacting manufacturers to ensure that their contact information is correct, that they are still responsible for STCs listed, and that we have access to related documentation. - Provides assistance to operations/maintenance personnel, flight crews, vendors and other employees to ensure they are able to access manuals via company manuals servers and company-issued iPads. - Works with Technical Publications staff to create, circulate and issue revisions to company manuals as needed. - Works with Technical Publications to create company forms and SOP documents as needed. - Works with Technical Publications and Engineering to create and revise task cards as needed. - Responsible for managing tasks associated with iPad program for both Maintenance and Flight Operations. Now qualifications (minimum): - High skill and comfort level with common office software, including MS Office and Adobe Acrobat - Willing and able to develop proficiency in new software titles and data systems - Strong ability to work under pressure - Adaptable to new projects and tasks - Excellent verbal and written communication skills - Able to work well with others and work together to accomplish various projects - Excellent organization skills - Types at least 45-50 wpm - Possesses good research skills - Fluent/proficient spoken and written English, and other office skills. Preferred qualifications: - Previous technical aviation knowledge - Framemaker skills (structured or unstructured) preferred but not required - Previous technical writing experience - Bachelor’s degree or higher in English, Communications, Technical Writing or other related area of study. Language skills: strong interpersonal and communications skills, ability to present information, clear responses, write reports, procedures, business correspondence. Could be part of Skills. Physical activities: sedentary work, sitting most of the time, office environment, standard office equipment, exerts up to 30 lbs occasionally. This could be under maybe "Physical Requirements" but not allowed heading; we could omit? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include physical activities somewhere. Since we don't have a heading for it, we could include it under a generic section like "About the role" or maybe under "Skills"? But it's not a skill. Could we create a section "Requirements"? That heading is allowed. Requirements could include physical requirements. So we can use

  Requirements

  and list physical activities and maybe language skills there. However we also have Skills heading allowed. We could split: Requirements for physical and language, Skills for technical/software skills. But we also have Qualifications heading for education/experience. Let's think. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use: - About the role: position summary paragraph. - Responsibilities: list of duties. - Requirements: physical activities and language skills (maybe also minimum qualifications? but we have Qualifications for education/experience). We'll put physical activities and language skills under Requirements. - Qualifications: minimum qualifications (education, experience, software proficiency, etc.) plus preferred qualifications? Could include both. - Skills: maybe technical skills like MS Office, Adobe Acrobat, typing speed, research, etc. But we already have those in Qualifications. Might be overlapping. Better to separate: Qualifications for education/experience, Skills for technical/software and soft skills. However the posting lumps many together. We need to preserve all info; we can duplicate? Not ideal but we can split. Let's decide: About the role: position summary paragraph. Responsibilities: list duties. Requirements: physical activities (sedentary work, sitting most of the time, office environment, standard office equipment, exerts up to 30 lbs occasionally) and language skills (strong interpersonal and communications skills, ability to present information, clear responses, write reports, procedures, business correspondence). Also maybe "Fluent/proficient spoken and written English" could be here. Qualifications: minimum qualifications (high skill with MS Office, Adobe Acrobat, willingness to learn new software, ability to work under pressure, adaptable, excellent verbal/written communication, teamwork, organization, typing 45-50 wpm, good research skills) plus preferred qualifications (technical aviation knowledge, Framemaker skills, technical writing experience, Bachelor’s degree or higher in English, Communications, Technical Writing or related). Skills: maybe we could list specific technical skills: MS Office, Adobe Acrobat, typing speed, research, etc. But that duplicates. Perhaps we can omit Skills section and put all under Qualifications. But we need to use headings only when there is real content; we can omit Skills if we feel Qualifications covers it. However the instruction: "Prefer a few substantive sections over many thin ones." So we could have About the role, Responsibilities, Qualifications (including minimum and preferred), Requirements (physical and language). That's four sections. That seems fine. We must not include Benefits, Pay, Schedule. Now ensure we don't include any placeholder like "None". We'll omit Supervisory Responsibilities. Now craft HTML. We'll need to escape any special characters? Not needed. Let's write:

  About the role

  The Technical Publications Analyst is responsible for issuing and auditing documentation for a wide range of uses in the Airline Quality Control and Airline Operations departments. The analyst will audit currency of manufacturers’ manuals and company manuals as distributed and assist in the production of company manual revisions as required.

  Responsibilities

  • Issues and tracks revisions to all company-controlled manuals assigned to aircraft.
  • Maintains and updates manuals status reports for Maintenance and Flight Operations Department, and aircraft audit lists for crew use.
  • Organizes and maintains company’s manuals servers with all master manuals, including company-generated and manufacturer-issued documents.
  • Responsible for auditing manufacturer-provided data for currency and completeness.
  • Assists in ordering company controlled materials as needed.
  • Maintains and updates Tech Pubs open action items in the Safety Management database.
  • Ensures all manual revision requests are supported by approved Manual Change Request forms.
  • Responsible for contacting manufacturers to ensure that their contact information is correct, that they are still responsible for STCs listed, and that we have access to related documentation.
  • Provides assistance to operations/maintenance personnel, flight crews, vendors and other employees to ensure they are able to access manuals via company manuals servers and company-issued iPads.
  • Works with Technical Publications staff to create, circulate and issue revisions to company manuals as needed.
  • Works with Technical Publications to create company forms and SOP documents as needed.
  • Works with Technical Publications and Engineering to create and revise task cards as needed.
  • Responsible for managing tasks associated with iPad program for both Maintenance and Flight Operations.

  Requirements

  • Sedentary work; sitting most of the time in an office environment.
  • Routinely involves standard office equipment such as computers, phones, photocopiers, filing cabinets and fax machines.
  • Exerts up to 30 lbs. of force occasionally for office supplies and equipment.
  • Strong interpersonal and communications skills; able to effectively present information, provide clear responses to questions, and write reports, procedures, and business correspondence.
  • Fluent/proficient spoken and written English.

  Qualifications

  • High skill and comfort level with common office software, including MS Office and Adobe Acrobat.
  • Willing and able to develop proficiency in new software titles and data systems.
  • Strong ability to work under pressure.
  • Adaptable to new projects and tasks.
  • Excellent verbal and written communication skills.
  • Able to work well with others and work together to accomplish various projects.
  • Excellent organization skills.
  • Types at least 45-50 wpm.
  • Possesses good research skills.
  • Preferred: Previous technical aviation knowledge.
  • Preferred: Framemaker skills (structured or unstructured) – preferred but not required.
  • Preferred: Previous technical writing experience.
  • Preferred: Bachelor’s degree or higher in English, Communications, Technical Writing or other related area of study.
  We have not included Skills section; we could add Skills but we already covered many skills in Qualifications. Might be okay. Check that we didn't repeat job title. No. We