Facility Integrity Specialist

We need to output HTML fragment with sections only where there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: Basic Function: description of role: "HF Sinclair Midstream is seeking a Facility Integrity Specialist. This position is open to locations of Artesia, NM, Albuquerque, NM, or Glendale, AZ. This position supports continued development and implementation of the Integrity Management Program and conducts high-level assignments and duties for the Integrity Management Department independently. May direct or lead the work of others from time to time." That could be "About the role" or maybe "Responsibilities"? The posting has "Job Duties" then list of duties. So we can have sections: About the role (basic function), Responsibilities (Job Duties), Requirements (Experience, Education Level, Certifications), Skills (Required Skills, Preferred Skills/Certifications), Benefits (Benefits), maybe Pay and Schedule not present (no pay or schedule specifics). So we omit Pay and Schedule. We must not create sections with filler. So include only sections with content. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. Let's extract details: About the role (Basic Function): - HF Sinclair Midstream is seeking a Facility Integrity Specialist. - Position open to locations: Artesia, NM; Albuquerque, NM; Glendale, AZ. - Supports continued development and implementation of the Integrity Management Program. - Conducts high-level assignments and duties for the Integrity Management Department independently. - May direct or lead the work of others from time to time. Responsibilities (Job Duties): List each bullet: - Collects, integrates and analyzes technical data and information associated with Risk and Integrity assessments and inspections - Ability to select and implement NDE and Direct Inspection Methods. - Knowledge of Industry codes and standards - Thorough knowledge of Piping system codes and standards - Thorough knowledge of mechanical drawings, electrical drawings, P&ID’s - Knowledge of integrity failure mechanisms - Ability to identify potential risks associated with piping systems, components and equipment. - Works directly with field personnel to ensure appropriate documentation of inspection results - Manages and tracks facility integrity project schedules and status - Develops technical solutions and process improvements in conjunction with management - Creates project plans, process maps, schedules, cost estimates, and participates in the development, implementation and training of standards, specifications and procedures - Interfaces with all parts of the organization involved with Integrity Management activities, including vendors and contractors - Provides training for inexperienced personnel as needed - Manages field projects associated with facility inspections and assessments which include data collection, analysis, coordination of resources and technology utilization - Supports and coordinates technology development for inspection and integrity data management (e.g. Autocad, GIS, Non-Destructive Examination, Corrosion Monitoring) - Maintains and gains knowledge and understanding of current practices and news related to technologies, compliance, and regulations - Special assignments or tasks assigned to the employee by their supervisor, as determined from time to time in their sole and complete discretion. Requirements (Experience, Education Level, Certifications): - Experience: A minimum of eight year’s Plant, Terminal, and above Ground Storage Tank experience directly related to inspections, repairs and mechanical integrity program requirements. - Preferred Experience: Experience in Corrosion control methods, Risk Management, NDE, and Information Data Management Systems (PCMS). - Education Level: A minimum of a Bachelor’s Degree Engineering or related technical discipline. - Certifications in API 570, API 510 or AMPP CIP Level 2. Certification in lieu of a degree, is required. Skills (Required Skills, Preferred Skills/Certifications): - Ability to work independently or in a team environment. - Effective problem solver and troubleshooter; good analytical and abstract thinker and ability to use evaluation techniques. - Strong technical and project management. - Proficient in the use of Autocad drawings, P&ID’s. - Proficient in Microsoft applications such as Excel, Access, Word, Project, Visio. - Working knowledge of GIS. - Advanced working knowledge of design, construction and operation of crude oil, refined products and gas facilities. - Thorough knowledge of Industry codes and regulations required by PHMSA §195 and 192. - Ability to process information quickly and develop rapport with HollyFrontier employees and contractors. - Active member in NACE and API. - The ability to effectively communicate to others, both written and verbal; intermediate reading and writing skills; and the ability to perform intermediate mathematical calculations. - Preferred Skills/Certifications: - Understanding of inspection techniques and results; understanding of corrosion prevention methods and Risk Management principles; proven ability to utilize data management systems with an interest in technology solutions. - Experience with PCMS IDMS. - Certification in API 570. - Other API certifications of interest are CWI, CIP Level 2, API 1169, API 510, and data analysis are preferred. Benefits: - HF Sinclair offers a comprehensive benefits package designed to support the well-being of our employees and their families. - Benefits include, but are not limited to: - Medical Insurance - Vision Insurance - Dental Insurance - Paid Time-Off - 401(k) Retirement Plan with match - Educational Reimbursement - Parental Bonding Time - Employee Discounts - We are committed to fostering a supportive and inclusive work environment, ensuring our employees have the resources needed to thrive professionally and personally. - Benefit eligibility is governed by official plan documents, for more details visit Total Rewards. We also have Physical Requirements, One HF Sinclair Culture, About HF Sinclair Corporation, Equal Opportunity Employer. According to instructions, we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The sections about Physical Requirements, Culture, About HF Sinclair, Equal Opportunity Employer are likely considered boilerplate or not required? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Physical Requirements might be considered not boilerplate but maybe part of job posting; but they didn't list a specific heading for Physical Requirements in allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements is not one of those, so we should not create a heading for it; we could possibly incorporate into Requirements or Skills? But it's not exactly a requirement or skill; it's physical demands. The instruction says to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Since Physical Requirements is not in the allowed list, we should not create a section for it. We could maybe fold some of that info into Requirements or Skills if relevant, but it's not exactly a skill. Safer to omit it, as it's not in allowed headings. Similarly, Culture and About HF Sinclair Corporation are not in allowed headings; we could maybe put About HF Sinclair under About the role? But About the role is about the role, not the company. The instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we should not add About HF Sinclair Corporation as a separate heading. We could incorporate some company overview into About the role? But that would be adding info not originally under Basic Function; but we could treat it as part of About the role? Might be stretching. Better to omit company overview and culture sections, as they are not required headings. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit those sections, we are losing substantive info (company description, culture). However, the allowed headings list does not include a heading for company overview; but we could still include a

  paragraph without a heading? The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says to use those for section headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't say we cannot have other headings besides those examples, but the examples are given. Likely they expect us to only use those headings. So we should not add extra headings like "About HF Sinclair Corporation". We could incorporate that info into a

  under "About the role" maybe? But that would be mixing role description with company overview, which may be okay but could be considered inventing? Not really; we are just placing the info somewhere. However, the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can fold minor metadata into a short

  . Company overview might be considered not minor metadata but substantive. But we have no heading for it; maybe we can put it as a

  before the first heading? The instruction says output ONLY the HTML fragment — no /. It doesn't forbid having stray paragraphs without heading. It says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't say you cannot have other headings, but likely they want only those headings. To be safe, we could include a brief

  paragraph before the first heading that contains the company overview and culture? But that might be considered adding a section without heading, which might be okay. However, they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". That refers to sections with headings. So we can have paragraphs without heading as long as they are not considered a section? Not clear. Given typical tasks, they expect to produce sections like About the role, Responsibilities, Requirements, Skills, Benefits. So we will produce those five sections. We'll incorporate the basic function into About the role. We'll incorporate job duties into Responsibilities. We'll incorporate experience, education, certifications into Requirements. We'll incorporate required and preferred skills into Skills. We'll incorporate benefits into Benefits. We'll omit Pay and Schedule. We need to ensure we preserve all substantive information from those sections. Let's verify we didn't miss any details. From Basic Function: we captured location, role, purpose, independent work, may direct/lead others. From Job Duties: we captured each bullet. From Experience: we captured minimum eight years Plant, Terminal, above Ground Storage Tank experience directly related to inspections, repairs and mechanical integrity program requirements. Preferred Experience: Experience in Corrosion control methods, Risk Management, NDE, and Information Data Management Systems (PCMS). From Education Level: Bachelor's Degree Engineering or related technical discipline. Certifications in API 570, API 510 or AMPP CIP Level 2. Certification in lieu of a degree, is required. From Required Skills: list as above. From Preferred Skills/Certifications: list as above. From Benefits: list as above. We also have "Work Conditions" (Office based with up to 50% travel...). That's not in allowed headings; maybe we could fold into Requirements or Skills? It's about work conditions. Could be considered part of Requirements? Not exactly. But we could include it under Requirements as a bullet? Might be okay. However, the instruction says to include a section only when posting