Field Pipeline Technician I/II - Sycamore, Genoa, Dekalb, IL
DT Midstream · Channahon, IL · 1 mo ago
On-siteManagementFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate etc.
We need to parse the posting.
Let's extract content:
First paragraph: "At DT Midstream, we've got the energy to achieve great things! DT Midstream owns and operates a diverse, integrated portfolio of midstream pipeline, storage and gathering assets, allowing us to provide a comprehensive set of midstream services to our customers across the Southern, Northeastern and Midwestern United States and into Canada. Our newly independent public company is an energy industry leader with more than 20 years of proven success as part of DTE Energy and our focus is to be safe, caring, dependable and efficient in all we do."
That's about the company; could be "About the role"? Actually "About the role" is typical heading for role description. But we have "Job Summary" then description. So we can put that under "About the role" or maybe "Job Summary". The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists.
We have Job Summary: "Day to day operations and maintenance of natural gas compressor stations and gathering system."
Then "Key Accountabilities A Field Pipeline Technician Level II should be able to perform most of the following:" then a long list of duties.
Thus Responsibilities section can contain that list.
Then "Minimum Education & Experience Requirements" then list: High School Diploma or equivalent, Three years of experience in valve maintenance, leak survey of natural gas pipelines, mechanical aptitude, miss-dig or equivalent technical education, Possess and maintain a valid driver’s license.
That's Requirements.
Then "Other Qualifications Preferred Associate’s Degree Technical Education". That's Qualifications (preferred). Could also be part of Qualifications.
Then "Compensation & Benefits" with list of benefits. That's Benefits section.
Then "Other Requirements" list: Ability to function autonomously, Thorough knowledge of O&M manual, Demonstrated ability to lead or participate in work crews, Demonstrated ability to special projects, Use experience to recommend solutions to operational problems, Recommend improvements for operational efficiency, Emergency response: Provide incident command support to emergency responders, lead mock and table top exercises, High integrity and self-motivated, Excellent vehicle driving record, Basic computer skills, Good communication, problem solving and physical perceptive skills, Must be able to work and perform without close supervision, Team player, Maintain OQ qualification of all tasks, Ability to start and stop equipment, Competent in damage prevention activities and documentation, Ability to read and interpret alignment sheets, Ability to read and interpret P&ID, Recommend solutions to operations issues, Interact with contractors and customers both internal and external.
These could be Skills or Requirements? They are more like skills/abilities. Could go under Skills.
Then "Physical Demands" and "Working Conditions". Those could be under Requirements? But we have no specific heading for Physical Demands; we could include under Requirements or maybe under a separate section but not in allowed list. The instruction says prefer a few substantive sections over many thin ones. We could incorporate Physical Demands and Working Conditions into Requirements or Skills? Probably better to put them under Requirements as they are job requirements. But we already have Requirements for education/experience. Could combine.
We also have Pay section: not mentioned explicitly; there is no pay info. So we should NOT include Pay section.
Schedule: not mentioned explicitly; no schedule info. So omit Schedule.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
Check each for substantive content.
About the role: we have company overview and Job Summary. That's substantive.
Responsibilities: the list of duties.
Requirements: Minimum Education & Experience Requirements.
Qualifications: Preferred Associate’s Degree Technical Education (maybe also other preferred qualifications). Could also include "Other Qualifications Preferred Associate’s Degree Technical Education". That's it.
Skills: the "Other Requirements" list (abilities). Could also include physical demands? But we might put physical demands under Requirements as well. However we need to avoid thin sections. Let's see if we have enough for Skills: the list is long, so yes.
Benefits: the compensation & benefits list.
We must not include boilerplate like EEO etc. Not present.
We must not include duplicated lines.
We must preserve all substantive info; not invent or summarize away detail. So we need to keep the details as they appear, but we can format as