Underground Foreman - Telecom Experienced

We need to output HTML fragment with sections: About Us? Actually we need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. The posting includes "About Us", "About This Role", "What You'll Do", "What You'll Bring", "Working Conditions", "Physical Requirements", "Benefits Include What You'll Get", "Compensation Range". Also "Equal Opportunity Employer" etc which we need to remove as boilerplate. We need to preserve all substantive information, remove boilerplate, duplicate lines, navigation, legal, EEO, scam-warning, application instructions. Also remove "Equal Opportunity Employer" lines. We need to decide which sections to include based on content. We have: - About Us: description of company. Could be considered "About the role"? Actually "About Us" is company overview. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should map content to those headings where appropriate. "About Us" could be "About the role"? But there is also "About This Role". So we could have "About the role" heading containing the "About This Role" paragraph. The "About Us" could be omitted? It's substantive info about company; maybe we could include as a separate section like "About the company" but not in list. The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. Probably we can use those headings where applicable, and we can also add other headings if needed, but better to stick to those. However "About Us" is not exactly "About the role". But we could treat "About Us" as "About the role"? Not accurate. Maybe we can include "About the company" as a heading but not in examples; risk of violating instruction? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings; we should not invent others. So we should map content to those headings. Thus we need sections: - About the role: from "About This Role" paragraph. - Responsibilities: from "What You'll Do" list. - Requirements / Qualifications: from "What You'll Bring" (Qualifications) plus maybe "Preferred Qualifications". Could combine into Requirements and Qualifications sections. The instruction says we can have both Requirements and Qualifications headings. We'll need to decide what goes where. Typically Requirements are mandatory; Qualifications could be preferred. We'll separate. - Skills: maybe from abilities like communication, etc. Could be part of Qualifications. - Benefits: from "Benefits Include What You'll Get" list. - Pay: from "Compensation Range". - Schedule: from "Working Conditions" (full-time hourly, at least 40 hours per week). Also maybe "Physical Requirements" could be separate but not in list; maybe we can include under Requirements or as its own section? Not in examples. Could omit? But we need to preserve ALL substantive information. Physical Requirements is substantive. We could include it under a section like "Requirements" or maybe "Physical Requirements" as a heading but not in examples. However instruction says we should prefer a few substantive sections over many thin ones. Could combine Physical Requirements into Requirements or Qualifications. We also have "Working Conditions" which describes environment; could be part of Requirements or its own section? Not in examples. Could include under Requirements. We need to avoid boilerplate: EEO lines, etc. We must not include headings with filler text like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Us: "Founded in 1964, Robinson Brothers Construction is a wholly owned subsidiary of Quanta Services, Inc. (NYSE: PWR), the largest utility contractor in North America. We are a general contractor dialed into the dynamics of installing infrastructure for the communications, renewable energy, natural gas, and electric utility industries. True to our word and proud of our people, we’re committed to providing superior service to our customers throughout the American West. Between 2006 and 2016, we grew from 14 employees to a team of over 200. We’re licensed, bonded, and insured to operate in Washington, Oregon, Idaho, Alaska, Montana, Wyoming, Kansas, Colorado, Oklahoma, Texas, New Mexico, and California. We’re pleased with our growth – but we’re not stopping here. RBC serves its clients, invests in its employees, and competes for the future – every day." But we may not have a heading for About Us; maybe we can omit because it's not required? However instruction says preserve ALL substantive information. If we omit About Us, we lose substantive info. But we could incorporate it into "About the role"? Not appropriate. Could we add a heading "About the company"? Not in examples but maybe acceptable? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, just gives examples. It says "Use

for section headings (e.g. ...)". Likely they expect those headings but not strictly limited. However to be safe, we could treat About Us as "About the role"? No. Maybe we can include About Us under a heading "About the role" as part of role description? But the "About This Role" already covers role. Could combine both under "About the role". Let's see: "About This Role" paragraph: "Ready to lead from the front? The Underground Foreman calls the shots on their crew, sized up to the job at hand, and can jump in and handle anything a Laborer or Operator can do. You'll train up the next generation of laborers and operators, keep the paperwork moving with daily timesheets for your crew and yourself, and make sure everyone goes home safe by keeping the crew sharp on job site safety processes and protocols. Robinson Brothers Construction, LLC keeps busy across most of the Pacific Northwest and beyond, with current and upcoming contracts stretching throughout the broader Northwest region. This is a travel position, and candidates should be prepared to work at various job sites as assigned." That's substantive. The About Us is company overview; we could include that as a separate section "About the company". But not in examples. However maybe we can add a heading "About the company" and still follow instruction? 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 use

