Technical Writer

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like Work Authorization/Security Clearance Requirements? That might be part of Requirements or Qualifications? We need to map content. Let's parse the posting: - Intro: "AIT is the world's largest provider..." This is about the company. Could be "About the role"? Actually "About the role" maybe summary of role. The posting includes "Summary The technical writer supports the end-users by analyzing information support requirements; writing and upgrading product documentation." That's a summary. - Salary Range: $85K - $100K -> Pay section. - Duties And Responsibilities: a long list. - Education And Work Experience: qualifications. - Work Authorization/Security Clearance Requirements: maybe part of Requirements or Qualifications. - Knowledge, Skills, And Abilities: skills. - Work Conditions: environment type, exposure types, work hours, travel requirements, physical demands, etc. Could be part of Schedule? Actually schedule: "Standard work schedule, overtime may be necessary for meeting deadlines, required travel, emergent conditions." Travel requirements separate. Could be part of Schedule or maybe separate but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Benefits: they mention "competitive compensation package (including free medical options for employees and their family), casual work environment and excellent growth opportunities." That's benefits. - Pay: salary range. - Schedule: work hours, overtime, travel. - About the role: maybe the introductory paragraph about AIT and summary. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title. Not include Job ID. We must not include boilerplate like EEO, etc. So we need to strip those. We must preserve all substantive info: that includes details about duties, education, skills, etc. We need to format using

for each section heading, then content:

for prose,

