MATERIAL PLANNER 2

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, EEO, etc. Must preserve all substantive info. Let's parse the posting: - Req ID: 48374 (metadata, drop) - Team: C104 PRODUCTION FACILITIES (metadata) - Entity: Newport News Shipbuilding (metadata) - US Citizenship Required for this Position: Yes (metadata) - Full-Time Shift: Multiple (metadata) - Relocation: No relocation assistance available (metadata) - Virtual/Telework Opportunity: No - Not eligible for telework (metadata) - Travel Requirement: No (metadata) - Clearance Required: No - Clearance Not Required to Start (metadata) Then a paragraph about HII Newport News Shipbuilding: description. Then "Want to be part of the team? Apply today! We look forward to meeting you." (call to action, maybe drop as application instruction? It's not exactly instruction but encouraging to apply; we can drop as it's not substantive content about role.) Then "The Role" heading (but we shouldn't repeat job title as heading; we can treat as section heading "About the role"? Actually they say use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have description of role: "Prepares lists of materials, accessories, and parts used in production following engineering and design blueprints. Examines blueprints, identifies parts code, computes quantity needed, and lists total material requirements including contract numbers, routing, and special handling instructions. Submits list to purchasing department for use in preparing purchase orders." That's responsibilities/duties. Then "Must Have High School/GED and 2 years of additional education and/or experience" (requirements/qualifications). Then "Nice to Have" (maybe skills? but not detailed). It just says "Nice to Have" with no content after? Actually after that line, there is "Why HII". So "Nice to Have" heading with no detail; we should not create a section if no specific content. So we skip. Then "Why HII" paragraph about mission, workforce, benefits, etc. That could be "About the role"? Actually "About the role" is more about the role itself; but we have role description already. "Why HII" is about company; could be "About the role"? Not exactly. Could be "About the role" or maybe we can treat as "About the role" includes company description? The instruction: Use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content. We have: - About the role: could include the introductory paragraph about HII Newport News Shipbuilding (the company) and maybe the role summary? But we already have role duties. Could combine. Better: Use "About the role" for the company overview and role summary (maybe first paragraph). Then "Responsibilities" for the duty list. Then "Requirements" for the Must Have. Then "Benefits" for the benefits list (medical, etc). No Pay or Schedule specifics given (Shift: Multiple but that's metadata; we could include schedule? It says Full-Time Shift: Multiple. That's schedule info but it's metadata; we could include schedule section if we have real content. The posting says "Full-Time Shift: Multiple". That's a schedule detail. Should we include schedule section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. "Multiple" is specific? It indicates multiple shifts. Could be considered schedule info. However they said "Prefer a few substantive sections over many thin ones." Might be okay to include schedule. But we also have "US Citizenship Required for this Position: Yes" - that's a requirement; could be included in Requirements. We also have "Clearance Required: No". Not needed. We have "Relocation: No relocation assistance available" - could be a note but not a section. We have "Travel Requirement: No". We have "Virtual/Telework Opportunity: No". We have "Team: C104 PRODUCTION FACILITIES" maybe not needed. We have "Entity: Newport News Shipbuilding". We have "Req ID: 48374". We should drop metadata like Req ID, Team, Entity, etc unless we fold into short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph at top with metadata like "Req ID: 48374 | Team: C104 PRODUCTION FACILITIES | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time Shift: Multiple | Relocation: No relocation assistance available | Virtual/Telework: No | Travel: No | Clearance: Not required". But that's a lot; maybe better to drop as not substantive. The instruction says fold minor metadata into a short

or drop it. Could include a short p with key info: US Citizenship required, Full-Time, Shift Multiple, No relocation, No telework, No travel, No clearance. That's still many items but okay. But we need to preserve ALL substantive information. Is citizenship substantive? Yes. Shift? Yes. Relocation? Yes. Telework? Yes. Travel? Yes. Clearance? Yes. So we should keep them somewhere. We could make a

