Instrument Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - About the role: The first paragraph: "The instrumentation engineer will assist in generating instrumentation project deliverables for new or updated process instrumentation under the supervision of a senior-level instrument engineer. Other duties include performing project site surveys of existing instrumentation to be replaced or re-designed, performing client documentation searches, marking up drawings or data sheets for as-found instrumentation and wiring details under the supervision of a senior-level instrument engineer." That's about the role. - Responsibilities: The list after "Job Duties/Responsibilities:" includes bullet points: Assist with instrument site surveys and walkdowns, Develop and prepare as-built or as-found instrumentation documentation, Perform client instrument documentation searches to find required project documents, Assist with generating instrumentation data, sheets, loop drawings, installation details, instrument lists, DCS/PLC I/O lists and P&IDs. - Requirements: Not explicitly a section but we have "Minimum Qualifications:" with Education, Experience, Licensure, Technical Skills, Management, Other Skills. Also "Professional Development Opportunities:" maybe part of Skills? Could be "Skills" section. - Qualifications: Could be same as Minimum Qualifications? The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: maybe the "Minimum Qualifications" includes education, experience, licensure, etc. Could be considered Requirements. - Qualifications: maybe the "Professional Development Opportunities"? Not exactly qualifications. Could be "Skills" includes technical skills, other skills, professional development. - Skills: we have Technical Skills (Microsoft Office, Adobe, Microsoft Windows, PC hardware) and Other Skills (Strong organizational, written and verbal communication skills). Also Professional Development Opportunities list. - Benefits: The paragraph about BE provides a comprehensive benefits package including health, dental, and vision insurance, life and disability insurance, 401(k) savings plan with employer matching, company paid holidays, paid parental leave, compensatory time off, and paid time off (PTO). Also mention discretionary bonus etc. So we have Benefits. - Pay: Pay Range: $70,000 - $95,000 annually. Also note about discretionary bonus etc. So we have Pay. - Schedule: Not mentioned. No schedule info. So we should NOT include Schedule heading. Also we need to remove boilerplate: EEO, E-Verify, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the details about physical requirements etc. Those are part of "Individual field assignments..." That seems like job requirements (physical demands). Should we put them under Requirements or maybe under Qualifications? Probably under Requirements (physical requirements). We'll include them as a list under Requirements. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to not repeat job title as heading. Not include Job ID. We need to output only HTML fragment. Let's structure:

  About the role

  The instrumentation engineer will assist in generating instrumentation project deliverables for new or updated process instrumentation under the supervision of a senior-level instrument engineer. Other duties include performing project site surveys of existing instrumentation to be replaced or re-designed, performing client documentation searches, marking up drawings or data sheets for as-found instrumentation and wiring details under the supervision of a senior-level instrument engineer.

  Responsibilities

  • Assist with instrument site surveys and walkdowns
  • Develop and prepare as-built or as-found instrumentation documentation
  • Perform client instrument documentation searches to find required project documents
  • Assist with generating instrumentation data, sheets, loop drawings, installation details, instrument lists, DCS/PLC I/O lists and P&IDs

  Requirements

  Education: BSc in Instrument, Mechanical, Electrical or Chemical Engineering

  Experience: Minimum 1 year, up to 3+ years

  Licensure: E.I.T. Preferred

  Management: No management experience required

  Other Skills: Strong organizational, written and verbal communication skills

  Physical and site‑specific requirements:

  • Possess physical mobility (on the ground and at heights)
  • May be required to pick up, lift, carry, and move up to 50 lbs
  • May be required to work at heights, climb ladders and stairways, and may occasionally work off platforms/scaffolding/ladders using appropriate fall protection
  • Must be able to work in all weather conditions (including heat, rain, cold, and wind) while wearing appropriate PPE (hard hat, safety glasses/goggles, ear plugs, masks/respirators, hi‑vis safety vests, leather gloves, leather steel‑toed work boots)
  • May be required to position yourself to work in confined spaces
  • May be required to adhere to a client’s random drug testing program prior to entering their site
  • May be required to meet a client’s facial hair safety policy prior to entering their site
  We could also include Technical Skills under Skills section.

  Skills

  Technical Skills: Microsoft Office, Adobe, Microsoft Windows, PC hardware

  Other Skills: Strong organizational, written and verbal communication skills

  Professional Development Opportunities:

  • Develop instrumentation knowledge skills
  • Develop project skills
  • Develop skills used to generate instrument deliverables
  • Develop knowledge of industry instrumentation standards
  • Obtain industry and skill‑specific certifications
  • Learn new engineering software tools and programs
  But note we already listed Other Skills under Requirements; we might duplicate. Better to keep Skills separate and not duplicate. The Requirements section could focus on education, experience, licensure, management. The physical requirements could be under Requirements as well. Then Skills section includes technical skills, other skills, professional development. Let's adjust: Requirements: Education, Experience, Licensure, Management (no management experience required). Also maybe we could include "Other Skills" under Skills not Requirements. Thus:

  Requirements

  • Education: BSc in Instrument, Mechanical, Electrical or Chemical Engineering
  • Experience: Minimum 1 year, up to 3+ years
  • Licensure: E.I.T. Preferred
  • Management: No management experience required
  Then physical requirements maybe under Requirements as well? They are more like job demands; could be under Requirements as a list. We could add a subheading? But we only allowed headings as per list. Could put physical requirements under Requirements as a list. Thus:

  Requirements

  • Education: BSc in Instrument, Mechanical, Electrical or Chemical Engineering
  • Experience: Minimum 1 year, up to 3+ years
  • Licensure: E.I.T. Preferred
  • Management: No management experience required
  • Physical and site‑specific requirements:
    • Possess physical mobility (on the ground and at heights)
    • May be required to pick up, lift, carry, and move up to 50 lbs
    • May be required to work at heights, climb ladders and stairways, and may occasionally work off platforms/scaffolding/ladders using appropriate fall protection
    • Must be able to work in all weather conditions (including heat, rain, cold, and wind) while wearing appropriate PPE (hard hat, safety glasses/goggles, ear plugs, masks/respirators, hi‑vis safety vests, leather gloves, leather steel‑toed work boots)
    • May be required to position yourself to work in confined spaces
    • May be required to adhere to a client’s random drug testing program prior to entering their site
    • May be required to meet a client’s facial hair safety policy prior to entering their site
  But nested lists may be okay. However instruction: Use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could be okay. Alternatively we could keep physical requirements as a

    then a

    . Simpler:

    Physical and site‑specific requirements:

    then
    . We'll do that. Now Skills:

    Skills

    • Technical Skills: Microsoft Office, Adobe, Microsoft Windows, PC hardware
    • Other Skills: Strong organizational, written and verbal communication skills

    Professional Development Opportunities:

    • Develop instrumentation knowledge skills
    • Develop project skills
    • Develop skills used to generate instrument deliverables
    • Develop knowledge of industry instrumentation standards
    • Obtain industry and skill‑specific certifications
    • Learn new engineering software tools and programs
    Benefits:

    Benefits

    In addition to base pay, employees may be eligible for discretionary bonus and/or other applicable incentive compensation plans. BE provides a comprehensive benefits package including health, dental, and vision insurance, life and disability insurance, 401(k) savings plan with employer matching, company paid holidays, paid parental leave, compensatory time off, and paid time off (PTO).

    Pay:

    Pay

    Pay Range: $70,000 - $95,000 annually. The above pay range represents a general guideline; however, Brindley considers several factors when determining base salary that are unique to each candidate, including but not limited to the candidate's depth of experience, skill set, certifications, specific work location, and current market conditions.

    We should not include Schedule. Now ensure we removed boilerplate: EEO, E-Verify, etc. Also removed duplicated lines like "Individual field assignments typically each have their own unique requirements." We kept the physical requirements derived from that. We kept the sentence about "Prior to deployment on any field assignment, you must be able to meet all client-specific site requirements." Might be considered boilerplate? It's somewhat generic but still part of requirements. Might keep as a brief statement. But we could incorporate into physical requirements. The instruction: Remove duplicated lines, and application instructions. The line about meeting client-specific site requirements is somewhat generic but still part of the posting. Might keep as a short sentence under Requirements. But we already have physical requirements list; we could add a preceding sentence: "Prior to deployment on any field assignment, you must be able to meet all client‑specific site requirements." as a

    . Let's add that. Now check for any other substantive content: "Individual field assignments typically each have their own unique requirements." That's basically same as above; we can drop as duplicate. Now ensure we didn't miss any other details: "Should you be unable or unwilling to meet assignment-specific requirements, your continued employment would then be subject to the availability of other assignments whose requirements can be met." That's more about employment condition; could be considered boilerplate? Might be considered part of requirements but it's more about employment policy. The instruction says remove duplicated lines, but not necessarily remove all conditional statements. However it's somewhat generic. I'd consider it boilerplate-ish and could drop. But to be safe, maybe