Estimator

We need to output HTML fragment with sections: About the role? The posting includes "Brief Description" then "Requirements" with subheadings: Essential Functions / Job Duties (list), Education Required, Experience & Skills, Work Environment & Physical Requirements, Summary (company description), Why Join Mazzella? (benefits), At Mazzella, Our Core Values Drive Everything We Do (core values). Also there is "Pre-Employment Requirements". We need to include sections only when real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to map content accordingly. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. We must not repeat job title as heading. We must not put Job ID etc. We need to preserve all substantive info. We need to decide which sections to include based on content. - About the role: could be the brief description. So we can have

About the role

with paragraph from Brief Description. - Responsibilities: could be the Essential Functions / Job Duties list. So

Responsibilities

with

• items. - Requirements: could combine Education Required and Experience & Skills? The instruction says we can have Requirements section; maybe we put education and experience there. But also there is Qualifications and Skills separate headings. We could split: Requirements for education, Qualifications for preferred degree? Actually typical: Requirements = mandatory; Qualifications = preferred; Skills = skills. But we can follow the instruction: Use headings as needed; we can include Requirements, Qualifications, Skills if content exists. Let's parse: Education Required: High School Diploma or GED. Preferred: Degree in Business, Engineering, Project Management, Operations Management, or related discipline. Experience & Skills: Minimum 3 years of estimating, industrial equipment, or modernization experience. Strong math skills and proficiency with Microsoft Office. Estimating spreadsheets and standard quoting tools. Solid communication, organization, and multitasking skills. Ability to interpret crane GA drawings, structural plans, and technical documents. Preferred: Crane estimating experience and familiarity with OSHA/ASME/CMAA. CAD/eDrawings viewer for reviewing drawings Thus we can have: -

  Requirements

  : Education Required (HS diploma/GED) and Minimum 3 years experience. -

  Qualifications

  : Preferred degree. -

  Skills

  : Strong math skills, proficiency with MS Office, estimating spreadsheets, communication, organization, multitasking, ability to interpret drawings, crane estimating experience, OSHA/ASME/CMAA familiarity, CAD/eDrawings viewer. But we need to avoid filler like "Preferred:" maybe still okay as content. Work Environment & Physical Requirements: Remote and/or Office-based. Travel up to 10%. Pre-Employment Requirements: Background check, drug screen, and E-Verify. We could put that under a section maybe "Work Environment" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No explicit Work Environment. However we could incorporate into Responsibilities or Requirements? Probably better to create a section "Work Environment" but instruction says use those headings e.g., but not limited? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we could still use those headings only. However we have info about work environment and travel; we could put under Responsibilities? Not ideal. Could create a section "Work Environment" as

  Work Environment

  though not in list but maybe acceptable. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for those categories, but we could also use other headings if needed? It says "use

  for section headings (e.g. ...)" meaning we should use h3 for headings, and those are examples of possible headings. So we can use other headings as needed. We'll include Work Environment. Benefits: The "Why Join Mazzella?" section lists benefits: Team-Oriented Environment, Work-Life Balance, Growth and Development, Humble, Hungry, Smart Culture, Market-Competitive Salaries, Comprehensive Benefits (list), Free Virtual Doctor Visits, Tuition Reimbursement. Also core values section. We need Benefits section: include those benefits. Pay: Not explicitly stated; they mention "Market-Competitive Salaries" but no specific numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have explicit list, so we can include Benefits. Pay: they say "Market-Competitive Salaries" but no specific figure; that's vague but still states that salaries are market-competitive. Is that enough to create a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. "Market-competitive salaries" is a statement about pay, albeit not specific. It might be considered stating pay. However they also say prefer a few substantive sections over many thin ones. Could include Pay with that statement. But we also have Benefits already. Schedule: Travel up to 10% maybe considered schedule? Not exactly schedule. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay (maybe), Work Environment. We need to ensure we don't create sections with filler like "commensurate with experience". We have concrete info. Now we need to output only HTML fragment, no markdown fences. Let's craft:

  About the role

  The Crane Estimator develops accurate and timely cost estimates for overhead crane systems, hoists, runway structures, electrification, installation labor, equipment, subcontractors, and field electrical scope.

  Responsibilities

  • Analyze bid specifications, drawings, RFQs.
  • Prepare complete estimates for cranes, hoists, electrification, controls, and installation.
  • Create estimates and respond to sales requests in real time.
  • Develop scope notes, clarifications, and exclusions with consistency.
  • Select crane configurations (top-running, under-running, single/double girder).
  • Determine hoist/trolley type, lift, speed, reeving, and duty cycle.
  • Identify appropriate controls, panels, festoon, conductor bar, and power requirements.
  • Coordinate with engineering regarding loading, deflection criteria, and runway interface.
  • Request and evaluate vendor quotations for hoists, controls, electrification, and auxiliary equipment.
  • Level subcontractor installation quotes and validate scope coverage.
  • Coordinate with engineering, operations, and project management.
  • Support project handoffs and ensure clear communication of scope.
  • Participate in Lifelong Learning and ongoing improvement of estimating tools and processes.

  Requirements

  • High School Diploma or GED.
  • Minimum 3 years of estimating, industrial equipment, or modernization experience.

  Qualifications

  • Preferred: Degree in Business, Engineering, Project Management, Operations Management, or related discipline.
  • Preferred: Crane estimating experience and familiarity with OSHA/ASME/CMAA.

  Skills

  • Strong math skills and proficiency with Microsoft Office.
  • Estimating spreadsheets and standard quoting tools.
  • Solid communication, organization, and multitasking skills.
  • Ability to interpret crane GA drawings, structural plans, and technical documents.
  • CAD/eDrawings viewer for reviewing drawings.

  Benefits

  • Team-Oriented Environment: collaboration and support from colleagues.
  • Work-Life Balance: real balance between professional and personal life.
  • Growth and Development: lifelong learning journey with tailored development opportunities and clear career path.
  • Humble, Hungry, Smart Culture: core values of humility, hunger for excellence, and smart decision‑making.
  • Market‑Competitive Salaries.
  • Comprehensive Benefits: paid time off, affordable health insurance, dental, vision, 401(k) with company match, life insurance, disability insurance.
  • Free Virtual Doctor Visits: Teledoc service with $0 copay.
  • Tuition Reimbursement program.

  Pay

  Market‑competitive salaries.

  Work Environment

  • Remote and/or Office‑based.
  • Travel up to 10%.
  • Pre‑Employment Requirements: Background check, drug screen, and E‑Verify.
  We need to ensure we didn't repeat job title. Good. Check for any boilerplate: we removed EOE/Drug Free Workplace etc. Also removed "At Mazzella, we're more than just a company..." we kept some of that in Benefits? Actually we used the "Why Join Mazzella?" content. We kept the core values? We included them in Benefits as "Humble, Hungry, Smart Culture". The core values section also had descriptions; we could incorporate those but we already captured some. The core values description: "Be Safe – personal commitment to all stakeholder’s well-being; purposeful control of risk Be a Lifelong Learner – routinely acquire new skills and capabilities that bring value Be Humble – lack excessive ego or concerns about status. Emphasize the Team over self Be Hungry – always looking for more, self-motivated, and diligent. Do more than to just get by, committed Be Smart – common sense about people, good judgement, and intuition around their impact on group dynamics". We could add those as part of Benefits or maybe a separate section "Culture". But we already have Benefits covering culture; we could add a subsection but we can incorporate into Benefits as list items. However we need to preserve all substantive information; we must not lose the core values details. We included only "Humble, Hungry, Smart Culture: core values of humility, hunger for excellence, and smart decision‑making." That loses the detailed descriptions of each value (Be Safe, Be a Lifelong Learner, etc). We need to preserve all substantive info. So we should include those details. We could add a section "Culture" or include under Benefits as list items describing each core value. Let's add a separate section maybe "Culture" but not in the examples; but we can use h3 for any heading. Let's add

  Culture

  with list of core values descriptions. But we already have Benefits section with many items; we could add core values there as list items. However we need to avoid too many sections; but we can add Culture section. Let's restructure: Keep Benefits as tangible benefits (PTO, insurance, etc). Add Culture section for core values and other cultural aspects (Team-Oriented Environment, Work-Life Balance, Growth and Development, Market-Competitive Salaries, etc). Actually those are also cultural/benefit. But we can keep Benefits as the tangible benefits (PTO, insurance, etc) and Culture for the intangible.