at start: "US Citizenship required. Full‑time position with multiple shifts. No relocation assistance, telework, or travel required. No security clearance needed to start." That captures. Now sections: - About the role: Could include the paragraph about HII Newport News Shipbuilding (the company) and maybe a brief role summary? But we have role details in Responsibilities. Could put company overview in About the role. - Responsibilities: the duty list. - Requirements: Must Have High School/GED and 2 years of additional education and/or experience; also US Citizenship required (though we already mentioned). Could also include "Nice to Have" but no detail. - Benefits: list of benefits. - Schedule: maybe we already included shift in metadata p; but we could also have a Schedule section with "Multiple shifts". However we already put shift in metadata p; but we could still have a Schedule section with that detail. The instruction: prefer few substantive sections over many thin ones. If we already put shift in metadata p, we might not need separate Schedule section. But we need to preserve shift info; we already did. So we can skip Schedule section. - Pay: not specified, so omit. Thus sections: About the role, Responsibilities, Requirements, Benefits. Check if we have any Skills section: none specific. Now we need to format lists with

• for any list of duties/requirements/benefits. Responsibilities: we have three sentences; could be list items. Requirements: we have "High School/GED and 2 years of additional education and/or experience". Could be list item. Benefits: list many items. Now we need to ensure we don't repeat job title as heading. No job title given explicitly; we can ignore. Now produce HTML fragment: Start with a

  for metadata summary. Then

  About the role

  then

  with company description. Then

  Responsibilities

  then
  • ...
  etc. Then

  Requirements

  then
  • ...
  maybe also include US Citizenship required? Already in metadata p; but we could also include in Requirements. However we already captured citizenship in metadata p; but we could also include it in Requirements for completeness. But we must not duplicate? The instruction: preserve ALL substantive information; duplication is okay if it's already elsewhere? It says remove duplicated lines. So we should avoid duplicating the same info. So we should not repeat citizenship in Requirements if we already put it in metadata p. But we could decide to not include metadata p and instead put citizenship in Requirements. Which is better? The metadata p is short; we could keep it and not duplicate citizenship elsewhere. However we need to ensure we preserve all substantive info; we have citizenship in metadata p, that's fine. Now Requirements: only the education/experience. Now Benefits: list. Now check for any other substantive content: "Why HII" includes mission statement, workforce description, values, etc. That could be part of About the role. We already have company description paragraph; we could expand About the role to include that mission and values. Let's incorporate the "Why HII" paragraph into About the role. Thus About the role

  will contain: description of HII Newport News Shipbuilding (size, role, etc) plus the Why HII paragraph (mission, workforce, values, benefits? Actually benefits are separate). But we should not include benefits there because we have Benefits section. Thus About the role

  will combine the initial paragraph about HII Newport News Shipbuilding (size, etc) and the "Why HII" paragraph (mission, workforce, values, supportive environment, training programs). That seems appropriate. Now Benefits

  list: medical, prescription drug, dental and vision plan choices, on-site health centers, tele-medicine, wellness resources, employee assistance programs, savings plan options (401K), financial education and planning tools, life insurance, tuition reimbursement, employee discounts, early childhood and post-secondary education scholarships, and more. Also note "Some benefits may vary depending on your specific division or work location." That's substantive; include as a sentence after list maybe in

  . Now ensure we don't include boilerplate: EEO statement, accommodation request, contact info, etc. Remove those. Now produce HTML. Check for any other content: "Full-Time Shift: Multiple" we captured in metadata p. "Relocation: No relocation assistance available" captured. "Virtual/Telework Opportunity: No - Not eligible for telework" captured. "Travel Requirement: No" captured. "Clearance Required: No - Clearance Not Required to Start" captured. Now metadata p: maybe combine: "US Citizenship required. Full‑time position with multiple shifts. No relocation assistance, telework, or travel required. No security clearance needed to start." Now final HTML:

  US Citizenship required. Full‑time position with multiple shifts. No relocation assistance, telework, or travel required. No security clearance needed to start.

  About the role

  [combined company description and Why HII]

  Responsibilities

  • Prepares lists of materials, accessories, and parts used in production following engineering and design blueprints.
  • Examines blueprints, identifies parts code, computes quantity needed, and lists total material requirements including contract numbers, routing, and special handling instructions.
  • Submits list to purchasing department for use in preparing purchase orders.

  Requirements

  • High school diploma or GED and 2 years of additional education and/or experience.

  Benefits

  • Medical, prescription drug, dental and vision plan choices
  • On‑site health centers
  • Tele‑medicine
  • Wellness resources
  • Employee assistance programs
  • Savings plan options (401K)
  • Financial education and planning tools
  • Life insurance
  • Tuition reimbursement
  • Employee discounts
  • Early childhood and post‑secondary education scholarships

  Some benefits may vary depending on your specific division or work location