Senior Estimator

We need to output HTML fragment with headings

for sections: 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. Content: - "Who are we?" paragraph: mission statement. That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes "Job Summary" then responsibilities. So we can have sections: About the role (maybe combine Who are we and Job Summary?), Responsibilities, Qualifications, Knowledge, Skills, & Abilities (maybe Skills), Physical Requirements & Environment (maybe not a standard heading; could be omitted unless fits Benefits/Pay/Schedule). There's also Soft Skills list (many bullet points). Also Core Values, Working Environment, etc. But we should only include sections that match the allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. - About the role: could include "Who are we?" and "Job Summary". That's substantive. - Responsibilities: list under "Key Responsibilities:" bullet points. - Requirements: maybe "Qualifications" (7+ years experience etc.) and also "Physical Requirements & Environment"? But Requirements heading is allowed; we can put qualifications there. However we also have a separate "Qualifications" heading allowed. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as possible headings. We need to decide which content goes where. Typically Requirements = qualifications, but they separated them. We could put "Requirements" for mandatory qualifications (years experience, etc.) and "Qualifications" for preferred or additional? But the posting has "Qualifications" heading with bullet list. Then "Knowledge, Skills, & Abilities:" heading. Then "Physical Requirements & Environment". Then "Soft Skills" etc. Then "Core Values". Then "Working Environment". Then EEO etc. We need to map to allowed headings. Let's think: - About the role: company mission + job summary. - Responsibilities: key responsibilities bullet list. - Requirements: maybe the "Qualifications" bullet list (7+ years experience etc.)? Or could be "Requirements" for mandatory qualifications (like 7+ years experience, significant commercial construction experience, proven success on large complex projects). The bullet list under "Qualifications" includes those. So we can put that under Requirements. - Qualifications: maybe the "Knowledge, Skills, & Abilities:" list (Leadership, Executive communication, etc.)? That seems like qualifications/skills. But we also have Skills heading allowed. Could put Knowledge, Skills, & Abilities under Skills. - Skills: maybe the "Soft Skills" list? That's a bunch of behavioral competencies. Could be Skills. - Benefits, Pay, Schedule: we need to see if posting mentions any. I don't see explicit benefits, pay, or schedule. There's "Working Environment Must be able to lift up to 10 pounds May require periods of travel Normal office environment Frequent activity: Sitting, Viewing Computer Screen". That's not benefits/pay/schedule. No mention of salary, benefits, schedule. So we should NOT include Benefits, Pay, Schedule sections because they lack specific content. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to include all substantive info from the posting that fits into these sections. Let's extract: About the role: - "Who are we? At Reeder General Contractors, we are driven by a clear mission: to provide opportunity and add value to the lives of the people we work with. We accomplish this by delivering purpose-driven construction services rooted in a safety-first approach, servant leadership, family values, and an unwavering commitment to excellence. Simply put, our mission is to Make People Better—our employees, our partners, and the communities we serve" - "Job Summary Our Senior Estimator is responsible for the overall project estimate or bid while providing leadership, training, and mentoring for the team under the Director of Preconstruction. This role works closely with clients, architects/engineers, and subcontractors/suppliers to plan cost factors for building projects, and analyzes construction documents, specifications, proposals, and other documentation to prepare accurate time, cost, and labor estimates and bids for projects." We should combine these into a

  maybe two paragraphs. Responsibilities: bullet list under "Key Responsibilities:": - Lead major pursuits and serve as the primary estimating lead on large, complex bids - Develop conceptual budgets during early project planning and preconstruction phases - Establish estimating strategy for each pursuit, including approach, resources, and timeline - Lead bid reviews and present final numbers to leadership prior to submission - Perform risk assessments and identify cost and schedule risks before they impact a project - Review contracts for scope, terms, and exposure ahead of buyout and award - Develop value engineering options that protect scope while improving cost or schedule outcomes - Support business development efforts, including proposal input and client-facing positioning - Participate in owner and architect interviews as a representative of the preconstruction team - Improve estimating procedures, tools, and standards across the department - Lead and mentor estimating staff, providing training and day-to-day guidance - Coordinate scheduling across active pursuits to ensure estimating deadlines and milestones are met We need to preserve all. Requirements: The "Qualifications" bullet list: - 7+ years of estimating experience - Significant commercial construction experience - Proven success on large, complex projects - Expert-level conceptual estimating ability - Strong understanding of current market conditions - Advanced constructability knowledge - Value engineering expertise - Procurement strategy development - Strong understanding of project scheduling - Risk analysis - Cost modeling - Preconstruction planning - Strong presentation skills - Interview experience representing the company to owners and architects We'll put these under Requirements heading. Qualifications: The "Knowledge, Skills, & Abilities:" list: - Leadership - Executive communication - Strategic thinking - Well versed in negotiation and buyout - Coaching - Collaboration - Critical thinking - Client relationship management Also there is "Performance Expectations" list after that, but that might be considered part of Qualifications? Actually after Knowledge, Skills, & Abilities there is "Performance Expectations" with bullet list: - Highly accurate estimates - Strong project win rate - Trusted advisor to operations - Develops future estimators - Protects company profitability - Builds owner and architect confidence We could include Performance Expectations under Qualifications as well, or maybe under Skills? But we already have Skills heading for soft skills. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Qualifications and Skills separate. We need to decide what goes where. The posting has "Knowledge, Skills, & Abilities:" then list, then "Performance Expectations". Then "Physical Requirements & Environment". Then "Soft Skills" (a long list). Then "Our Core Values". Then "Working Environment". Then EEO. Thus we have multiple lists that could be considered skills or qualifications. We need to map to allowed headings without inventing content. We could put: - Qualifications: the "Knowledge, Skills, & Abilities:" list plus maybe Performance Expectations? But Performance Expectations are more like expected outcomes, could be considered qualifications as well. - Skills: the "Soft Skills" list (the long list of behaviors). That seems like skills. Thus we will have: Qualifications heading: include the Knowledge, Skills, & Abilities list and Performance Expectations list (both are substantive). We'll combine them into one

  maybe separate
  for each? The instruction: Use
  • for any list of duties/requirements/benefits. So we can have multiple
    under a section. Skills heading: include the Soft Skills list. We must not include headings with filler. Ensure we have real content. Now we need to strip boilerplate: remove "Who are we?" heading? We'll not use heading for that; just include paragraph. Remove "Job Summary" heading? We'll just include paragraph. Remove "Key Responsibilities:" heading? We'll use

    Responsibilities

    then list. Remove "Qualifications" heading? We'll use

    Requirements

    for the qualifications list (7+ years etc.) and

    Qualifications

    for Knowledge, Skills, & Abilities + Performance Expectations. Remove "Knowledge, Skills, & Abilities:" heading? We'll just list under Qualifications. Remove "Performance Expectations" heading? We'll list under Qualifications as well. Remove "Physical Requirements & Environment" heading? Not allowed heading; we could omit because not Benefits/Pay/Schedule. But it's substantive. However we have no appropriate heading for it; we could maybe put under Requirements? But it's physical requirements, not qualifications. The allowed headings do not include Physical Requirements. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since we don't have a matching heading, we should omit that content? But we must preserve ALL substantive information. However we cannot invent a heading not allowed. The allowed headings list is given as examples; maybe we can use other headings if they exist? The instruction 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 an exhaustive list. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can use any heading that matches content, but we should follow the pattern of those examples. However the examples are typical sections. It might be safe to use headings like "Physical Requirements" if present. But 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 to be safe, we could include a heading "Physical Requirements & Environment" as

    . However the list of examples didn't include it, but it's not prohibited. The important part is not to create sections with filler. Since we have real content, we can include it. But we also have "Soft Skills" which could be a heading under Skills. But we already have Skills heading; we could put the soft skills list under Skills. We also have "Our Core Values" and "Working Environment". Could we include those? They are substantive. But we don't have a matching heading like "Culture" or "Values". Could we create a heading "Core Values"? The examples didn't list it, but it's not prohibited. However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be implying to use those specific headings only. The phrase "e.g." indicates examples, but the later instruction about not creating Pay/Schedule/Benefits sections unless posting states them suggests they care about those specific sections. It might be safer to stick to the given headings only. However we would then lose some substantive info like Physical Requirements &