Naval Architecture Intern

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the description. Given text: "Description Gibbs & Cox, a wholly owned subsidiary of Leidos, is the largest independent naval architecture and marine engineering firm in the United States. Since our founding in 1929, 24 classes of combatants and nearly 7,000 vessels have been built to Gibbs & Cox designs. We proudly support military and commercial clients in the U.S. and internationally with all phases of marine design, construction, and lifecycle management. Our passion is solving our customers’ 21st century maritime challenges with quality and integrity. As a Naval Architecture Intern in the naval architecture department, you will tackle new and evolving ship design and integration engineering challenges by applying naval architecture principles, techniques, calculations, procedures, and criteria.The projects executed within the team cover the full range of ship design phases from conceptual design through detail design, and post-delivery support. Your contributions will directly support the continued maturation of ship design solutions across all phases of design. Primary Responsibilities Work with hydrostatics including weight estimates and intact/damage stability assessments.Work with hydrodynamics such as hull design, resistance predictions, and seakeeping assessments.Work with arrangements such as general arrangements, compartment outfitting, aviation integration, and topside integration.Preparing and presenting technical reports and engineering documentation. Basic Qualifications Pursuing a bachelor’s degree in Naval Architecture or Marine Engineering.Proficiency in naval architecture software tools such as RHINO, GHS, SHCP, NavCAD, AutoCAD, and/or Microsoft Office Suite.Strong written and oral communication skills.Strong time management and organizational skills as an independent contributor.Ability to obtain and maintain a Secret Security Clearance.Active Secret Security Clearance preferred.U.S. Citizenship required. If you're looking for comfort, keep scrolling. At Leidos, we outthink, outbuild, and outpace the status quo — because the mission demands it. We're not hiring followers. We're recruiting the ones who disrupt, provoke, and refuse to fail. Step 10 is ancient history. We're already at step 30 — and moving faster than anyone else dares. Original Posting September 17, 2026 For U.S. Positions: While subject to change based on business needs, Leidos reasonably anticipates that this job requisition will remain open for at least 3 days with an anticipated close date of no earlier than 3 days after the original posting date as listed above. Pay Range Pay Range $48,100.00 - $86,950.00 The Leidos pay range for this job level is a general guideline onlyand not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law. About Leidos Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com. Pay And Benefits Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details are available at www.leidos.com/careers/pay-benefits. Securing Your Data Beware of fake employment opportunities using Leidos’ name. Leidos will never ask you to provide payment-related information during any part of the employment application process (i.e., ask you for money), nor will Leidos ever advance money as part of the hiring process (i.e., send you a check or money order before doing any work). Further, Leidos will only communicate with you through emails that are generated by the Leidos.com automated system – never from free commercial services (e.g., Gmail, Yahoo, Hotmail) or via WhatsApp, Telegram, etc. If you received an email purporting to be from Leidos that asks for payment-related information or any other personal information (e.g., about you or your previous employer), and you are concerned about its legitimacy, please make us aware immediately by emailing us at LeidosCareersFraud@leidos.com. If you believe you are the victim of a scam, contact your local law enforcement and report the incident to the U.S. Federal Trade Commission. Commitment to Non-Discrimination All qualified applicants will receive consideration for employment without regard to sex, race, ethnicity, age, national origin, citizenship, religion, physical or mental disability, medical condition, genetic information, pregnancy, family structure, marital status, ancestry, domestic partner status, sexual orientation, gender identity or expression, veteran or military status, or any other basis prohibited by law. Leidos will also consider for employment qualified applicants with criminal histories consistent with relevant laws. #Remote" We need to extract sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real specific content. - About the role: The description includes a paragraph about Gibbs & Cox and the intern role. That's about the role. So we can have About the role section with that prose. - Responsibilities: There's "Primary Responsibilities" list: Work with hydrostatics..., Work with hydrodynamics..., Work with arrangements..., Preparing and presenting technical reports... So we can list those as

