Jobs · Engineering · Mississippi

ENGINEER ELECTRICAL 3

HII · Pascagoula, MS · 3 days ago
EngineeringFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role (the description of the role) - Responsibilities (what the role does) - Requirements (must-have qualifications) - Qualifications (nice-to-have) - Benefits (what HII offers) - There's also metadata like Req ID, Team, Entity, Citizenship, Shift, Relocation, Telework, Travel - these should be folded into a short

or dropped. Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use
  • for lists,

    for prose - Do NOT repeat job title as heading (the page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences Now, let's parse the content: Metadata: - Req ID: 50364 - Team: 57 Research and Development - Entity: Ingalls Shipbuilding - US Citizenship Required: Yes - Full-Time Shift: 1st - Relocation: No relocation assistance available - Virtual/Telework Opportunity: No - Not eligible for telework - Travel Requirement: No This metadata can be folded into a short

    at the beginning or end. Since it's minor metadata, I'll include it as a paragraph. About the role: There's a paragraph "We're building tomorrow's fleet today..." and then "The Role" section: "Researches, develops, designs, and tests electrical components, equipment, systems, and networks. Designs electrical equipment, facilities, components, products, and systems for commercial, industrial, and domestic purposes. Technical Point of Contact (TPOC) – Cybersecurity and C5ISR. The candidate must be able to serve as a Technical Point of Contact for future platforms and for current platforms as required. This role includes providing technical support and guidance in the areas of Cybersecurity and Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems for Ingalls-built ships." That's the role description. Could be under "About the role" heading. Responsibilities: The role description includes duties. Could be listed as responsibilities. But the posting doesn't have a separate "Responsibilities" section; it's embedded. I'll extract the duties into a list under Responsibilities. Requirements: "Must Have Bachelor of Science degree in Engineering from an ABET accredited university and 5 years of experience -or- Master of Science degree in Engineering from an ABET accredited university and 3 years of experience or PHD in Engineering from an ABET accredited university and 0 year of experience" That's a requirement. Also US Citizenship required. That's a requirement. Qualifications: "Nice to Have" section: "Capable of serving as a Technical Point of Contact (TPOC) for future platforms and for current platforms as required. Provide technical support and guidance in the areas of Cybersecurity and Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems for Ingalls-built ships. Demonstrated experience with US Navy combat systems equipment, ship operations, and Cybersecurity. Able to present complex technical information clearly and coherently to senior leadership and potential customers." That's nice-to-have qualifications. 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. There's also "Why HII" section with company description. That could be "About the company" but the rules say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why HII" is not in the list, but could be considered "About the company". However, the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., so we can use other headings if appropriate. But the instruction: "include a section ONLY when the posting has real, specific content for it". The "Why HII" section has substantive content about the company and benefits. But benefits are already covered. The company description could be under "About the company" but the rules don't explicitly forbid it. However, the user said "Prefer a few substantive sections over many thin ones." So maybe we can include a "About the company" section? But the example headings don't include it. The rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the preferred headings. But we can use others if needed. However, the "Why HII" section includes benefits and company culture. Since we already have Benefits, we could fold the company description into a paragraph before sections or omit. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The EEO statement is at the end: "All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity or expression, sexual orientation, national origin, physical or mental disability, age, or veteran status or any other basis protected by federal, state, or local law. U.S. Citizenship may be required for certain positions." That's boilerplate, remove. Also "Do You Need Assistance?" section about reasonable accommodation - that's application instruction, remove. So we need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly also a metadata paragraph. Let's structure:

    Req ID: 50364 | Team: 57 Research and Development | Entity: Ingalls Shipbuilding | US Citizenship Required: Yes | Shift: 1st | Relocation: No relocation assistance | Telework: Not eligible | Travel: No

    About the role

    We’re building tomorrow’s fleet today. With more than 11,000 employees, HII’s Ingalls Shipbuilding Division is the largest manufacturing employer in Mississippi and a major contributor to the economic growth of Alabama. For nearly 85 years, we’ve designed, built, and maintained amphibious ships, destroyers, and cutters for the U.S. Navy and the U.S. Coast Guard. As the largest supplier of U.S. Navy surface combatants, we’re simultaneously building four classes of ships and have pioneered the development and production of technologically advanced, highly capable ships for the surface navy fleet for decades.

    The role researches, develops, designs, and tests electrical components, equipment, systems, and networks. Designs electrical equipment, facilities, components, products, and systems for commercial, industrial, and domestic purposes. Serves as a Technical Point of Contact (TPOC) for Cybersecurity and C5ISR, providing technical support and guidance in the areas of Cybersecurity and Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems for Ingalls-built ships.

    Responsibilities

    • Research, develop, design, and test electrical components, equipment, systems, and networks
    • Design electrical equipment, facilities, components, products, and systems for commercial, industrial, and domestic purposes
    • Serve as Technical Point of Contact (TPOC) for Cybersecurity and C5ISR for future and current platforms
    • Provide technical support and guidance in Cybersecurity and Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) systems for Ingalls-built ships

    Requirements

    • U.S. Citizenship required
    • Bachelor of Science degree in Engineering from an ABET accredited university and 5 years of experience, OR Master of Science degree in Engineering from an ABET accredited university and 3 years of experience, OR PhD in Engineering from an ABET accredited university and 0 years of experience

    Qualifications

    • Capable of serving as a Technical Point of Contact (TPOC) for future and current platforms
    • Provide technical support and guidance in Cybersecurity and C5ISR systems for Ingalls-built ships
    • Demonstrated experience with U.S. Navy combat systems equipment, ship operations, and Cybersecurity
    • Able to present complex technical information clearly and coherently to senior leadership and potential customers

    Benefits

    • Medical, prescription drug, dental, and vision plan choices
    • On-site health centers and tele-medicine
    • Wellness resources and employee assistance programs
    • Savings plan options (401K) and financial education and planning tools
    • Life insurance
    • Tuition reimbursement
    • Employee discounts
    • Early childhood and post-secondary education scholarships
    • Additional benefits may vary by division or work location
    Note: The "Why HII" paragraph about company culture and values is not included as a separate section because it's somewhat generic. But it does have specific info about the company. However, the rules say "Preserve ALL substantive information". The "Why HII" paragraph includes: "We build the world’s most powerful, survivable naval ships and defense technology solutions that safeguard our seas, sky, land, space and cyber. HII’s diverse workforce includes skilled tradespeople; artificial intelligence, machine learning (AI/ML) experts; engineers; technologists; scientists; logistics experts; and business administration professionals. Recognized as one of America’s top large company employers, we are a values and ethics driven organization that puts people’s safety and well-being first. Regardless of your role or where you serve, at HII, you’ll find a supportive and welcoming environment, competitive benefits, and valuable educational and training programs for continual career growth at every stage of your career. Working at HII is more than a job - it’s an opportunity to build a future." That is substantive information about the company. Could be included under "About the company" heading. But the example headings don't include that. However, the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we cannot use other headings. But the instruction: "include a section ONLY when the posting has real, specific content for it". The "Why HII" section has real content. I think we should include it as "About the company" or "Why HII". But the user might expect only the example head

Similar jobs

Electrical Engineer

CollaberaLos Angeles, CA· 1 mo ago
Engineering$28–$30/hrapply on collabera.com

Electrical Engineer

ActalentKirkland, WA· 1 mo ago
Engineering$60–$75/hrapply on ars2.equest.com

Electrical Engineer

ArcadisCincinnati, OH· 1 mo ago
OTHR$105k–$150k/yrapply on jobs.arcadis.com

Electrical Engineer

Huitt-Zollars, Inc.Fort Worth, TX· 1 mo ago
Engineeringapply on recruiting.paylocity.com