Graduate Engineer, Electrical - LNG

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. Let's parse posting: - Date, Location, Company: maybe metadata; we can fold minor metadata into short

or drop. Probably include a short

with date, location, company? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

with Date, Location, Company maybe. - Then "We believe real value..." is about company values; could be part of About the role? Actually "About the role" heading could contain description of opportunity. The posting includes "The Opportunity As an entry-level Electrical Engineer..." That's about role. So we can put that under

About the role

with

. - Responsibilities: list of duties under "Key Responsibilities" with bullet points. So we can create

Responsibilities

• ... each bullet. - Preferred Qualifications: list of qualifications. Could go under

  Qualifications

  or

  Preferred Qualifications

  . The instruction says use headings like Qualifications, Skills, etc. We have both Preferred Qualifications and Minimum Qualifications. We could combine into Qualifications section with both preferred and minimum? But we need to preserve all substantive info. Could have two sub-sections? But only allowed headings from list; we could use

  Qualifications

  and inside include both minimum and preferred as paragraphs or lists. Or we could separate into

  Minimum Qualifications

  not allowed; but we could still use

  Qualifications

  and include both. - Skills: The posting includes "Skilled in Problem Solving, Written Communication, Informing, and Peer Relationships." Also maybe other skills. Could put under

  Skills

  . - Benefits: The posting mentions "A variety of additional benefits are available to our professionals, including a company matched 401k plan, adoption reimbursement, vendor discounts, an employment referral program, AD&D insurance, pre-taxed accounts, voluntary legal plan and the B&V Credit Union. Professionals may also be eligible for a performance-based bonus program." Also "Hybrid or flexible work options may be offered after the first 90 days of employment". That's a benefit. So we can create Benefits section. - Pay: The posting includes "Salary Plan ENG: Engineering Job Grade 014". That's pay info but not a specific number. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Plan and Job Grade. That is pay-related info. Should we include Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Salary Plan ENG: Engineering Job Grade 014. That's a statement about pay. So we can include Pay section with that info. However we must avoid filler like "commensurate with experience". This is specific: Salary Plan ENG: Engineering Job Grade 014. So we can include. - Schedule: The posting mentions "Hybrid or flexible work options may be offered after the first 90 days of employment based upon manager discretion, job performance and work assignments." That's schedule info (flexible/hybrid). So we can include Schedule section. - Also there is "Relocation eligible : Yes". Could be part of metadata. - Also "Opportunity Type : College full time". Could be metadata. We need to avoid boilerplate like EEO, legal, accessibility contact, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, preferred qualifications, minimum qualifications, skills, benefits, pay, schedule. We must not repeat job title as heading. We must not include duplicated lines. We need to output only HTML fragment. Let's structure:

  Date: Sep 28, 2026 | Location: Houston, TX, US | Company: Black & Veatch Family of Companies

  Then

  About the role

  The Opportunity As an entry-level Electrical Engineer at Black & Veatch, you will help address some of the world's most pressing infrastructure challenges. You will have the opportunity to work on a wide range of projects to meet our clients' needs and contribute to the growth and success of Black & Veatch. You will be assigned to a functional area in our Fuels & Natural Resources department.

  Then Responsibilities: list each bullet. We need to extract bullet points from "Key Responsibilities" section: - Engineering Standards: Develops familiarity by reading, understanding and applying departmental design guides, standards, systems, applicable engineering codes and Black and Veatch policies and procedures - Quality / Continuous Improvement: Develops an understanding and complies with the Black and Veatch quality program Supports continuous improvement and change management efforts - Engineering Production: Contributes to preparation of less complex engineering deliverables such as drawings, reports, specifications, and studies of limited scope Performs routine research and develops recommendations for equipment and/or materials selection Collects, assimilates, and manages data for engineering work Prepares basic engineering calculations following standard methods and principles used in similar engineering analysis Understands and adheres to budget, schedule, and quality requirements - Project Coordination: Shares information with others as requested Coordinates with others when directed by supervisor or project leadership - Client Focus: Focuses on the needs of internal clients (project team leadership) while attempting to gain basic understanding of external client's main interests and drivers May provide support to business development or pursuit activities - Knowledge Sharing, Innovation and Technology: Shares current knowledge of latest technology and processes We need to keep each as separate
