Senior Estimator

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Company: Trueline's client, large builder, seeking multiple Senior Estimators in Minneapolis, hybrid schedule. - Lead estimating efforts on large, complex projects across sports, data center, federal, manufacturing, ground-up vertical construction. - Base salaries reaching $192,300 in Minneapolis and up to $211,500 in select markets, plus incentive plan. - Hiring at two senior estimating levels: experienced estimators with 6+ years in construction to seasoned estimating leaders with 9+ years. - Minneapolis priority location, exceptional candidates near other regional offices considered. - What You'll Do: list of duties. - Must-Haves: requirements. - Nice-to-Haves: qualifications/skills. - Our Client Offers: benefits, pay, schedule, etc. We need to avoid repeating job title as heading. No Job ID. We need to include sections only if content present. We need to use

for section headings. We need

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is EEO statement; we should drop that. Also drop "Trueline and its clients are unabashed equal-opportunity employers..." etc. Also drop "Work booked through 2030..." maybe that's substantive? It's about work pipeline; could be considered benefit? Might be considered part of benefits? It's not typical benefit but could be considered "Work booked through 2030" as a statement about job security. Might be considered part of benefits? The instruction: include a section ONLY when posting has real, specific content for it. "Work booked through 2030 at a company that has grown roughly 40% in most years" is specific content about company growth and workload. Could be placed under Benefits or maybe a separate section like "Company Overview". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put that under Benefits or About the role. Probably under Benefits as it's about company stability. We need to avoid filler like "commensurate with experience", "not specified", etc. We have specific salary ranges. We need to include Pay section if posting states them. It does: Base salary of $109,300-$192,300 in Minneapolis, depending on experience and level, and up to $211,500 in select markets. Also plus incentive plan. So Pay section. Schedule: Hybrid schedule, with Tuesday through Thursday in the office and Monday and Friday remote. Also mention ability to work in office Tuesday through Thursday, travel up to 20%, hold driver's license. That's schedule info. So Schedule section. Benefits: list includes medical and prescription drug coverage with vision included at no additional cost, plus dental; 401(k) with generous company match; Paid time off, holidays, other paid leave; Employer-paid life, AD&D, disability insurance; Tuition reimbursement, adoption assistance, gym membership discount program; No-cost mental health support and work-life concierge resources; Work booked through 2030...; clear path to grow; humble respectful culture; etc. Those are benefits. We need to avoid duplicating lines. Ensure we capture all. Now structure: We could have:

  About the role

  ... brief description.

  Responsibilities

  ... list of duties from "What You'll Do as the Senior Estimator:"

  Requirements

  ... Must-Haves

  Qualifications

  maybe combine Nice-to-Haves? Or Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide where Nice-to-Haves go. Could be Qualifications or Skills. Nice-to-Haves includes credentials, experience, understanding, etc. Could be Qualifications. Skills could be specific proficiencies like BIM, tools. But we have proficiency listed under Must-Haves as well. Might be better to put Nice-to-Haves under Qualifications. We also have Skills heading; maybe we can put specific tool proficiencies under Skills. But we already have them in Must-Haves. Could split: Must-Haves as Requirements, Nice-to-Haves as Qualifications, and specific proficiencies as Skills. However we must not invent sections if content is thin. We have content for Skills: proficiency using BIM, plans, project documents; proficiency with estimating and takeoff tools such as WinEst or Bid2Win, On-Screen Takeoff, Bluebeam, and BuildingConnected. That's specific. So we can make a Skills section. Thus: - About the role: brief overview. - Responsibilities: list of duties. - Requirements: Must-Haves (experience, education, ability to lead teams, etc.) - Qualifications: Nice-to-Haves (LEED AP, DBIA, managing estimators, construction law, union experience, specific project experience, trade partner relationships) - Skills: Proficiency with BIM, plans, tools. - Benefits: list of benefits. - Pay: salary ranges and incentive. - Schedule: hybrid schedule, travel, driver's license. We need to ensure we don't repeat content. Let's extract each. About the role: "Trueline's client, one of the largest and most respected builders in the country, is seeking multiple Senior Estimators to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead estimating efforts on large, complex projects across sports, data center, federal, manufacturing, and ground-up vertical construction, with base salaries reaching $192,300 in Minneapolis and up to $211,500 in select markets, plus an incentive plan.The company is hiring at two senior estimating levels, from experienced estimators with 6+ years in construction to seasoned estimating leaders with 9+ years in the industry, and your experience determines where you start. Minneapolis is the priority location, but exceptional candidates near the company's other regional offices will also be considered." We could keep that as prose. Responsibilities: list from "What You'll Do as the Senior Estimator:" each bullet. Let's list: - Lead estimating efforts on large, complex projects from early design through final pricing and submission - Develop conceptual, detailed, and self-perform estimates and cost models, including general conditions - Organize, research, and plan estimate preparation, pricing, scheduling, and submission - Facilitate kickoffs, status updates, plan flips, and final estimate reviews - Develop trade partner strategy, select subcontractors for bidding, and review subcontractor proposals - Complete quantity surveys using BIM, plans, and other project documents - Research tax laws, collective bargaining agreements, and permits, and incorporate all contract requirements into complete, reliable estimates - Write and submit RFIs, and keep owners, architects, engineers, team members, and subcontractors aligned on scope - Analyze historical project data and cost history to price current work at both the unit-price and building-systems level - Help select building systems and support project scheduling - Lead, train, and mentor estimators, including performance evaluations at the senior level That's all. Requirements (Must-Haves): - 6+ years of construction industry experience, including leading full estimates on large, complex commercial projects. Candidates with 9+ years in construction, including 6+ years in estimating, will be considered for the senior level. - Associate or bachelor's degree in Construction Management, Estimating, Engineering, or a related field, or equivalent experience - Experience leading teams of estimators and managing multiple complex estimates at once - Ability to build conceptual, detailed, and self-perform estimates using cost history and past project data - Proficiency using BIM, plans, and project documents to quantify work - Proficiency with estimating and takeoff tools such as WinEst or Bid2Win, On-Screen Takeoff, Bluebeam, and BuildingConnected - A humble, team-first approach and the integrity to do the right thing when nobody's looking - Ability to work in the office Tuesday through Thursday, travel up to 20%, and hold a current driver's license - Authorization to work in the U.S. without current or future visa sponsorship Note: Some of these overlap with Skills and Schedule. We'll keep them in Requirements as they are must-haves. However we also have a separate Skills section for proficiency with BIM and tools. To avoid duplication, we might move those proficiency items to Skills and keep Requirements focused on experience, education, leadership, humble approach, work schedule, travel, driver's license, work authorization. But the instruction: preserve ALL substantive information; do not invent or summarize away detail. If we split, we need to ensure we don't lose any info. We can keep proficiency in Requirements and also have Skills section maybe redundant but allowed? Might be considered duplication. Better to avoid duplication: we can put proficiency under Skills, and keep Requirements without those proficiency lines. But then we would be omitting them from Requirements, which is part of Must-Haves. However we can still include them in Requirements as part of Must-Haves but also list them under Skills? That would duplicate. The instruction says "Do NOT repeat the job title as a heading" but doesn't explicitly forbid repeating content across sections. However earlier: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should aim to avoid unnecessary duplication. However we need to follow the instruction to use sections for specific types: Responsibilities (list of duties/requirements/benefits), Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. Thus: - Responsibilities: duties list. - Requirements: mandatory experience, education, leadership ability, humble approach, work authorization, ability to work Tue-Thu, travel up to 20%, driver's license. (These are must-haves not covered elsewhere.) - Qualifications: nice-to-haves (LEED AP/DBIA, managing estimators, construction law, union experience, specific project experience, trade partner relationships). - Skills: proficiency using BIM, plans, project documents; proficiency with estimating and takeoff tools (WinEst/Bid2Win, On-Screen Takeoff, Bluebeam, BuildingConnected). - Benefits: list from "Our Client Offers:" including medical, dental, vision, 401(k), PTO, holidays, employer-paid life/AD&D/disability, tuition reimbursement, adoption assistance, gym discount, no-cost mental health support, work-life concierge, work booked through 2030, 40% growth, clear path to grow, humble respectful culture, etc. - Pay: base salary range and incentive plan. - Schedule: hybrid schedule (Tue-Thu in office, Mon-Fri remote) plus maybe note about travel? Travel is already in Requirements. But schedule section could include hybrid schedule and remote days. We'll keep schedule as hybrid schedule details. Now we need to ensure we don't include boilerplate like EEO statement at end. Remove. Now produce HTML. We'll need to wrap each section in

  heading then content. For lists, use

  • . For prose, use

    . Let's craft. About the role paragraph: combine the initial description. "Trueline's client, one of the largest and most respected builders in the country, is seeking multiple Senior Estimators to join their team in Minneapolis, MN, on a hybrid schedule. You'll lead estimating efforts on large, complex projects across sports, data center, federal, manufacturing