Estimator II - Energy

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the posting. We have description: Title: Estimator II, Reports To: Chief Estimator, Location: San Jose, CA | Hybrid, Salary Range: $75,000 to $98,000. Then some text about pay determination, benefits program, etc. Then "Who We Are" paragraph about CEI. Then "THE ENERGY TEAM" paragraph. Then "About The Role" paragraph with responsibilities. Then "About You" bullet list? Actually it's a paragraph with lines separated by line breaks. Then "Minimum Qualifications" with education, licensure/certifications, experience. Then some notes about sponsorship, scam warning, EEO, accessibility. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the "PLEASE NOTE: CEI will never ask for any money..." and the EEO statement, accessibility contact, etc. Also remove "Who We Are" maybe? It's not a required heading but could be considered "About the company". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't say we must include "Who We Are". We can include if there is substantive content, but we should prefer few substantive sections. The "Who We Are" is descriptive but not required heading; we could put it under a

without heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow that pattern. Probably we should include sections: About the role (maybe under About The Role heading), Responsibilities (maybe we can extract duties), Requirements/Qualifications/Skills (maybe combine), Pay (salary range), Benefits (mention of benefits program), Schedule (Hybrid). Also Location maybe? Not in list but could be included as a paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include specifics: Salary range $75,000 to $98,000, mention that final determination varies based on factors, competitive compensation package, robust benefits program. Benefits: we have only mention of robust benefits program, not specifics. Should we include Benefits section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits program (robust benefits program). So we can include Benefits section with that statement. Schedule: Hybrid mentioned. So we can include Schedule section with "Hybrid (San Jose, CA)". Also location maybe. Pay: Salary range and note about determination. Now responsibilities: Under About The Role: list of duties: developing and completing utility scale solar PV and BESS estimates, including self-perform and subcontracted scopes; estimating includes RFP & drawing package review, developing proposal level designs, quantity take-off, material RFQ prep & evaluation, and subcontractor RFQ prep & evaluation; Perform all levels and types of estimating, planning, scheduling and cost engineering project activities; Accurately perform material quantity take-off of all renewable energy projects; Management of material vendor relationships, including packaging and presentation of RFQs and evaluation of vendor pricing; Develop and maintain relationships with subcontractors and material vendors; Manage subcontractor database; Prepare RFQs and evaluate vendor pricing; Compare and reconcile scopes of work. We need to put these in