• . Some sentences are long; we can keep as is. Then Qualifications: we have Minimum Qualifications and Preferred Qualifications. Minimum Qualifications: "Requires a bachelor's degree in engineering from either a recognized accredited program in their home country or the country in which the professional is practicing. All applicants must be able to complete pre-employment onboarding requirements (if selected) which may include any/all of the following: criminal/civil background check, drug screen, and motor vehicle records search, in compliance with any applicable laws and regulations." Preferred Qualifications: list: "Coursework and knowledge of Power Systems, Motors, Transformers, Renewable Energy, Power Delivery, or Three Phase Power Calculations. Previous internship experience. Basic knowledge of engineering design principles, design guides and standards. Insights of industry trends and developing technologies. Fundamental knowledge of construction practices and principles. Skilled in Problem Solving, Written Communication, Informing, and Peer Relationships. Cumulative GPA of 3.0 or higher" We could split into two sub-sections but only allowed headings from list; we could still use

  Qualifications

  and inside have

  for Minimum Qualifications and

  for Preferred Qualifications (or vice versa). But we need to preserve all detail. Better:

  Qualifications

  Minimum Qualifications: ...

  Preferred Qualifications:

  • ... each item.
  But we must not invent headings like "Minimum Qualifications". Using bold inside p is okay. Skills: The posting includes "Skilled in Problem Solving, Written Communication, Informing, and Peer Relationships." That's already in Preferred Qualifications. But we could still have a Skills section highlighting those skills. However to avoid duplication, maybe we can put skills under Qualifications. But the instruction says we can use Skills heading if there is real specific content. The posting does mention skills explicitly. We could create a Skills section with those skills. However we already listed them under Preferred Qualifications. To avoid duplication, we could still include them but ensure not duplicate content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundant repetition. However we could keep them in Qualifications and not have separate Skills section unless there are other skills not covered. The posting also mentions "Basic knowledge of engineering design principles, design guides and standards." That's also knowledge. So maybe we just keep Qualifications and not separate Skills. But we need to decide if we include Skills heading. Since the posting does mention skills, we could include a Skills section with those skills. However we would be repeating content from Preferred Qualifications. Might be considered duplication but not prohibited. The instruction says "Prefer a few substantive sections over many thin ones." So better to combine. Thus we will not create a separate Skills section. Benefits: list: "A variety of additional benefits are available to our professionals, including a company matched 401k plan, adoption reimbursement, vendor discounts, an employment referral program, AD&D insurance, pre-taxed accounts, voluntary legal plan and the B&V Credit Union. Professionals may also be eligible for a performance-based bonus program." Also "Hybrid or flexible work options may be offered after the first 90 days of employment based upon manager discretion, job performance and work assignments." That's schedule but also benefit. We'll put hybrid/flexible under Schedule. Thus Benefits section:
  • company matched 401k plan
  • adoption reimbursement
  • vendor discounts
  • employment referral program
  • AD&D insurance
  • pre-taxed accounts
  • voluntary legal plan
  • B&V Credit Union
  • performance-based bonus program
  Pay: "Salary Plan ENG: Engineering Job Grade 014". We'll put in

  Salary Plan: ENG, Engineering Job Grade 014

  under

  Pay

  . Schedule: "Hybrid or flexible work options may be offered after the first 90 days of employment based upon manager discretion, job performance and work assignments." Also maybe "Full time/Part time : Full-Time". That's schedule info. Also "Relocation eligible : Yes". Could be schedule/benefit. We'll include full-time and relocation under Schedule? The instruction: Schedule section for schedule info. We'll include full-time, relocation eligibility, hybrid/flexible after 90 days. Thus Schedule section:

  Full-time position. Relocation eligible. Hybrid or flexible work options may be offered after the first 90 days of employment based upon manager discretion, job performance and work assignments.

  Now we need to ensure we didn't miss any substantive info: The posting also includes "Opportunity Type : College full time". That's covered by full-time. "Project Only Hire: No" maybe not needed. "Visa Sponsorship Available:No" maybe minor metadata; could be dropped or folded into short p. We could include in metadata p. We also have "Recruiter : Cody Gaston". Could be metadata. We'll include a short metadata p at top: Date, Location, Company, Recruiter, Opportunity Type, Visa Sponsorship, Relocation eligible, etc. But we should avoid too much metadata; but it's okay to fold minor metadata into a short p. Let's craft:

  Date: Sep 28, 2026 | Location: Houston, TX, US | Company: Black & Veatch Family of Companies | Recruiter: Cody Gaston | Opportunity Type: College full time | Relocation eligible: Yes | Visa Sponsorship: No

  Now we need to ensure we didn't include any boilerplate like EEO, legal, accessibility contact, etc. We removed those. Now output HTML fragment. Check for any missing content: The "We believe real value is powered by the unique skills and experiences of our professionals..." That's company values;