• . - Requirements: Might be "Basic Qualifications" etc. But we also have Qualifications and Skills separate. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have "Basic Qualifications" list: Pursuing a bachelor’s degree in Naval Architecture or Marine Engineering. Proficiency in naval architecture software tools such as RHINO, GHS, SHCP, NavCAD, AutoCAD, and/or Microsoft Office Suite. Strong written and oral communication skills. Strong time management and organizational skills as an independent contributor. Ability to obtain and maintain a Secret Security Clearance. Active Secret Security Clearance preferred. U.S. Citizenship required. These could go under Qualifications (or Requirements). The distinction: Requirements often are mandatory; Qualifications maybe preferred. But we can put them under Qualifications. However we also have a separate Skills heading; we could put software tools and communication etc under Skills. But we need to avoid duplication. Let's think: The posting includes "Basic Qualifications" which includes education, software proficiency, communication, time management, security clearance, citizenship. Those could be considered Qualifications. Skills could be separate: maybe "Proficiency in naval architecture software tools such as RHINO, GHS, SHCP, NavCAD, AutoCAD, and/or Microsoft Office Suite." and "Strong written and oral communication skills." and "Strong time management and organizational skills as an independent contributor." Those are skills. But we can also put them under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we might combine Qualifications and Skills into one section? But we have to use headings only when there is real specific content. We could have Qualifications section containing education, clearance, citizenship. Skills section containing software tools, communication, time management. That would be two sections. But we also have Requirements heading; maybe we can put the security clearance and citizenship under Requirements (since they are requirements). However we have to avoid duplication. Let's see typical job posting: Requirements often include education, experience, clearance, citizenship. Qualifications may be preferred qualifications. Skills may be technical skills. But we have only one list of basic qualifications. We could split: Requirements: U.S. Citizenship required; Ability to obtain and maintain a Secret Security Clearance; Active Secret Security Clearance preferred. Qualifications: Pursuing a bachelor’s degree in Naval Architecture or Marine Engineering. Skills: Proficiency in naval architecture software tools such as RHINO, GHS, SHCP, NavCAD, AutoCAD, and/or Microsoft Office Suite; Strong written and oral communication skills; Strong time management and organizational skills as an independent contributor. That seems reasonable. Now Benefits: There's a "Pay And Benefits" section: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also earlier there is a generic statement about compensation packages. So we can list those benefits. Pay: There's a Pay Range: $48,100.00 - $86,950.00. Also note that the pay range is a guideline. We should include the pay range as content. So Pay section with that range. Schedule: Not mentioned anywhere. There's no schedule info (full-time, part-time, remote?). There's a "#Remote" at the end but that's a hashtag maybe indicating remote? The posting includes "#Remote" at the very end after the non-discrimination statement. That could indicate the position is remote. However it's just a hashtag; not explicit schedule. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, we have no explicit statement about schedule (like full-time, part-time, hours). The "#Remote" could be considered a schedule/location indicator but not schedule. Safer to omit Schedule section. Now we need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Use

  for each heading. Use

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

    for prose. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate/navigation/legal/EEO/scam-warning boilerplate, duplicated lines, and application instructions. We need to ensure we keep all substantive info: The description about Gibbs & Cox, the role, responsibilities, basic qualifications (education, clearance, citizenship), skills (software tools, communication, time management), benefits (competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement), pay range. We also have some other sentences like "If you're looking for comfort, keep scrolling..." etc. That's motivational fluff but maybe considered boilerplate? It's not a standard boilerplate but it's promotional language. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That fluff is not explicitly listed to remove, but it's not substantive info about the job; it's more marketing. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The fluff is not substantive about the job; but it's part of the posting. Should we keep it? The instruction says remove boilerplate etc. It doesn't say remove motivational fluff. But we should aim to keep only substantive info about the role. The fluff like "If you're looking for comfort, keep scrolling. At Leidos, we outthink..." is not substantive about the role; it's more company culture. Could be considered boilerplate? Not sure. Safer to keep it? But the instruction says "Prefer a few substantive sections over many thin ones." So we could include that fluff in About the role section as prose. However it's not about the role; it's about Leidos culture. Might be okay to include in About the role? The About the role section currently includes the description of Gibbs & Cox and the intern role. We could add that fluff as part of that prose. But it's not