DOCUMENT CONTROL SUPPORT 2
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe includes company description). We'll include that. - "The Role Performs operational duties in support of regulatory and/or Good Manufacturing Practice (GMP) compliance documentation; coordinating the verification, approval, and processing of document revisions; and tracking document activity to ensure timeliness and process efficiency." That's responsibilities. - "Must Have High School/GED and 2 years of additional education and/or experience" That's qualifications/requirements. - "Nice to Have Regular and Consistent Attendance Ready to Work Adaptable to Changing Work Environments and Situations Adequate Technical Knowledge of Microsoft Office Programs Ability to Collaborate, Communicate and Cooperate with peers, customers, management and others Ability to Work Autonomously and Within Groups Strong Written and Verbal Communication Skills" Those are skills/requirements. - Benefits: "We offer comprehensive benefits including: 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. Some benefits may vary depending on your specific division or work location." - Pay: Salary range given. - Schedule: Full-Time Shift: 1st. So schedule info: Full-Time, 1st shift. - Also US Citizenship Required, etc. Could be part of Requirements? Might be a requirement. But we can include in Requirements or Qualifications. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include US Citizenship Required etc in a short paragraph maybe under Requirements. We need to avoid boilerplate: EEO, accommodation, etc. Remove those. We need to preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include.
We have content for:
- About the role: company description (Meet HII’s Newport News Shipbuilding ...). That's substantive.
- Responsibilities: The Role Performs operational duties... (one sentence). Could be a
or
- . Since it's a single duty description, we can put in
. But instruction: Use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. So we can put responsibilities in
.
- Requirements: Must Have High School/GED and 2 years of additional education and/or experience. Also US Citizenship Required, Full-Time, Shift: 1st? Actually shift is schedule. But we can include citizenship and education as requirements. Could be a
- .
- Qualifications: maybe same as requirements? The distinction is fuzzy. We could combine. But we need to avoid thin sections. Perhaps we have Requirements (education/experience, citizenship) and Qualifications (maybe none separate). Could skip Qualifications if no distinct content.
- Skills: Nice to Have list: Regular and Consistent Attendance, Ready to Work, Adaptable..., Technical Knowledge of Microsoft Office, Ability to Collaborate..., Ability to Work Autonomously..., Strong Written and Verbal Communication Skills. That's a list of skills. Use
- .
- Benefits: list of benefits. Use
- .
- Pay: Salary range. Use
.
- Schedule: Full-Time Shift: 1st. Use
.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid.
Schedule: we have Full-Time Shift: 1st. That's specific.
Now we need to remove boilerplate: EEO, accommodation, etc. Also remove "Meet HII’s Newport News Shipbuilding With more than 25,000 employees..." That's substantive, keep.
Also remove "Want to be part of the team? Apply today! We look forward to meeting you." That's application instruction? It's a call to action; maybe considered boilerplate? The instruction says remove application instructions. That line is an invitation to apply; likely considered application instruction. So we should drop it.
Also remove "All qualified applicants will receive consideration..." that's EEO boilerplate; drop.
Also remove "Do You Need Assistance?" etc; drop.
Also remove "U.S. Citizenship may be required for certain positions." Actually we have US Citizenship Required for this Position: Yes earlier; we keep that as requirement.
Now produce HTML.
Structure:
About the role
Meet HII’s Newport News Shipbuilding With more than 25,000 employees – including third-, fourth- and even fifth-generation shipbuilders – HII’s Newport News Shipbuilding (NNS) division is the largest industrial employer in Virginia. We’re the sole designer, builder and refueler of U.S. Navy nuclear aircraft carriers and one of two providers of U.S. Navy nuclear submarines. Our diverse and innovative team of professionals ranges from skilled trades to project managers, engineers and software developers to solution architects, technical subject matter experts, and system users. We collaborate together at the forefront of technology, manufacturing, and integration of the most powerful and survivable naval ships in the world.
Responsibilities
The Role Performs operational duties in support of regulatory and/or Good Manufacturing Practice (GMP) compliance documentation; coordinating the verification, approval, and processing of document revisions; and tracking document activity to ensure timeliness and process efficiency.
Requirements
- High School/GED and 2 years of additional education and/or experience
- U.S. Citizenship required
Skills
- Regular and Consistent Attendance
- Ready to Work
- Adaptable to Changing Work Environments and Situations
- Adequate Technical Knowledge of Microsoft Office Programs
- Ability to Collaborate, Communicate and Cooperate with peers, customers, management and others
- Ability to Work Autonomously and Within Groups
- Strong Written and Verbal Communication Skills
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
Pay
Salary Range: $42,000.00 to $52,000.00
Schedule
Full-Time, 1st shift
Check if any content missing: The posting also mentions "Relocation: No relocation assistance available", "Virtual/Telework Opportunity: No - Not eligible for telework", "Travel Requirements: No", "Clearance Required: No - Clearance Not Required to Start". Those are minor metadata; we could fold into a short paragraph under Requirements or maybe a separate section like "Additional Details". But the instruction says only include sections when posting has real, specific content for it. Those are specific but maybe minor. Could we add a section "Additional Details"? Not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. We could fold those minor metadata into Requirements or maybe a short paragraph under Requirements. But we already have Requirements list; we could add items like "No relocation assistance", "Not eligible for telework", "No travel required", "No clearance required". However those are not requirements but details. Could be okay to add as list items under Requirements? Might be stretching. Better to maybe add a short after Requirements that includes those details, but that would be prose not a list. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we could add a
under Requirements that includes those details. But we already have a
for Requirements; we could add a after the list. That's okay.
But we need to avoid creating thin sections. Adding a paragraph under Requirements is fine.
Similarly, we could add a short paragraph under Schedule about full-time etc. Already we have schedule.
We need to ensure we don't duplicate content.
Let's incorporate:
After Requirements list, add a
with: "No relocation assistance available. Not eligible for telework. No travel required. No clearance required to start."
That is prose.
Now check if we missed any substantive content: "The anticipated salary range represents the estimated base pay for this role. Final compensation will be determined based on experience, qualifications, and other job-related factors, and may vary from the posted range". That's more detail about pay. We could include that in Pay section as prose after the salary range. So Pay section:
Salary Range: $42,000.00 to $52,000.00
The anticipated salary range represents the estimated base pay for this role. Final compensation will be determined based on experience, qualifications, and other job-related factors, and may vary from the posted range.
Now check if we missed any content about "Full-Time Shift: 1st". Already schedule.
Now check if we missed any content about "Team: E08 E&D BUSINESS OPS Entity: Newport News Shipbuilding". That's metadata; could be folded into About the role? Already we have company description. Could add a short line about team/entity. But maybe not needed.
We need to preserve ALL substantive information. The team and entity are substantive? Possibly minor metadata but still part of posting. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. So we can fold Team, Entity into a short paragraph maybe under About the role or Requirements. Let's add a short paragraph after About the role: "Team: E08 E&D BUSINESS OPS. Entity: Newport News Shipbuilding." That's prose.
Now check if we missed any content about "US Citizenship Required for this Position: Yes". Already in Requirements.
Now check if we missed any content about "Full-Time Shift: 1st Relocation: No relocation assistance available Virtual/Telework Opportunity: No - Not eligible for telework Travel Requirements: No Clearance Required: No - Clearance Not Required to Start". We covered relocation, telework, travel, clearance in the Requirements paragraph. Shift
for prose. We need to decide which sections to include. We have content for: - About the role: company description (Meet HII’s Newport News Shipbuilding ...). That's substantive. - Responsibilities: The Role Performs operational duties... (one sentence). Could be a
or
- . Since it's a single duty description, we can put in
. But instruction: Use
- for any list of duties/requirements/benefits. If it's not a list, we can use
. So we can put responsibilities in
. - Requirements: Must Have High School/GED and 2 years of additional education and/or experience. Also US Citizenship Required, Full-Time, Shift: 1st? Actually shift is schedule. But we can include citizenship and education as requirements. Could be a
- .
- Qualifications: maybe same as requirements? The distinction is fuzzy. We could combine. But we need to avoid thin sections. Perhaps we have Requirements (education/experience, citizenship) and Qualifications (maybe none separate). Could skip Qualifications if no distinct content.
- Skills: Nice to Have list: Regular and Consistent Attendance, Ready to Work, Adaptable..., Technical Knowledge of Microsoft Office, Ability to Collaborate..., Ability to Work Autonomously..., Strong Written and Verbal Communication Skills. That's a list of skills. Use
- .
- Benefits: list of benefits. Use
- .
- Pay: Salary range. Use
. - Schedule: Full-Time Shift: 1st. Use
. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid. Schedule: we have Full-Time Shift: 1st. That's specific. Now we need to remove boilerplate: EEO, accommodation, etc. Also remove "Meet HII’s Newport News Shipbuilding With more than 25,000 employees..." That's substantive, keep. Also remove "Want to be part of the team? Apply today! We look forward to meeting you." That's application instruction? It's a call to action; maybe considered boilerplate? The instruction says remove application instructions. That line is an invitation to apply; likely considered application instruction. So we should drop it. Also remove "All qualified applicants will receive consideration..." that's EEO boilerplate; drop. Also remove "Do You Need Assistance?" etc; drop. Also remove "U.S. Citizenship may be required for certain positions." Actually we have US Citizenship Required for this Position: Yes earlier; we keep that as requirement. Now produce HTML. Structure:
About the role
Meet HII’s Newport News Shipbuilding With more than 25,000 employees – including third-, fourth- and even fifth-generation shipbuilders – HII’s Newport News Shipbuilding (NNS) division is the largest industrial employer in Virginia. We’re the sole designer, builder and refueler of U.S. Navy nuclear aircraft carriers and one of two providers of U.S. Navy nuclear submarines. Our diverse and innovative team of professionals ranges from skilled trades to project managers, engineers and software developers to solution architects, technical subject matter experts, and system users. We collaborate together at the forefront of technology, manufacturing, and integration of the most powerful and survivable naval ships in the world.
Responsibilities
The Role Performs operational duties in support of regulatory and/or Good Manufacturing Practice (GMP) compliance documentation; coordinating the verification, approval, and processing of document revisions; and tracking document activity to ensure timeliness and process efficiency.
Requirements
- High School/GED and 2 years of additional education and/or experience
- U.S. Citizenship required
Skills
- Regular and Consistent Attendance
- Ready to Work
- Adaptable to Changing Work Environments and Situations
- Adequate Technical Knowledge of Microsoft Office Programs
- Ability to Collaborate, Communicate and Cooperate with peers, customers, management and others
- Ability to Work Autonomously and Within Groups
- Strong Written and Verbal Communication Skills
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
Pay
Salary Range: $42,000.00 to $52,000.00
Schedule
Full-Time, 1st shift
Check if any content missing: The posting also mentions "Relocation: No relocation assistance available", "Virtual/Telework Opportunity: No - Not eligible for telework", "Travel Requirements: No", "Clearance Required: No - Clearance Not Required to Start". Those are minor metadata; we could fold into a short paragraph under Requirements or maybe a separate section like "Additional Details". But the instruction says only include sections when posting has real, specific content for it. Those are specific but maybe minor. Could we add a section "Additional Details"? Not in the allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create other headings. We could fold those minor metadata into Requirements or maybe a short paragraph under Requirements. But we already have Requirements list; we could add items like "No relocation assistance", "Not eligible for telework", "No travel required", "No clearance required". However those are not requirements but details. Could be okay to add as list items under Requirements? Might be stretching. Better to maybe add a shortafter Requirements that includes those details, but that would be prose not a list. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we could add a
under Requirements that includes those details. But we already have a
- for Requirements; we could add a
after the list. That's okay. But we need to avoid creating thin sections. Adding a paragraph under Requirements is fine. Similarly, we could add a short paragraph under Schedule about full-time etc. Already we have schedule. We need to ensure we don't duplicate content. Let's incorporate: After Requirements list, add a
with: "No relocation assistance available. Not eligible for telework. No travel required. No clearance required to start." That is prose. Now check if we missed any substantive content: "The anticipated salary range represents the estimated base pay for this role. Final compensation will be determined based on experience, qualifications, and other job-related factors, and may vary from the posted range". That's more detail about pay. We could include that in Pay section as prose after the salary range. So Pay section:
Salary Range: $42,000.00 to $52,000.00
The anticipated salary range represents the estimated base pay for this role. Final compensation will be determined based on experience, qualifications, and other job-related factors, and may vary from the posted range.
Now check if we missed any content about "Full-Time Shift: 1st". Already schedule. Now check if we missed any content about "Team: E08 E&D BUSINESS OPS Entity: Newport News Shipbuilding". That's metadata; could be folded into About the role? Already we have company description. Could add a short line about team/entity. But maybe not needed. We need to preserve ALL substantive information. The team and entity are substantive? Possibly minor metadata but still part of posting. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. So we can fold Team, Entity into a short paragraph maybe under About the role or Requirements. Let's add a short paragraph after About the role: "Team: E08 E&D BUSINESS OPS. Entity: Newport News Shipbuilding." That's prose. Now check if we missed any content about "US Citizenship Required for this Position: Yes". Already in Requirements. Now check if we missed any content about "Full-Time Shift: 1st Relocation: No relocation assistance available Virtual/Telework Opportunity: No - Not eligible for telework Travel Requirements: No Clearance Required: No - Clearance Not Required to Start". We covered relocation, telework, travel, clearance in the Requirements paragraph. Shift
- .
- Pay: Salary range. Use
- .
- Benefits: list of benefits. Use
- .
- Qualifications: maybe same as requirements? The distinction is fuzzy. We could combine. But we need to avoid thin sections. Perhaps we have Requirements (education/experience, citizenship) and Qualifications (maybe none separate). Could skip Qualifications if no distinct content.
- Skills: Nice to Have list: Regular and Consistent Attendance, Ready to Work, Adaptable..., Technical Knowledge of Microsoft Office, Ability to Collaborate..., Ability to Work Autonomously..., Strong Written and Verbal Communication Skills. That's a list of skills. Use
- for any list of duties/requirements/benefits. If it's not a list, we can use