Procurement Coordinator — Estimating
Thalle Construction Company, Inc. · Hillsborough, NC · 2 wk ago
PurchasingFull-time
We need to output HTML fragment with sections only where content exists. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those sections that have real specific content.
From posting:
- About the role: description of company, location, etc. Could be "About the role" heading with paragraph(s) about Thalle, location, etc.
- Responsibilities: list of duties (Essential Duties And Responsibilities). Use
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those sections that have real specific content.
From posting:
- About the role: description of company, location, etc. Could be "About the role" heading with paragraph(s) about Thalle, location, etc.
- Responsibilities: list of duties (Essential Duties And Responsibilities). Use - .
- Requirements: maybe "Qualifications Required" and "Physical Requirements". Could combine into Requirements section? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: "Qualifications Required" ->
Qualifications
. "Preferred" maybe also qualifications. Physical Requirements could be part of Requirements or maybe separate but we can include under Requirements.
- Skills: maybe mention proficiency in Excel, Word, Outlook, Smartbid, Kahua, Procore, etc. Could be a Skills section.
- Benefits: they mention competitive salary package with benefits list: Major Medical, Dental, Vision, Short and Long-Term Disability, generous PTO, paid company holidays, Life Insurance, 401K with company match, and more! Also mention competitive salary package based on experience. So we can have Benefits section with list.
- Pay: they say "Compensation is based on experience and qualifications." and "Salary: Competitive compensation package based on experience." That's vague; we should not create Pay section if content is just "commensurate with experience" or "competitive". The rule: 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. For Pay, they say "Competitive compensation package based on experience." That's somewhat filler but it's still stating something. However it's vague like "commensurate with experience". The rule says avoid filler like "commensurate with experience". So we should NOT create Pay section.
- Schedule: not mentioned, so omit.
- Skills: we have specific skills: Smartbid, Kahua, Autodesk, Procore experience; proficiency in Microsoft Excel, Word, Outlook; comfort learning new platforms; clear written communication. So we can create Skills section.
- Requirements: we have required qualifications: 2-5 years experience, etc. Also physical requirements. So we can have Requirements section.
- Qualifications: we have Preferred qualifications (Heavy civil experience, familiarity with regulations, degree). Could be separate Qualifications section. But we already used Requirements for required qualifications; Qualifications for preferred? The instruction list includes both Requirements and Qualifications as separate headings. We can put required under Requirements, preferred under Qualifications.
- About the role: we have company description, location, etc.
Now we need to output HTML fragment only, no extra tags.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... each duty ...
Requirements
- ... required qualifications ...
Maybe also physical requirements as list items.
Qualifications
- ... preferred qualifications ...
Skills
- ... skills ...
Benefits
- ... benefits ...
We must not repeat job title as heading. Not include Job ID etc.
We need to preserve all substantive information. Let's extract.
About the role:
- Thalle Construction Co. Inc. (“Thalle”) is seeking a Procurement Coordinator — Estimating, reporting to the Bid Procurement & Compliance Lead.
- Position located out of office in Hillsborough, NC.
- Thalle, established in 1947, is a heavy civil construction company with corporate office in Hillsborough, NC, and regional office in Alvarado, Texas.
- Thalle has construction projects throughout Southeast, Texas, New Jersey with growth nationwide.
- Diverse project scope includes dams, reservoirs, locks, DOT roadway construction and bridges, large diameter utilities, landfills, mass excavation, wastewater, on-demand emergency services.
- Proud representative of Tully Group (www.tullygroup.us). Tully Group is one of nation’s largest privately held, family-owned construction firm with corporate office in NYC and long history of heavy civil projects in Metro New York Area and New Jersey.
- Safety is TOP priority.
- Thalle offers a competitive salary package with a full range of benefits, including Major Medical, Dental, Vision, Short and Long-Term Disability, generous PTO, paid company holidays, Life Insurance, 401K with a company match, and more!
- Compensation based on experience and qualifications.
- Thalle is an Equal Opportunity Employer, E-Verify, and Drug Free Workplace.
- Regional Office Location: Hillsborough, NC
- Job Title: Procurement Coordinator — Estimating
- Salary: Competitive compensation package based on experience.
We should not repeat job title as heading, but we can include in About the role paragraph maybe.
We should not include EEO etc? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove "Thalle is an Equal Opportunity Employer, E-Verify, and Drug Free Workplace." That's EEO boilerplate. Remove.
Also remove "Regional Office Location: Hillsborough, NC" maybe considered metadata but it's location; we can keep location in About the role.
We should not include "Job Title: Procurement Coordinator — Estimating" as heading but we can mention in paragraph.
We should not include "Salary: Competitive compensation package based on experience." as separate; we can incorporate into Benefits or About the role? It's about compensation; but we decided not to create Pay section. Could mention in Benefits? Actually Benefits section is for benefits; compensation is separate. Since we cannot create Pay section due to vagueness, we could incorporate compensation statement into About the role or Benefits? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits we have actual list, so we can create Benefits. Pay we have only vague statement, so we should not create Pay section. We could still mention compensation in About the role as a sentence.
Now Responsibilities: list from "Essential Duties And Responsibilities". We need to capture each bullet.
Let's extract duties:
- Distribute bid invitations and plan access through plan rooms and bid management platforms; maintain the invitation list by trade, region, and certification status
- Track responses, follow up on non-responders, and escalate coverage gaps to the Bid Procurement & Compliance Lead early enough to act on them
- Maintain the vendor database — contact records, trade coverage, geographic footprint, certification expiration dates, and prior performance flags
- Coordinate outreach in advance of bid rather than on bid week; build and maintain standing bidder lists for Thalle's recurring work types (earthwork, structural concrete, pipelines, treatment plant construction, dams and RCC, marine, landfill, foundations)
- Identify certified firms through state Unified Certification Program (UCP) directories and owner-specific certification lists; verify certification status and NAICS scope before a firm is counted toward a goal
- Assemble and maintain the good-faith-effort file for every goal-bearing pursuit — solicitation evidence, follow-up records, quotes received, rejection rationale, and outreach to assistance organizations
- Track committed participation against the contract goal and produce the participation schedule required at bid submission
- Maintain records in owner-required tracking systems and produce post-award participation reporting as requested
- Collect and review supplier certifications for Build America, Buy America Act (BABAA) requirements on IIJA-funded work, and American Iron and Steel (AIS) requirements on Clean Water and Drinking Water SRF work
- Flag material and equipment items where domestic availability is uncertain, and support waiver research where required
- Maintain the certification log by project so the record is complete and retrievable at award rather than reconstructed months later
- Track funding-source requirements by pursuit — different funding streams carry different compliance regimes, and the differences matter at bid time
- Log incoming quotes, route them to the responsible estimator, and confirm scope acknowledgment
- Confirm that every required certification, participation form, and outreach document is in the submission package before it leaves
- Support the Estimating Admin with addenda distribution to bidders
- Maintain outreach and compliance records to an audit-ready standard
- Contribute to post-bid review with coverage and participation data — which trades came in thin, which firms did not respond, where the bidder list needs building
- Recommend improvements to solicitation templates, tracking tools, and outreach cadence
Now Requirements (required qualifications):
- 2-5 years of experience in construction procurement, bid coordination, contract administration, or compliance support
- Smartbid, Kahua, Autodesk, and/or Procore experience
- Working knowledge of federal, state, or local DBE / MWBE / SBE program requirements
- Strong document control discipline and comfort managing many concurrent deadlines
- Proficiency in Microsoft Excel, Word, and Outlook; comfort learning new platforms quickly
- Clear written communication — much of this role's output is a record someone else will rely on
- High school diploma or equivalent
Physical Requirements (maybe include under Requirements as separate bullet points):
- Ability to safely and successfully perform the essential job functions consistent with the ADA, FMLA and other federal, state and local standards, including meeting qualitative and/or quantitative productivity standards.
- Ability to maintain regular, punctual attendance consistent with the ADA, FMLA and other federal, state and local standards.
- Must be able to lift and carry up to 50 lbs.
- Must be able to talk, listen and speak clearly on telephone.
We could include these as list items under Requirements.
Now Qualifications (preferred):
- Heavy civil, water / wastewater, or public infrastructure experience
- Familiarity with 49 CFR Part 26 (USDOT DBE) and 40 CFR Part 33 (EPA DBE) good-faith-effort standards
- Familiarity with BABAA and American Iron and Steel requirements
- Associate's or bachelor's degree in construction management, business, supply chain, or a related field
- Experience supporting bids in multiple states with differing certification programs
Now Skills: we could separate but many overlap with Requirements. However we can still create Skills section for specific technical skills: Smartbid, Kahua, Autodesk, Procore; Microsoft Excel, Word, Outlook; ability to learn new platforms quickly; clear written communication. But some already in Requirements. To avoid duplication, maybe we combine Skills with Requirements? But instruction says we can have Skills section. We'll include distinct skills not already covered: maybe "Proficiency in Smartbid, Kahua, Autodesk, and/or Procore"; "Proficiency in Microsoft Excel, Word, Outlook"; "Ability to learn new platforms quickly"; "Clear written communication". However these are also in Requirements. To avoid duplication, we could still include but risk repeating. Better to not create Skills section if it duplicates. But we could create Skills section focusing on technical software proficiency: Smartbid, Kahua, Autodesk, Procore; Microsoft Excel, Word, Outlook; ability to learn new platforms. That's still somewhat overlapping but okay.
Alternatively we could omit Skills section and put those under Requirements. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one Requirements section. But we already have Qualifications separate. Let's decide: We'll have About the role, Responsibilities, Requirements (including required qualifications, physical requirements, and skills), Qualifications (preferred), Benefits.
Thus we omit separate Skills section.
Now Benefits: list:
- Major Medical
- Dental
- Vision
- Short and Long-Term Disability
- Gener
Qualifications
. "Preferred" maybe also qualifications. Physical Requirements could be part of Requirements or maybe separate but we can include under Requirements. - Skills: maybe mention proficiency in Excel, Word, Outlook, Smartbid, Kahua, Procore, etc. Could be a Skills section. - Benefits: they mention competitive salary package with benefits list: Major Medical, Dental, Vision, Short and Long-Term Disability, generous PTO, paid company holidays, Life Insurance, 401K with company match, and more! Also mention competitive salary package based on experience. So we can have Benefits section with list. - Pay: they say "Compensation is based on experience and qualifications." and "Salary: Competitive compensation package based on experience." That's vague; we should not create Pay section if content is just "commensurate with experience" or "competitive". The rule: 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. For Pay, they say "Competitive compensation package based on experience." That's somewhat filler but it's still stating something. However it's vague like "commensurate with experience". The rule says avoid filler like "commensurate with experience". So we should NOT create Pay section. - Schedule: not mentioned, so omit. - Skills: we have specific skills: Smartbid, Kahua, Autodesk, Procore experience; proficiency in Microsoft Excel, Word, Outlook; comfort learning new platforms; clear written communication. So we can create Skills section. - Requirements: we have required qualifications: 2-5 years experience, etc. Also physical requirements. So we can have Requirements section. - Qualifications: we have Preferred qualifications (Heavy civil experience, familiarity with regulations, degree). Could be separate Qualifications section. But we already used Requirements for required qualifications; Qualifications for preferred? The instruction list includes both Requirements and Qualifications as separate headings. We can put required under Requirements, preferred under Qualifications. - About the role: we have company description, location, etc. Now we need to output HTML fragment only, no extra tags. Structure:About the role
... paragraphs ...
Responsibilities
- ... each duty ...
Requirements
- ... required qualifications ...
Qualifications
- ... preferred qualifications ...
Skills
- ... skills ...
Benefits
- ... benefits ...