Project Engineer, Gas Pipeline

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, job title: Gas Pipeline Project Engineer (implied). Not to repeat as heading. We need sections: - About the role: likely description paragraph about company and role. The posting includes a description: "Since 1980, CobbFendley has been committed..." and "Are You Ready To Join Our Block And Advance Your Career?" etc. That's about the role/company. So we can put that in

About the role

with

containing that prose. - Responsibilities: there is a "Responsibilities" heading with bullet-like items. We need to extract each bullet as

. The text after "Responsibilities" includes sections like "Design + Analysis //Complete entire design..." etc. We need to parse each bullet. Let's extract responsibilities: From posting: Responsibilities Design + Analysis //Complete entire design and analysis for a simple project, ensure latest manual and criteria are being met, sign and seal plans. Work with project team to ensure tasks design and analysis tasks are coordinated. Compliance + Quality //Adhere to Company QA/QC processes and procedures and review work by others. Understand general contract language and risk assessments and mitigation. Communication + Collaboration //Work with supervisor, project manager, task leads, and various internal personnel to complete assignments within discipline and other disciplines. Lead meetings and follow up documentation. Training, Learning + Advancement //Attend internal or external training. Assist with onboarding and training various types of staff. Client + Internal Satisfaction //Work with clients daily, problem solve issues and escalate concerns when needed. Set and adhere to project schedule, attend client meetings, assist with marketing and project interviews, general understanding of financial management to ensure profitability. Technical //Support Senior Project Managers with engineering tasks and project management for various gas utility relocation projects, HDD design, system improvement, gate & district regulator station design, regulator relief selection, and sizing. Apply technical expertise and be able to work with a project team on a variety of applications ranging from feasibility studies to final as-built maintenance records. Assist in evaluation and solution of potential field problems. Motivated to learn in a dynamic environment with short project deadlines. We need to turn each line into

. Some lines have double slash comments; we can keep the text after // as description. Probably combine the heading before // and the description. We'll produce list items like:

Design + Analysis: Complete entire design and analysis for a simple project, ensure latest manual and criteria are being met, sign and seal plans. Work with project team to ensure tasks design and analysis tasks are coordinated.

But note there are two sentences for Design + Analysis: first sentence after //, then second line "Work with project team...". We'll combine. Similarly for Compliance + Quality: "Adhere to Company QA/QC processes and procedures and review work by others. Understand general contract language and risk assessments and mitigation." Communication + Collaboration: "Work with supervisor, project manager, task leads, and various internal personnel to complete assignments within discipline and other disciplines. Lead meetings and follow up documentation." Training, Learning + Advancement: "Attend internal or external training. Assist with onboarding and training various types of staff." Client + Internal Satisfaction: "Work with clients daily, problem solve issues and escalate concerns when needed. Set and adhere to project schedule, attend client meetings, assist with marketing and project interviews, general understanding of financial management to ensure profitability." Technical: "Support Senior Project Managers with engineering tasks and project management for various gas utility relocation projects, HDD design, system improvement, gate & district regulator station design, regulator relief selection, and sizing. Apply technical expertise and be able to work with a project team on a variety of applications ranging from feasibility studies to final as-built maintenance records. Assist in evaluation and solution of potential field problems. Motivated to learn in a dynamic environment with short project deadlines." We'll produce

