Technical Editor and Writer Level 5

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. We need to preserve all substantive info: relocation assistance, clearance required for start, clearance type, travel, description paragraphs, responsibilities (list of duties), basic qualifications, preferred qualifications, salary range, benefits description. We need to decide sections: About the role (maybe the introductory description about Northrop Grumman and role). Responsibilities (list of duties). Requirements (maybe basic qualifications). Qualifications (maybe preferred qualifications). Skills (maybe list of skills like proficiency with MS Office, publishing software, vector graphic designing, etc). Benefits (benefits description). Pay (salary range). Schedule (maybe travel %? Actually schedule not given; travel is 10% of time. Could be schedule? Not exactly schedule. There's no explicit schedule like full-time, shift. So we should not create Schedule section unless posting actually states them. It does not state schedule like hours, shift. So omit Schedule. We must not create sections with filler like "commensurate with experience". Pay section we have salary range, so include Pay. Benefits: we have description of benefits: health insurance, life and disability, savings plan, company paid holidays, PTO. Include Benefits. Now we need to format using

for section headings. Use

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

  for prose. We must not include markdown fences. Let's extract content. First, relocation assistance line: "RELOCATION ASSISTANCE: Relocation assistance may be available". Also "CLEARANCE REQUIRED FOR START: No", "CLEARANCE TYPE: Secret", "TRAVEL: Yes, 10% of the Time". These are metadata; we can fold into a short

  maybe under About the role or separate? Probably include in About the role paragraph. Description paragraphs: Starting "At Northrop Grumman, our employees...". That's about company and role. We'll put that in About the role. Then "We are looking for you to join our team as a Technical Editor and Writer Level 5 based out of Merritt Island, FL. OR Silverdale, WA. OR Sunnyvale, CA. OR Kings Bay, GA. OR Ocean Springs, MS." That's location info; could be in About the role. Then "As a Technical Editor and Writer Level 5 at Northrop Grumman you will have a challenging and rewarding opportunity..." That's responsibilities intro. Then bullet list of duties: "Write and/or edit technical documents such as technical procedure manuals, user manuals, programming manuals, service manuals, operational specifications, and related technical publications." etc. We'll make a

  list. Then "This requisition may be filled at Technical Editor and Writer Level 5 based on qualifications listed below:" then Basic Qualifications bullet list. Then "Preferred Qualifications" bullet list. Then "Primary Level Salary Range: $73,900.00 - $128,400.00" plus explanation. Then benefits paragraph: "In addition, Northrop Grumman provides a variety of benefits including health insurance coverage, life and disability insurance, savings plan, Company paid holidays and paid time off (PTO) for vacation and/or personal business." Also earlier: "Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses are designed to reward individual contributions as well as allow employees to share in company results. Employees in Vice President or Director positions may be eligible for Long Term Incentives." That's also compensation/benefits; could be included in Pay or Benefits. We'll include in Pay section maybe. We need to avoid repeating job title as heading. So no

  Technical Editor and Writer Level 5. Now produce HTML. Structure:

  Relocation assistance may be available. Clearance required for start: No. Clearance type: Secret. Travel: Yes, 10% of the time.

  Then

  About the role

  with paragraphs: the description about Northrop Grumman, mission, location, etc. We need to ensure we don't duplicate content. Let's craft About the role paragraph(s): First paragraph: "At Northrop Grumman, our employees have incredible opportunities to work on revolutionary systems that impact people's lives around the world today, and for generations to come. Our pioneering and inventive spirit has enabled us to be at the forefront of many technological advancements in our nation's history - from the first flight across the Atlantic Ocean, to stealth bombers, to landing on the moon. We look for people who have bold new ideas, courage and a pioneering spirit to join forces to invent the future, and have fun along the way. Our culture thrives on intellectual curiosity, cognitive diversity and bringing your whole self to work — and we have an insatiable drive to do what others think is impossible. Our employees are not only part of history, they're making history." Second paragraph: "Northrop Grumman Mission Systems is a trusted provider of mission-enabling solutions for global security. Our Engineering and Sciences (E&S) organization pushes the boundaries of innovation, redefines engineering capabilities, and drives advances in various sciences. Our team is chartered with providing the skills, innovative technologies to develop, design, produce and sustain optimized product lines across the sector while providing a decisive advantage to the warfighter." Third paragraph: "Come be a part of our mission! We are looking for you to join our team as a Technical Editor and Writer Level 5 based out of Merritt Island, FL. OR Silverdale, WA. OR Sunnyvale, CA. OR Kings Bay, GA. OR Ocean Springs, MS." Fourth paragraph: "As a Technical Editor and Writer Level 5 at Northrop Grumman you will have a challenging and rewarding opportunity to be a part of our Enterprise-wide digital transformation. Through the use of Model-based Engineering, DevSecOps and Agile practices we continue to evolve how we deliver critical national defense products and capabilities for the warfighter. Our success is grounded in our ability to embrace change, move quickly and continuously drive innovation. The successful candidate will be collaborative, open, transparent, and team-oriented with a focus on team empowerment & shared responsibility, flexibility, continuous learning, and a culture of automation." That seems good. Now Responsibilities: list of duties. We'll create

  Responsibilities

  then
  with each duty as
  • . Duties list from "What You’ll Get To Do": - Write and/or edit technical documents such as technical procedure manuals, user manuals, programming manuals, service manuals, operational specifications, and related technical publications. - Communicate clearly and effectively technical specifications and instructions to a wide range of audiences. - Develop subject knowledge by interviewing product developers, observing performance of production performance observation, referring to technical specifications, blueprints, engineering illustrations, and trade journals. - Take strong ownership to drive documentation through process from inputs to final distribution. - Lead preparation of illustrative materials, selecting drawings, sketches, diagrams and charts. - Conduct quality review of materials. - Develop new concepts, techniques, and standards. - Communicate effectively and clearly present technical approaches and findings. - Support implementation to a team of technical writers and text processors. - Serve as lead consultant to management and special external spokesperson for the organization on major matters pertaining to its policies, plans, and objectives. - Present to internal and external stakeholders at reviews/documentation conferences. - Develop agendas and captures minutes to assess documentation impacts. We need to keep exact phrasing? Preserve all substantive information; do not invent or summarize away detail. So we should copy the sentences as they appear. Let's extract each bullet exactly as in text: From posting: "What You’ll Get To Do Write and/or edit technical documents such as technical procedure manuals, user manuals, programming manuals, service manuals, operational specifications, and related technical publications.Communicate clearly and effectively technical specifications and instructions to a wide range of audiences.Develop subject knowledge by interviewing product developers, observing performance of production methods, referring to technical specifications, blueprints, engineering illustrations, and trade journals.Take strong ownership to drive documentation through process from inputs to final distribution.Lead preparation of illustrative materials, selecting drawings, sketches, diagrams and charts.Conduct quality review of materials.Develop new concepts, techniques, and standards.Communicate effectively and clearly present technical approaches and findings. Support implementation to a team of technical writers and text processors.Serve as lead consultant to management and special external spokesperson for the organization on major matters pertaining to its policies, plans, and objectives. Present to internal and external stakeholders at reviews/documentation conferences. Develop agendas and captures minutes to assess documentation impacts." Note there is no punctuation between some sentences; but we can keep as is. We'll separate into list items with periods. We'll produce each as
  • with the sentence. Now Requirements: maybe basic qualifications. We'll create

    Requirements

    with
    list. Basic Qualifications bullet list: - Bachelor’s Degree with 12 years of experience or Master’s Degree with 10 years of experience. - Additional 15 years’ experience may be accepted in lieu of a Degree. - Proficiency with Microsoft Office - Experience with publishing software. - Experience with vector graphic designing applications (Illustrator preferred). - Ability to meet deadlines and quality standards - Strong interpersonal, written, and oral communication skills - Must be a U.S. Citizen - Ability to obtain a Secret Security Clearance. We need to keep exactly as posted. Now Qualifications: maybe Preferred Qualifications.

    Qualifications

    with
    list. Preferred Qualifications bullet list: - Experience with military documentation standards and style guides - Experience with SharePoint, Confluence, and/or JIRA - Experience with writing procedures and technical manuals that describe installation, operation, and maintenance of equipment - Understanding of XML and other authoring languages - Experience with documentation authoring/publishing tools - Familiarity with database structures to support development of interactive electronic technical manuals (IETMs) - Active Secret Security Clearance Now Skills: maybe we could combine some skills from basic qualifications like proficiency with MS Office etc. But we already have those in Requirements. Could create Skills section for things like "Strong interpersonal, written, and oral communication skills" etc. But we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they ask to use headings for sections like Requirements, Qualifications, Skills. We can include them if they have content. We have content for Requirements (basic qualifications) and Qualifications (preferred). Skills could be derived from those but we might not need separate Skills if we already covered. However we could create Skills section for things like "Proficiency with Microsoft Office, Experience with publishing software, Experience with vector graphic designing applications (Illustrator preferred), Ability to meet deadlines and quality standards, Strong interpersonal, written, and oral communication skills". But that duplicates Requirements. Better to keep Requirements and Qualifications and maybe omit Skills to avoid thin sections. But we need to follow instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to include all. So we can omit Skills if not needed. Now Benefits: we have paragraph about benefits. Also mention overtime, shift differential, discretionary bonus, annual bonuses, long term incentives for VP/Director. We'll include in Benefits. We'll create

    Benefits

    with

    containing: "Depending on the position, employees may be eligible for overtime, shift differential, and a discretionary bonus in addition to base pay. Annual bonuses are designed to reward individual contributions as well as allow employees to share in company results. Employees in Vice President or Director