Estimator - Concrete

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 need to decide which sections have content. From posting: Job Summary: description about Estimator I and II titles, duties. That could be "About the role". We'll put that in

About the role

with

. Key Responsibilities: list of duties. Use

• . Minimum Job Requirements: experience levels, degree, LEED, Microsoft Office. That could be "Requirements" or "Qualifications". We'll treat as Requirements. Preferred candidates: LEED accreditation, willingness. Could be Qualifications? But we can combine. Physical Requirements: list of physical demands. Could be part of Requirements? Might be separate but we have no heading for Physical Requirements; we could include under Requirements as part of list. Safety Level: Non-Safety Sensitive. Could be part of Requirements? Might be minor metadata; we can fold into a short

  maybe. About Us: description of company, benefits list. Benefits list: Market Competitive Salary etc. That's Benefits section. Pay: Not explicitly stated except "Market Competitive Salary (paid weekly)" which is pay info. So we can have Pay section with that. Schedule: Not mentioned. So we omit Schedule. Skills: maybe Microsoft Office proficiency. Could be Skills section. We need to avoid boilerplate: EEO, legal, notice to external search firms, etc. We must preserve all substantive information; not invent or summarize away detail. Must not repeat job title as heading. We need to output only HTML fragment. Let's structure:

  About the role

  Estimator I and II titles are developmental positions within the preconstruction department. The El/Ell provides support for single large projects or multiple smaller projects. Primary duties include participation in bid efforts, working with teams on Design Build and CM at Risk delivery methods, and providing administrative support to the estimating department. The El/Ell is expected to be competent in basic estimating tasks and is developing an understanding of more advanced estimating principals including conceptual estimating, project logistics, and indirect costs.

  Responsibilities

  • Accurately performs quantity takeoff.
  • Assists in the pricing of project logistics, including hoisting, personnel lifts, and temporary construction elements.
  • Develops abstracts and competently evaluates basic trade bids.
  • Develops basic understanding of indirect costs, including insurance, taxes, and fees.
  • Develops pricing for basic project elements and assists in the preparation of key estimating deliverables.
  • Drafts subcontracts and purchase orders for review by senior personnel.
  • Provides document control (sub lists, distribution of plans, addenda, etc.) for assigned projects.
  • Solicits pricing for projects in the hard bid environment.
  • Supports conceptual estimating efforts within the department, including development of basic models for review by senior personnel.
  • With oversight from senior personnel, develops budget uploads and purchasing plans.

  Requirements

  Experience levels: Estimator I: 1-3 years of experience; Estimator II: 2-5 years of experience. Four year engineering degree or equivalent combinations of technical training and/or related experience. Preferred candidates will have obtained their LEED accreditation, or express willingness to obtain. Proficient use of all Microsoft Office Suite programs.

  Physical requirements: May stoop, kneel, or bend on an occasional basis; must comply with all safety standards and procedures; required to use hands to grasp, lift, handle, carry or feel objects frequently; will interact with people and technology frequently during a shift/workday; will lift, push or pull objects on an occasional basis; will sit, stand or walk short distances for up to the entire duration of a shift/workday; will use telephone, computer system, email, and other electronic devices frequently to communicate with internal and external customers or vendors.

  Safety level: Non‑Safety Sensitive.

  Skills

  • Proficient use of Microsoft Office Suite programs.

  Benefits

  • Market Competitive Salary (paid weekly)
  • Bonus Eligibility based on company, group, and individual performance
  • Employee Stock Ownership Plan & 401K
  • Industry Leading Health Coverage Starting Your First Day
  • Flexible Time Off (FTO)
  • Medical, Health Savings, and Wellness credits
  • Flexible Spending Accounts
  • Employee Assistance Program
  • Workplace Wellness Programs
  • Mental Health Program
  • Life and Disability Insurance
  • Employee-Owner Perks
  • Educational Assistance
  • Sundt Foundation - Charitable Employee-Owner's program

  Pay

  Market Competitive Salary (paid weekly)

  We have duplicated benefit of salary; maybe we should not duplicate. The Pay section could just state that salary is market competitive and paid weekly, but we already have that in Benefits list. However instructions: include a section ONLY when posting has real, specific content for it. Pay info exists: "Market Competitive Salary (paid weekly)" is specific. So we can have Pay section with that sentence. Benefits section can list other benefits excluding salary to avoid duplication. But we must preserve ALL substantive information; we can keep salary in both places? That would be duplication but not invented. Might be okay but better to avoid duplication. Let's move salary to Pay only, and Benefits list excludes salary. Thus Benefits list: Bonus Eligibility..., Employee Stock Ownership Plan & 401K, Industry Leading Health Coverage..., Flexible Time Off (FTO), Medical, Health Savings, and Wellness credits, Flexible Spending Accounts, Employee Assistance Program, Workplace Wellness Programs, Mental Health Program, Life and Disability Insurance, Employee-Owner Perks, Educational Assistance, Sundt Foundation - Charitable Employee-Owner's program. Now ensure we didn't include boilerplate: EEO statement, notice to external search firms, etc. Removed. Check for any other substantive content: "Note: Job Description is subject to change at any time and may include other duties as assigned." That's a note; could be considered minor metadata; we could fold into a short

  under About the role or Responsibilities. But it's generic; maybe we can include as a short paragraph under About the role. It's substantive? It's a note about description changes; could be considered boilerplate? It's not EEO/legal; it's a note about job description flexibility. Might be okay to include. But instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is not those; it's about job description changes. Could keep. We could add a

  under About the role: "Note: Job Description is subject to change at any time and may include other duties as assigned." Also "Note: Jobs with the Safety-Sensitive designation are those that include tasks or duties that the employer reasonably believes could affect the safety and health of the employee performing the task or others such as operating a vehicle, operating equipment, operating machinery or power tools, repairing/maintaining the operation of any vehicle/equipment, the handling/disposal/transport of hazardous materials, or the handling/treatment/disposal of potentially flammable/combustible materials." That's explanatory about safety level; could be folded into Safety level note. Might be considered boilerplate? It's a definition; maybe we can keep as part of Requirements. We'll include a short paragraph after Safety level. Now produce final HTML. Check for any missing content: "About Us" paragraph about employee-owned contractor, culture, etc. That's substantive; we could include under About the role or a separate section like "About the company". But we only have allowed headings list; we could put under About the role or maybe create a new heading not allowed. Better to incorporate into About the role? The About the role currently is about the job; we could add another section "About the company" but not in allowed list. The instructions say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we can use those headings; we shouldn't invent others. So we should fit company description into one of those headings. Perhaps "About the role" can include both role and company description. Or we could put under "About the role" a paragraph about Sundt. Let's do that. Thus About the role paragraph will include job summary and company description. Let's craft:

  About the role

  Estimator I and II titles are developmental positions within the preconstruction department. The El/Ell provides support for single large projects or multiple smaller projects. Primary duties include participation in bid efforts, working with teams on Design Build and CM at Risk delivery methods, and providing administrative support to the estimating department. The El/Ell is expected to be competent in basic estimating tasks and is developing an understanding of more advanced estimating principals including conceptual estimating, project logistics, and indirect costs.

  As a 100% employee-owned contractor, Sundt offers a culture where everyone is an owner, focused on building long‑term prosperity for clients, communities and employee‑owners. The company provides competitive pay, industry‑leading benefits (including a 401k and employee stock ownership plan), incentive programs, and training for personal and professional growth.

  Note: Job Description is subject to change at any time and may include other duties as assigned.

  Now Responsibilities as before. Requirements: include experience, degree, LEED, Microsoft Office, physical requirements, safety level, safety definition note. We'll combine. Let's write Requirements:

  Requirements

  Experience levels: Estimator I: 1‑3 years of experience; Estimator II: 2‑5 years of experience. Four‑year engineering degree or equivalent combinations of technical training and/or related experience. Preferred candidates will have obtained their LEED accreditation, or express willingness to obtain. Proficient use of all Microsoft Office Suite programs.

  Physical requirements: May stoop, kneel, or bend on an occasional basis; must comply with all safety standards and procedures; required to use hands to grasp, lift, handle, carry or feel objects frequently; will interact with people and technology frequently during a shift/workday; will lift, push or pull objects on an occasional basis; will sit, stand or walk short distances for up to the entire duration of a shift/workday; will use telephone, computer system, email, and other electronic devices frequently to communicate with internal and external customers or vendors.

  Safety level: Non‑Safety Sensitive. (Jobs with the Safety‑Sensitive designation are those that include tasks or duties that the employer reasonably believes could affect the safety and health of the employee performing the task or others such as operating a vehicle, operating equipment, operating machinery or power tools, repairing/maintaining the operation of any vehicle/equipment, the handling/disposal/transport of hazardous materials, or the handling/treatment/disposal of potentially flammable/combustible materials.)

  Skills: maybe just Microsoft Office proficiency; but we already mentioned in Requirements. Could still have Skills section with that. But to avoid duplication, we could keep Skills as Microsoft Office proficiency. It's okay. Benefits list as above. Pay section: Market Competitive Salary (paid weekly). Now ensure no duplicated lines: we have salary in Pay only; benefits list excludes salary. Check for any leftover boilerplate: we removed EEO, notice to external search firms, etc. Now