MECH TECH D 2 (ELECTRICIAN)

We need to output HTML fragment with sections: About the role? The posting includes a description: "Meet HII’s Newport News Shipbuilding ..." That's about the company. Then "The Role" description. Then "Must Have" and "Nice to Have". Then "Why HII" includes benefits description. Also there is "We offer comprehensive benefits including: ..." So we need sections: About the role? Actually "About the role" heading for description of role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have real content. We have: - About the role? The posting includes "The Role" description: "Repairs, constructs, installs, troubleshoots, and maintains routine electrical systems and equipment. Modifies, aligns, calibrates, designs, programs, installs, tests, troubleshoots and maintains routine electrical systems and equipment to include control systems, a wide variety of industrial infrastructure and production equipment. Cuts, threads, bends, couples, and straps conduit as required. Troubleshoots electrical malfunctions, inspects circuits and wiring for shielding and grounding, and tests electrical equipment for safety and efficiency." That's responsibilities/duties. Could be under "Responsibilities". Also "About the role" could be a brief overview, but we have that content. We could use "Responsibilities" heading. - Requirements/Qualifications: "Must Have High School diploma or equivalent and 2 years additional education and/or related experience; Apprentice graduate/ Associate's Degree in relevant discipline and 1 year of related experience. May require certification." Also "Nice to Have" maybe skills? There's no explicit nice to have content besides maybe nothing? The posting says "Nice to Have" heading but no content after? Actually after "Nice to Have" there is "Why HII". So "Nice to Have" section is empty; we should not include it if no specific content. So we omit Nice to Have. - 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." That's benefits content. So we can have Benefits heading. - About the company: "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. Want to be part of the team? Apply today! We look forward to meeting you." That's about the company; could be under "About the role"? Actually "About the role" is not appropriate; maybe we could use a heading like "About the role" but that's not correct. The instruction list includes "About the role" as an example heading. We could use that for company overview? But better to use "About the role" for role description? However we already used Responsibilities for role duties. Could also have "About the role" as a brief overview preceding responsibilities. But we have no separate overview besides the role description. The "The Role" heading is basically responsibilities. So we could treat that as "About the role". But the instruction says use headings like About the role, Responsibilities, etc. We can choose whichever fits. We have also metadata: Req ID, Team, Entity, US Citizenship Required, Full-Time Shift: Multiple, Relocation: No relocation assistance available, Virtual/Telework Opportunity: No - Not eligible for telework, Travel Requirement: No, Clearance Required: No - Clearance Not Required to Start. These are minor metadata; we should fold into a short

or drop it. Probably we can include a short paragraph at top with that info. We must not include boilerplate like EEO, accommodation, etc. Remove those lines. Thus final HTML:

Req ID: 49821 | Team: C100 PRODUCTION | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time | Shift: Multiple | Relocation: No relocation assistance available | Telework: Not eligible | Travel: No | Clearance: Not required.

Then sections:

About the role

maybe with a brief description: The role involves repairing, constructing, installing, troubleshooting, and maintaining routine electrical systems and equipment... Actually that's responsibilities. Could be under About the role. But we also have Responsibilities heading; we could put the detailed duties under Responsibilities. Let's decide: - About the role: short summary: "This position focuses on electrical systems work for shipbuilding production, including installation, maintenance, troubleshooting, and related tasks." - Responsibilities: list of duties as bullet points. - Requirements: list of must-have qualifications. - Benefits: list of benefits. We must not create Pay or Schedule sections because not specified. We must not include Nice to Have because no content. We must preserve all substantive information: include the Must Have details, the Nice to Have heading is present but no content; we should not create a section for it. We must include the "Why HII" content? That includes benefits and some motivational text. The benefits are already captured; the motivational text about building future etc could be considered part of About the company? But we already have About the role. Could we add a section "About HII"? Not in allowed headings list but we could use About the role? Actually the allowed headings list is examples; we could also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; but we could also use other headings if needed? It says use

for section headings (e.g. ...). Likely we should stick to those examples. So we can use About the role, Responsibilities, Requirements, Benefits. Possibly also Qualifications (similar to Requirements). We'll use Requirements. We need to preserve all substantive information: the "Why HII" paragraph about building future etc is substantive but not covered by those headings. Could we put it under About the role? That seems odd. Maybe we can put it under About the role as a company overview. But the heading "About the role" is for role, not company. However we could treat it as "About the role" meaning about the role at HII. Might be okay. Alternatively we could create a section "About HII" but not in list; risk of violating instruction. Safer to incorporate that text into About the role or Responsibilities? The "Why HII" section is more about company culture and benefits; benefits we already have; the rest is motivational. Could be omitted? But instruction says preserve ALL substantive information; we cannot omit motivational text. So we need to include it somewhere. Perhaps we can add a section "About the role" that includes both role description and company overview. That would be substantive. Thus:

About the role

Meet HII’s Newport News Shipbuilding ... Want to be part of the team? Apply today! We look forward to meeting you.

The Role Repairs, constructs, installs, troubleshoots, and maintains routine electrical systems and equipment. Modifies, aligns, calibrates, designs, programs, installs, tests, troubleshoots and maintains routine electrical systems and equipment to include control systems, a wide variety of industrial infrastructure and production equipment. Cuts, threads, bends, couples, and straps conduit as required. Troubleshoots electrical malfunctions, inspects circuits and wiring for shielding and grounding, and tests electrical equipment for safety and efficiency.

But that duplicates content; we could split. Better: About the role paragraph: company overview. Then Responsibilities heading with duty list. Let's extract company overview: "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. Want to be part of the team? Apply today! We look forward to meeting you." That's substantive. Now responsibilities: list of duties as bullet points. We need to convert the sentences into list items. Duties: - Repairs, constructs, installs, troubleshoots, and maintains routine electrical systems and equipment. - Modifies, aligns, calibrates, designs, programs, installs, tests, troubleshoots and maintains routine electrical systems and equipment to include control systems, a wide variety of industrial infrastructure and production equipment. - Cuts, threads, bends, couples, and straps conduit as required. - Troubleshoots electrical malfunctions, inspects circuits and wiring for shielding and grounding, and tests electrical equipment for safety and efficiency. We could combine first two but keep as separate. Now Requirements: Must Have: "High School diploma or equivalent and 2 years additional education and/or related experience; Apprentice graduate/ Associate's Degree in relevant discipline and 1 year of related experience. May require certification." We can list as bullet points: - High school diploma or equivalent and 2 years of additional education and/or related experience. - Apprentice graduate or Associate's degree in a relevant discipline and 1 year of related experience. - May require certification. Now Benefits: list as bullet points from the benefits sentence. 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 - More (some benefits may vary depending on specific division or work location) We could include note about variation. Now we need to include metadata paragraph at top. We must not include boilerplate like EEO, accommodation, etc. Remove those lines. Now output only HTML fragment. Let's craft:

Req ID: 49821 | Team: C100 PRODUCTION | Entity: Newport News Shipbuilding | US Citizenship Required: Yes | Full-Time | Shift: Multiple | Relocation: No relocation assistance available | Telework: Not eligible | Travel: No | Clearance: Not required.

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