• . About You: list of knowledge/skills: Knowledge of utility scale solar PV and BESS; Excellent verbal and written communication skills; Proven analytical, organizational, and negotiation skills; Experience with Engineer, Procure, Construct (EPC) estimates; Experience with MS Office; Experience with Accubid or similar estimating software; Experience with Bluebeam or similar on-screen take-off software; Existing relationships with Tier 1 vendors; Basic knowledge of electrical circuitry and calculations; Ability to meet deadlines and partner with team members while working remotely; Knowledge of power delivery, including substations and transmission lines; Knowledge of engineering scopes, including electrical, structural, civil, civil experts (hydrology, Geotech, etc.) and permitting; Knowledge of Civil construction related to utility scale solar PV – grading, hydrology, trenching, etc. We could split into Requirements, Qualifications, Skills. The instruction says use headings for those categories. We need to decide what goes where. Typically Requirements = minimum qualifications (education, experience). Qualifications = preferred qualifications. Skills = specific skills. But we can combine. Minimum Qualifications: Education: High School Diploma or GED required. Bachelor’s in Engineering or Construction Management preferred. Licensure/Certifications: None required. Experience: Three (3) years of estimating experience in solar PV and managing subcontracts preferred. Experience with design/build and Engineer, Procure, Construct (EPC). Experience with Accubid preferred. Applicants must be authorized to work in the United States. This position is not eligible for sponsorship. We should keep that info. We need to remove boilerplate like sponsorship note? It's not boilerplate; it's relevant. The "PLEASE NOTE: CEI will never ask for any money..." is scam warning, remove. Also EEO statement remove. Accessibility contact remove. Now we need to output only HTML fragment, no markdown fences. Let's structure:

  About the Role

  ... maybe a short summary? The About The Role heading already has a paragraph describing role. We can put that paragraph as

  then

  for duties. But we should not repeat the heading as job title. Already fine. We need to include location and schedule maybe as separate sections. Let's decide sections: - About the Role (h3) with paragraph summary and ul duties. - Responsibilities (maybe duplicate of duties). But we already have duties under About the Role. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid overlapping but we should avoid thin sections. Perhaps we can combine About the Role and Responsibilities into one section? But we need to follow instruction: use h3 for section headings (e.g. About the role, Responsibilities...). It doesn't say we must use all; we can choose which to include. To be safe, we can include About the Role (summary) and Responsibilities (list). But that may be thin. However we have substantive content for both: summary paragraph and list of duties. That's okay. - Requirements (h3) for minimum qualifications (education, experience, authorization). Could also include licensure. - Qualifications (h3) for preferred qualifications (Bachelor's preferred, 3 years experience preferred, etc.) Might overlap with Requirements. But we can separate: Requirements = required (HS diploma, auth to work). Qualifications = preferred (Bachelor, 3 years experience, Accubid, etc.) - Skills (h3) for the list of knowledge/skills from About You. - Benefits (h3) for robust benefits program. - Pay (h3) for salary range and note about determination. - Schedule (h3) for Hybrid and location. We should also include location maybe in Schedule or separate? Could include location in Schedule: "Hybrid (San Jose, CA)". Or we could add a separate paragraph for location but not required. We must not include headings with filler text. All sections have real content. Now we need to ensure we don't repeat content unnecessarily. Let's extract. Paragraph for About the Role summary: "The Estimator will work closely with the Preconstruction team, Project Managers, Purchasing, Engineering, and report to the Chief Estimator - Energy. The Estimator will be responsible for developing and completing utility scale solar PV and Battery Energy Storage System (BESS) estimates, including self-perform and subcontracted scopes of work." We can put that as

  . Then Responsibilities

  with the detailed duties list. Now Requirements: Education: High School Diploma or GED required. Bachelor’s in Engineering or Construction Management preferred. (But preferred maybe goes to Qualifications). Let's treat required: HS Diploma or GED required. Authorization to work in US required. (Also maybe no licensure). So Requirements: HS Diploma or GED required; Must be authorized to work in the United States. Qualifications: Bachelor’s in Engineering or Construction Management preferred; Three (3) years of estimating experience in solar PV and managing subcontracts preferred; Experience with design/build and Engineer, Procure, Construct (EPC); Experience with Accubid preferred. Skills: Knowledge of utility scale solar PV and BESS; Excellent verbal and written communication skills; Proven analytical, organizational, and negotiation skills; Experience with MS Office; Experience with Accubid or similar estimating software; Experience with Bluebeam or similar on-screen take-off software; Existing relationships with Tier 1 vendors; Basic knowledge of electrical circuitry and calculations; Ability to meet deadlines and partner with team members while working remotely; Knowledge of power delivery, including substations and transmission lines; Knowledge of engineering scopes, including electrical, structural, civil, civil experts (hydrology, Geotech, etc.) and permitting; Knowledge of Civil construction related to utility scale solar PV – grading, hydrology, trenching, etc. Benefits: We provide a competitive compensation package that recognizes your experience, credentials, and education alongside a robust benefits program to meet your needs. (Also mention compensation reflects cost of labor across several US geographic markets). We can include that. Pay: Salary Range: $75,000 to $98,000. Final determination of a successful candidate’s starting pay will vary based on a number of factors, including market location and may vary depending on job-related knowledge, skills, education and experience. The pay scale listed for this position is generally for candidates that meet the specified qualifications and requirements listed on this specific job description. Our compensation reflects the cost of labor across several US geographic markets. Schedule: Hybrid (San Jose, CA). Also mention location: San Jose, CA | Hybrid. We could also include location in Schedule. Now we need to ensure we don't include boilerplate like "Who We Are", "THE ENERGY TEAM", etc. Those are not required headings; we could optionally include them as paragraphs without heading? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say we must remove company description. However "Who We Are" and "THE ENERGY TEAM" are not boilerplate but could be considered company overview. The instruction says prefer a few substantive sections over many thin ones. Including them would add extra sections or paragraphs without headings. Might be okay to include as a paragraph without heading? But we have no heading for that; we could just include a

  after the title? But the instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should avoid extra headings. We could include a

  for company overview without heading. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a company overview paragraph might be okay but could be considered thin. However it's substantive info about the company. The instruction didn't forbid including it; just said to use h3 for those specific section headings. It didn't say we cannot have other content outside those headings. So we could include a

  for "Who We Are" and "THE ENERGY TEAM" as a combined paragraph. But we need to decide. Given the instruction to prefer few substantive sections, maybe we omit company overview to keep sections focused on the job. The job posting already shows the title; we don't need to repeat company overview. I'd lean to omit. Thus final HTML will have