Engineer I
American Bureau of Shipping (ABS) · Houston, TX · 1 mo ago
HybridEngineeringFull-time
We need to output HTML fragment with sections: About the role? Actually the job description includes "Job Description" then paragraphs. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content.
We have:
- About the role: The initial paragraph describing the role: "ABS is seeking an Engineer I to assist with the modeling, review, and analysis of vessel structures, stability, load line, and hull strength for ships and offshore floating structures, and to verify compliance with applicable Rules, Regulations, and contract commitments. This position will work under the supervision of experienced engineers or an engineering manager and will support a range of engineering assignments of varying scope and complexity. Through broader and more technically challenging work assignments, the ideal candidate will develop a thorough understanding of policies, methods, and procedures. Depending on business needs, the Engineer I may also support time-sensitive damage assessment activities, routine emergency response drills, and technical service requests related to vessel incidents."
That's about the role.
- Responsibilities: The "What You Will Do" bullet list (actually sentences). We need to extract each duty as list items.
- Requirements: Possibly "What You Will Need Education and Experience" includes education and experience. Could be Requirements.
- Qualifications: maybe "Knowledge, Skills, And Abilities" could be Skills. Also "It Would Be Nice If You Had" could be Qualifications? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Benefits section: "About Our Benefits" with list.
Pay: Not mentioned. So we should NOT include Pay section.
Schedule: Not mentioned. So omit.
Qualifications: Could be "Education and Experience" maybe as Requirements? Actually typical: Requirements = education+experience; Qualifications = maybe certifications, licenses; Skills = knowledge, skills, abilities. But we can decide.
We have "Education and Experience" bullet: B.S. degree ...; M.S. may be preferred; 0 to 5 years related experience; etc. That's qualifications.
We have "Knowledge, Skills, And Abilities": list of knowledge, skills, abilities.
We have "It Would Be Nice If You Had": professional license, experience supporting time-sensitive assessments.
We could map:
- Requirements: Education and Experience (maybe plus exposure to vessel stability calculations etc). Actually the "Education and Experience" includes also "Experience or exposure to vessel stability calculations and ship and/or offshore floating structures preferred." That's part of requirements.
- Qualifications: maybe "It Would Be Nice If You Had" (preferred qualifications). But we need to ensure we don't create empty sections.
- Skills: Knowledge, Skills, And Abilities.
We also have "Reporting Relationships" and "Notice" etc but those are boilerplate? Reporting Relationships maybe not required heading; we could ignore as not in list. The instruction: Use headings only for those listed; we can ignore other headings.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all substantive content from the posting, but we can reorganize under headings.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Notice" about export control? That's legal; maybe considered boilerplate? It's substantive? It's about export control; might be considered legal but it's part of job description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The export control notice is legal; likely should be removed. Also "About Us" maybe not required heading; but it's substantive about company. Could be included under About the role? Might be considered boilerplate? It's about the company; not required heading but we could keep as a paragraph under About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate About Us into About the role? But About the role already has description; we could add a paragraph about company under About the role? Might be okay.
But we must not invent headings; we can only use those headings. So we need to place all content under those headings. If some content doesn't fit, we could still put under About the role or Responsibilities etc. But we must preserve all substantive information.
Let's extract substantive content:
1. Role description (first paragraph).
2. Responsibilities (What You Will Do) list:
- Under supervision, perform detailed engineering reviews and analyses related to ship structures, stability, load line, hull strength for compliance.
- Develop analysis models and prepare calculations using first principles and computer-aided engineering tools to predict structural integrity and stability.
- Perform classical stress calculations, finite element stress analysis, fatigue analysis, and stability analyses, as assigned.
- Use finite element modeling techniques, primarily FEMAP for finite element model development and NASTRAN finite element solution, as well as stability software such as GHS, NAPA, or equivalent tools.
- Prepare technically accurate and timely reports, calculations, and responses for review by experienced engineers or managers.
- Assist in resolving technical problems that may involve limited information, conflicting requirements, or time constraints.
- Communicate the status of assigned work to appropriate team members to support quality and timely delivery of services.
- Work collaboratively with other engineers to identify and resolve technical issues.
- May support emergency response activities, including routine drills, rotating standby assignments, and response to client service requests, as required.
- Maintain the technical quality, content, consistency, continuity, and timeliness of assigned work in accordance with ABS standards.
- Implement and maintain ABS Quality System requirements relative to responsibilities after undergoing ABS Quality System training.
- Implements and maintains ABS Quality System requirements relative to responsibilities after undergoing ABS Quality System training. (duplicate sentence; we should deduplicate.)
3. Education and Experience (What You Will Need):
- B.S. degree in Naval Architecture, Ocean Engineering, Civil Engineering, Structural Engineering, Mechanical Engineering, or other related disciplines; an M.S. degree may be preferred.
- 0 to 5 years of related engineering experience, or relevant coursework or research, in a shipyard, design/consulting office, shipping/oil company, offshore industry, government support environment, or classification society.
- Experience or exposure to vessel stability calculations and ship and/or offshore floating structures preferred.
- Demonstrated computer literacy in engineering software required.
- Experience with software related to stability and engineering analysis such as GHS, NAPA, Hecsalv, FEMAP, NASTRAN, or equivalent software preferred.
- Exposure to Finite Element Method through coursework, supervised research, or practical application preferred.
4. Knowledge, Skills, And Abilities:
- Knowledge of related technical disciplines required.
- The ability to identify, analyze, and propose solutions to problems (i.e., the competence to demonstrate complex problem-solving skills).
- Good command of the English language.
- Ability to communicate orally and in writing.
- Ability to work well with others and perform effectively within schedule constraints.
- Ability to work both independently and as part of a team, once trained.
- Familiarity with the ABS Health, Safety, Quality & Environmental Management Systems (applicable to ABS internal candidates only).
- Ability to obtain a working knowledge of the ABS Health, Safety, Quality, and Environmental Management Systems.
5. It Would Be Nice If You Had:
- Professional or chartered engineer license.
- Experience supporting time-sensitive engineering assessments or emergency response activities.
6. Reporting Relationships: The incumbent will report to a senior-level engineer or a technical manager. This position has no direct reports. (Could be placed under About the role or maybe under Responsibilities? Might be considered part of role description.)
7. About Us: paragraph about ABS history, mission, etc. (Could be placed under About the role or maybe separate but we don't have heading for About Us; we could incorporate into About the role.)
8. Benefits: list of benefits.
9. Equal Opportunity: boilerplate; remove.
10. Notice about third-party agency: legal; remove.
11. Other: job description not intended to be all-inclusive; maybe keep? It's somewhat boilerplate but could be considered substantive? Probably remove as it's generic.
We need to output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also include a short paragraph for metadata like Reporting Relationships under About the role? Or we could add a separate section? Not allowed headings besides those. So we can put Reporting Relationships under About the role as a paragraph.
We must not include Pay or Schedule.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now construct HTML:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse content.
We have:
- About the role: The initial paragraph describing the role: "ABS is seeking an Engineer I to assist with the modeling, review, and analysis of vessel structures, stability, load line, and hull strength for ships and offshore floating structures, and to verify compliance with applicable Rules, Regulations, and contract commitments. This position will work under the supervision of experienced engineers or an engineering manager and will support a range of engineering assignments of varying scope and complexity. Through broader and more technically challenging work assignments, the ideal candidate will develop a thorough understanding of policies, methods, and procedures. Depending on business needs, the Engineer I may also support time-sensitive damage assessment activities, routine emergency response drills, and technical service requests related to vessel incidents."
That's about the role.
- Responsibilities: The "What You Will Do" bullet list (actually sentences). We need to extract each duty as list items.
- Requirements: Possibly "What You Will Need Education and Experience" includes education and experience. Could be Requirements.
- Qualifications: maybe "Knowledge, Skills, And Abilities" could be Skills. Also "It Would Be Nice If You Had" could be Qualifications? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have Benefits section: "About Our Benefits" with list.
Pay: Not mentioned. So we should NOT include Pay section.
Schedule: Not mentioned. So omit.
Qualifications: Could be "Education and Experience" maybe as Requirements? Actually typical: Requirements = education+experience; Qualifications = maybe certifications, licenses; Skills = knowledge, skills, abilities. But we can decide.
We have "Education and Experience" bullet: B.S. degree ...; M.S. may be preferred; 0 to 5 years related experience; etc. That's qualifications.
We have "Knowledge, Skills, And Abilities": list of knowledge, skills, abilities.
We have "It Would Be Nice If You Had": professional license, experience supporting time-sensitive assessments.
We could map:
- Requirements: Education and Experience (maybe plus exposure to vessel stability calculations etc). Actually the "Education and Experience" includes also "Experience or exposure to vessel stability calculations and ship and/or offshore floating structures preferred." That's part of requirements.
- Qualifications: maybe "It Would Be Nice If You Had" (preferred qualifications). But we need to ensure we don't create empty sections.
- Skills: Knowledge, Skills, And Abilities.
We also have "Reporting Relationships" and "Notice" etc but those are boilerplate? Reporting Relationships maybe not required heading; we could ignore as not in list. The instruction: Use headings only for those listed; we can ignore other headings.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all substantive content from the posting, but we can reorganize under headings.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Notice" about export control? That's legal; maybe considered boilerplate? It's substantive? It's about export control; might be considered legal but it's part of job description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The export control notice is legal; likely should be removed. Also "About Us" maybe not required heading; but it's substantive about company. Could be included under About the role? Might be considered boilerplate? It's about the company; not required heading but we could keep as a paragraph under About the role? The instruction: "Prefer a few substantive sections over many thin ones." We could incorporate About Us into About the role? But About the role already has description; we could add a paragraph about company under About the role? Might be okay.
But we must not invent headings; we can only use those headings. So we need to place all content under those headings. If some content doesn't fit, we could still put under About the role or Responsibilities etc. But we must preserve all substantive information.
Let's extract substantive content:
1. Role description (first paragraph).
2. Responsibilities (What You Will Do) list:
- Under supervision, perform detailed engineering reviews and analyses related to ship structures, stability, load line, hull strength for compliance.
- Develop analysis models and prepare calculations using first principles and computer-aided engineering tools to predict structural integrity and stability.
- Perform classical stress calculations, finite element stress analysis, fatigue analysis, and stability analyses, as assigned.
- Use finite element modeling techniques, primarily FEMAP for finite element model development and NASTRAN finite element solution, as well as stability software such as GHS, NAPA, or equivalent tools.
- Prepare technically accurate and timely reports, calculations, and responses for review by experienced engineers or managers.
- Assist in resolving technical problems that may involve limited information, conflicting requirements, or time constraints.
- Communicate the status of assigned work to appropriate team members to support quality and timely delivery of services.
- Work collaboratively with other engineers to identify and resolve technical issues.
- May support emergency response activities, including routine drills, rotating standby assignments, and response to client service requests, as required.
- Maintain the technical quality, content, consistency, continuity, and timeliness of assigned work in accordance with ABS standards.
- Implement and maintain ABS Quality System requirements relative to responsibilities after undergoing ABS Quality System training.
- Implements and maintains ABS Quality System requirements relative to responsibilities after undergoing ABS Quality System training. (duplicate sentence; we should deduplicate.)
3. Education and Experience (What You Will Need):
- B.S. degree in Naval Architecture, Ocean Engineering, Civil Engineering, Structural Engineering, Mechanical Engineering, or other related disciplines; an M.S. degree may be preferred.
- 0 to 5 years of related engineering experience, or relevant coursework or research, in a shipyard, design/consulting office, shipping/oil company, offshore industry, government support environment, or classification society.
- Experience or exposure to vessel stability calculations and ship and/or offshore floating structures preferred.
- Demonstrated computer literacy in engineering software required.
- Experience with software related to stability and engineering analysis such as GHS, NAPA, Hecsalv, FEMAP, NASTRAN, or equivalent software preferred.
- Exposure to Finite Element Method through coursework, supervised research, or practical application preferred.
4. Knowledge, Skills, And Abilities:
- Knowledge of related technical disciplines required.
- The ability to identify, analyze, and propose solutions to problems (i.e., the competence to demonstrate complex problem-solving skills).
- Good command of the English language.
- Ability to communicate orally and in writing.
- Ability to work well with others and perform effectively within schedule constraints.
- Ability to work both independently and as part of a team, once trained.
- Familiarity with the ABS Health, Safety, Quality & Environmental Management Systems (applicable to ABS internal candidates only).
- Ability to obtain a working knowledge of the ABS Health, Safety, Quality, and Environmental Management Systems.
5. It Would Be Nice If You Had:
- Professional or chartered engineer license.
- Experience supporting time-sensitive engineering assessments or emergency response activities.
6. Reporting Relationships: The incumbent will report to a senior-level engineer or a technical manager. This position has no direct reports. (Could be placed under About the role or maybe under Responsibilities? Might be considered part of role description.)
7. About Us: paragraph about ABS history, mission, etc. (Could be placed under About the role or maybe separate but we don't have heading for About Us; we could incorporate into About the role.)
8. Benefits: list of benefits.
9. Equal Opportunity: boilerplate; remove.
10. Notice about third-party agency: legal; remove.
11. Other: job description not intended to be all-inclusive; maybe keep? It's somewhat boilerplate but could be considered substantive? Probably remove as it's generic.
We need to output HTML with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also include a short paragraph for metadata like Reporting Relationships under About the role? Or we could add a separate section? Not allowed headings besides those. So we can put Reporting Relationships under About the role as a paragraph.
We must not include Pay or Schedule.
We need to ensure we don't include filler like "commensurate with experience" etc. Not present.
Now construct HTML:
About the role
... role description ...
Reporting Relationships: The incumbent will report to a senior-level engineer or a technical manager. This position has no direct reports.
About Us: ...
maybe combine. But we should not repeat "About Us" heading; just include as paragraph. Better to keep About the role paragraph includes role description and maybe About Us after. Now Responsibilities:Responsibilities
- ... each duty
Requirements
- ... education/experience items
Skills
- ... knowledge, skills, abilities
Benefits
- ... benefits