• ...
etc. - Requirements: there is a "Requirements" heading with subheadings EDUCATION, REGISTRATION, CERTIFICATION and EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA). We need to capture content. Under EDUCATION, REGISTRATION, CERTIFICATION: "The successful candidate’s most important qualifications include the following. Bachelor’s degree in a civil or related engineering discipline, required. Registration and designation as an Engineer in Training (EIT), required." Under EXPERIENCE + KNOWLEDGE SKILLS ABILITY (KSA): "Proficient // Solid understanding and substantial experience; works independently and efficiently. 3+ years of professional experience, EIT may be required. Knowledge of standard engineering and scientific techniques, procedures, and criteria in carrying out tasks. Familiarity with CobbFendley’s QA/QC Management System.Skills including use of industry-standard computer software for the position (i.e., software such as CADD, HCS, AutoCAD, MicroStation, GIS, and Hydrologic/Hydraulic models).Ability to use spreadsheets, word processing, and standard office software." We need to parse into list items. Probably separate items: - Bachelor’s degree in a civil or related engineering discipline, required. - Registration and designation as an Engineer in Training (EIT), required. - 3+ years of professional experience (EIT may be required). - Solid understanding and substantial experience; works independently and efficiently. - Knowledge of standard engineering and scientific techniques, procedures, and criteria in carrying out tasks. - Familiarity with CobbFendley’s QA/QC Management System. - Skills including use of industry-standard computer software for the position (i.e., software such as CADD, HCS, AutoCAD, MicroStation, GIS, and Hydrologic/Hydraulic models). - Ability to use spreadsheets, word processing, and standard office software. But note "Proficient // Solid understanding and substantial experience; works independently and efficiently." So the proficiency description is the solid understanding etc. We'll treat as separate bullet. We'll produce
• ...
. - Qualifications: The posting didn't have a separate "Qualifications" heading besides the requirements. However there is a line: "The successful candidate’s most important qualifications include the following." That's under Requirements. We could treat Qualifications as same as Requirements? But we need to include a section only if posting has real specific content for it. There's no separate Qualifications heading besides that sentence. Might combine with Requirements. However we could still create a Qualifications section with that sentence? But that would be duplicative. Better to not create Qualifications section if no distinct content. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Qualifications. - Skills: There's a "Skills" heading? Not explicitly, but there is a "Skills including use of industry-standard computer software..." under Experience+Knowledge. Could treat as Skills section. But we already have skills in Requirements. Might create a Skills section listing software etc. However we need to avoid thin sections. Could combine skills into Requirements. But we have a separate "Skills" heading not present. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can include Skills if there is specific content. There is content about software skills etc. So we can create Skills section. But we already used some of that in Requirements. To avoid duplication, we could split: Requirements cover education, registration, experience; Skills cover software and tools. Let's extract skills: From the posting: "Skills including use of industry-standard computer software for the position (i.e., software such as CADD, HCS, AutoCAD, MicroStation, GIS, and Hydrologic/Hydraulic models). Ability to use spreadsheets, word processing, and standard office software." Also maybe "Knowledge of standard engineering and scientific techniques, procedures, and criteria in carrying out tasks." That's more knowledge than skill. Could go under Requirements. We'll create Skills section with those two bullets. - Benefits: There's a "Compensation + Benefits //" section with list: Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs. Also Paid Parental Leave details, Winter Holiday, Community Engagement. We need to extract benefits specifics. Let's parse: Compensation + Benefits // Competitive compensation package with comprehensive benefits including 401(k) Matching and Profit-sharing Contributions; Employee Stock Ownership Plan (ESOP); Health, Vision, and Dental Insurance; Short-Term and Long-Term Disability Insurance; Employer Funded and Voluntary Life Insurance; Tuition Reimbursement; and Continuing Education Programs Paid Parental Leave // FMLA-eligible employees will receive fully paid leave in the amounts of eight (8) weeks for maternity cases and two (2) weeks for paternity or adoptions cases Winter Holiday // Extended office closure from December 25 through January 1 to relax and enjoy the holidays Community Engagement // CobbFendley Cares focuses on STEM Education, Hunger Relief, and Sustainable Solutions Thus Benefits section should include these items as list. - Pay: The posting mentions "Competitive compensation package" but no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation package" but no specific figure. Is that enough? It says "Competitive compensation package with comprehensive benefits". That's a statement about compensation but not a specific number. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation package, albeit generic. I'd argue we can include Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." Pay section would be thin (just generic). Might be better to omit Pay and incorporate into Benefits? But Benefits already includes compensation package. The Benefits section already mentions compensation package. So we could omit Pay. - Schedule: There's "EXPECTED WORK HOURS This is a full-time position, generally 40 hours per week, however, hours may fluctuate depending on department needs including the use of overtime.CobbFendley’s standard operating hours are Monday through Friday, 7:30 AM to 4:30 PM CST. Generally, employees receive a 1-hour unpaid lunch break free of duty. Please note, operating hours and lunch hours may differ based on project workload, primarily for field staff." Also "WORK LOCATION FLEXIBILTY This position is eligible for a hybrid schedule once the training period is complete as established by the department." Thus we have schedule info: full-time, 40 hrs/week, standard hours M-F 7:30-4:30 CST, 1hr unpaid lunch, possible overtime, hybrid after training. Thus we can create Schedule section with that info. Now we need to output HTML fragment with headings

and

or

• . Ensure we don't include boilerplate like EEO, miscellaneous, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. Let's craft each section. About the role: combine the introductory paragraphs up to "Are You Ready To Join Our Block And Advance Your Career?" and the following sentences about CobbFendley being people valued resource, new hire program, development opportunities, compensation + benefits, paid parental leave, winter holiday, community engagement. Actually those are benefits; but they appear in the description before the specific job. We'll include them in About the role as prose. Thus About the role paragraph: "Since 1980,