for section headings (e.g. ...). It might be interpreted as you should use those headings where applicable, but you can also add others if needed. However they also say "Prefer a few substantive sections over many thin ones." So adding many sections may be discouraged. Adding About Us as separate section adds another section; but we could merge it into About the role? Might be okay. Let's think: The job posting already shows the job title at top; we shouldn't repeat it as heading. The "About Us" is not about the role but about the company. Could be considered background; maybe we can include it under a heading "About the role" as part of role description? Might be stretching. Alternatively, we could omit About Us and still preserve substantive information? The instruction says preserve ALL substantive information; omitting would violate. So we need to include it. Thus we need a heading for company info. Could we use "About the role" and include both About This Role and About Us? The heading would be "About the role". Under it we could have two paragraphs: first about the role, second about the company. That would preserve all info. That seems acceptable. Now Responsibilities: list from "What You'll Do". We'll output

• each item. Requirements: mandatory qualifications from "What You'll Bring" (the list before "Preferred Qualifications"). Let's extract: - Willingness to travel. - 3–5 years of experience in underground construction. - Ability to read maps, plans, and blueprints, and convey this information to others. - Experience operating heavy equipment. - Knowledge of proper operation and safety standards for heavy equipment. - 1–3 years of experience operating heavy machinery, including loaders, dozers, backhoes, and excavators. - Traffic Control Maintainer certificate. - Ability to pass a pre-employment drug screen and background check. - Valid driver's license or eligibility and willingness to obtain the required license for the position. - Good driving record. - Basic knowledge of and ability to operate various types of utility trucks and equipment safely. - Basic knowledge of and ability to use hand tools and equipment safely. - Effective communication skills with customers, employees, etc. - Willingness and ability to work in all weather conditions. - Ability to lift/carry 50 lbs regularly and up to 100 lbs as needed, with or without assistance. - Class A CDL is a plus (higher wage scales apply to CDL holders). - OSHA 10 certificate. Note: "Class A CDL is a plus (higher wage scales apply to CDL holders)" is a plus, not mandatory; but it's in the list. Could treat as qualification but maybe put under Preferred Qualifications? However it's listed under "What You'll Bring" before "Preferred Qualifications". We'll keep it in Requirements but note it's a plus. Preferred Qualifications: list: - Previous construction experience, preferably in the underground industry. - Ability to follow directions and take initiative when needed. - Understanding of daily maintenance for underground equipment. - Ability to perform all underground procedures and duties. We could put these under Qualifications section. Skills: maybe we can extract communication skills etc. But we already have communication skills in Requirements. Could create Skills section for things like effective communication, ability to read maps, etc. But we might avoid duplication. Working Conditions: description: "This is a full-time hourly position, expected to work at least 40 hours per week. The position operates in an outdoor environment and is regularly exposed to various weather conditions, including extreme cold, rain, sleet, snow, humidity, high temperatures, and high wind. The work environment will vary throughout the day, including changes in terrain, traffic, urban settings, and rural settings. There may be occasional exposure to natural gas and the risk of electrical shock, as well as moderate to loud noise levels." Physical Requirements: list: "The employee must be able to stand for long periods (up to 12 hours at a time), tolerate extreme weather conditions, speak and hear worksite safety instructions, and withstand prolonged and repeated lifting, standing, climbing, kneeling, reaching, feeling, crouching, and crawling. The employee must be able to regularly lift 75 pounds. Specific vision abilities required include close vision, distance vision, color vision, peripheral vision, depth perception, and the ability to adjust focus." We could combine Working Conditions and Physical Requirements into a section like "Working Conditions & Physical Requirements" or separate. Since we have no heading for physical requirements, maybe we can include under Requirements. Benefits: list from "Benefits Include What You'll Get": Health Insurance: Medical, Dental, Vision Plans; Flexible Spending Accounts/Health Savings Accounts; Retirement Savings Plan (401K) with company match; Short- & Long-Term Disability; Supplemental Life and AD&D Insurance; Paid Holidays and Vacation; Competitive Pay