• for lists. We need to decide what goes where. Let's extract sections: About the role: Could include company description and summary of role. The posting starts: "AIT is the world's largest provider of automation, factory integration and tooling solutions dedicated to the global aerospace, defense, and space launch vehicle industries. AIT offers a competitive compensation package (including free medical options for employees and their family), casual work environment and excellent growth opportunities. Summary The technical writer supports the end-users by analyzing information support requirements; writing and upgrading product documentation." We could combine that into About the role: a paragraph describing the role and company. Responsibilities: The "Duties And Responsibilities" block. Requirements: Might include Work Authorization/Security Clearance Requirements? Or maybe "Education And Work Experience" is Qualifications. Actually typical sections: Education And Work Experience = Qualifications. Knowledge, Skills, And Abilities = Skills. Work Authorization/Security Clearance Requirements = Requirements (like legal eligibility). Also maybe "Work Conditions" could be Schedule? But we have Schedule heading for work hours, overtime, travel. Physical demands maybe not needed but could be part of Schedule? However schedule is about time, not physical demands. But we have no other heading for physical demands; we could omit if not fitting allowed headings. But we must preserve all substantive info; we cannot drop physical demands unless we can fit them under Schedule? Not ideal. However instructions: "Prefer a few substantive sections over many thin ones." We could include Schedule to cover work hours, overtime, travel, physical demands? Might be okay to include physical demands under Schedule as part of work conditions. But better to maybe include them under Schedule? The heading Schedule is for work schedule; physical demands not schedule. But we have no other heading for physical demands; we could maybe put them under Requirements? Not appropriate. Could we create a section not in allowed list? No, only allowed headings are those eight. So we must fit everything into those sections. If something doesn't fit, we may need to omit? But we must preserve ALL substantive information. So we need to find a way to include physical demands somewhere within allowed sections. Perhaps we can include them under Schedule as part of "Work Conditions" which includes work hours, travel, physical demands. The heading Schedule may be interpreted broadly as work conditions. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples, not strict limitation to only those exact headings? It says use those for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we must map all content to those. Thus we need to map: - About the role: company description + summary. - Responsibilities: duties list. - Requirements: maybe security clearance, work authorization, citizenship, etc. - Qualifications: education and work experience. - Skills: knowledge, skills, abilities list. - Benefits: competitive compensation package (free medical, casual work environment, growth opportunities). - Pay: salary range. - Schedule: work hours, overtime, travel, physical demands, environment type, exposure types. We must ensure we don't create sections with filler. All have real content. Now we need to strip boilerplate: EEO, equal opportunity, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Work Authorization/Security Clearance Requirements" heading but keep its content under Requirements. Also remove "AIT Safety - ..." etc? Those are boilerplate about safety, quality, procedure compliance, security clearance statement, ITAR requirements, EEO, Affirmative Action, Revision History, etc. Those are legal/boilerplate; we should remove them. However some content like "Security Clearance Statement - This position may require a government security clearance; you must be a US Citizen for consideration." That's substantive (requirement). So we need to keep that but strip the surrounding boilerplate phrasing? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can keep the substantive requirement but remove the legal boilerplate phrasing. For example, "Security Clearance Statement - This position may require a government security clearance; you must be a US Citizen for consideration." The phrase "Security Clearance Statement -" maybe considered boilerplate? But the core requirement is that position may require govt security clearance, must be US Citizen. We can keep that as a sentence. Similarly ITAR Requirements: "To conform to U.S. Government commercial space technology export regulations, including the International Traffic in Arms Regulations (ITAR), 8 U.S.C. 1324b(a)(3), applicants for employment at AIT must be a U.S. citizen or national, lawfully admitted for permanent residence into the U.S. (i.e. current green card holder), or lawfully admitted as a refugee or granted asylum under 8 U.S.C.1157-1158." That's also a requirement about citizenship. We can keep the substance: applicants must be US citizen/national, permanent resident, refugee/asylee. Affirmative Action and Disability Accommodation: that's boilerplate; remove. Revision History: remove. EEO is the Law | E-Verify: remove. Also "AIT Safety - AIT enforces a safety culture..." etc. That's boilerplate about safety, quality, procedure compliance. Might be considered legal boilerplate; remove. Thus we keep only substantive info: company description, summary, duties, education/experience, skills, benefits, pay, schedule (work hours, overtime, travel, physical demands, environment), requirements (security clearance, citizenship). Now we need to format. Let's extract each piece. **About the role**: - "AIT is the world's largest provider of automation, factory integration and tooling solutions dedicated to the global aerospace, defense, and space launch vehicle industries." - "AIT offers a competitive compensation package (including free medical options for employees and their family), casual work environment and excellent growth opportunities." - "Summary The technical writer supports the end-users by analyzing information support requirements; writing and upgrading product documentation." We could combine into a paragraph. **Responsibilities** (Duties And Responsibilities): List items: - Understand documentation requirements by conferring with mechanical design engineers, software developers and electrical engineers; studying mechanical designs using 3D models and 2D drawings in either of the following software: CATIA V5, NX, Solidworks, Pro E, etc. - Able to understand complex concepts then document these at a level that would be easily understood by a semi-skilled user. - When writing operations manuals, use illustrations and text to tell the “story” in a clear manner that is easily to follow, while remaining concise. - Maintenance manuals are to be written with a skilled person in mind. - Confirm documentation by observing product use and interviewing users. - Improve documentation by evaluating frequently asked questions, interviewing technical support specialists and users. - Update job knowledge by participating in educational workshops, reading professional publications, maintaining personal networks, participating in professional organizations. - Enhance organization reputation by accepting ownership for accomplishing new and different requests, exploring opportunities to add value to job accomplishments. - Maintain safe and healthy training environment by following organization standards and legal regulations. - Maintain quality service by establishing and enforcing organization standards. - Contribute to team effort by accomplishing related results as needed. - Perform other duties as assigned. Note: Some sentences start with "Able to..." which is more like a skill but appears in duties. We'll keep as duty. **Requirements** (Work Authorization/Security Clearance Requirements + ITAR etc): - This position may require a government security clearance; you must be a US Citizen for consideration. - To conform to U.S. Government commercial space technology export regulations, including the International Traffic in Arms Regulations (ITAR), applicants for employment at AIT must be a U.S. citizen or national, lawfully admitted for permanent residence into the U.S. (i.e. current green card holder), or lawfully admitted as a refugee or granted asylum. We could combine: "Position may require a government security clearance; applicants must be U.S. citizens or nationals, lawful permanent residents (green card holders), refugees, or asylees." **Qualifications** (Education And Work Experience): - Bachelor’s degree in professional writing, technical writing, or in a technical field required. - Minimum of three years of technical writing or similar experience with focus on aerospace tooling design and automated equipment. - Experience with Adobe InDesign. - Working knowledge of Word and Excel. - Proficient in the use of Adobe Creative Cloud software to create illustrations from CAD models. **Skills** (Knowledge, Skills, And Abilities): List items: - Able to read and understand engineering data using 3D models, 2D drawings, and schematics (i.e.: Electrical, Hydraulic, and Pneumatic) - Able to understand complex concepts then document these at a level that would be easily understood by a semi-skilled user. - Able to read design drawings for Bills of Material (BOMs). - Display a high level of initiative, effort, and commitment towards completing assignments in a timely manner. - Excellent time management skills and ability to plan and set priorities. - Take personal responsibility for the quality and timeliness of work and achieves results. - Clear and effective communication skills in both written and spoken forms. - Clearly articulates ideas, opinions, and information so others understand them. - Able to properly structure, organize, and grammatically correct reports and documents. - Knowledge of computer applications including email, databases, word-processing program, and spreadsheets (such as Microsoft Office). - Maintain confidentiality while processing