Recruiter
Flare Construction, LLC · Coalville, UT · 3 wk ago
Human ResourcesFull-time
We need to output HTML fragment with sections: About the role? The posting includes "About Us", "About This Role", "What You'll Do", "What You'll Bring", "What You'll Get", "Work Environment", "Why Flare", "Benefits", "Equal Opportunity Employer" (but we must remove EEO boilerplate). Also we must not repeat job title as heading. Use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings appropriately. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to map content to these headings appropriately. 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. But we must only include a section when posting has real, specific content for it. So we need to decide which sections apply.
We have content: About Us (company description) maybe "About the role"? Actually "About This Role" could map to "About the role". Responsibilities: "What You'll Do". Requirements/Qualifications/Skills: "What You'll Bring" includes experience, education, skills. Benefits: there is a Benefits section listing many items. Pay: not mentioned. Schedule: not mentioned (though mentions travel % and in-person). Could we treat "Work Environment" as Schedule? Not exactly. The instruction says only create Pay/Schedule/Benefits sections if posting actually states them. Benefits is stated, so include Benefits. Pay not stated, so omit. Schedule not explicitly stated (though mentions travel % and in-person). Might be considered schedule? Probably not; we should omit Schedule if not explicit. Also we could include "About the role" (About This Role). Responsibilities (What You'll Do). Requirements (maybe combine Qualifications and Skills). Could separate into Requirements and Skills? But we can combine into one section if we want fewer sections. The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements, Benefits. Possibly also "Work Environment" but that's not in the list of allowed headings; we could maybe treat as part of About the role or Responsibilities? But we need to use only those headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. So we can map:
- About the role: combine About Us and About This Role? Actually About Us is company description; About This Role is role description. Could put both under About the role.
- Responsibilities: What You'll Do.
- Requirements: What You'll Bring (includes experience, education, skills, driver's license, travel). Could also split into Qualifications and Skills but we prefer few sections.
- Benefits: Benefits list.
We must not include EEO boilerplate. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Equal Opportunity Employer" lines.
We must preserve all substantive information. So we need to include details: company established 1976, Quanta Services, full-service contractor heavy civil industrial energy construction in 12 western states, growth, retention, etc. Also About This Role: serving Oil & Gas Infrastructure and Civil & ROW Construction markets across Utah, Idaho, Nevada, Wyoming, Arizona, surrounding states since 1976. Looking for Recruiter who finds great people via relationships, networking, time at colleges, technical schools, community, industry events, building connections, thrives on being out in community, energized rather than drained by full recruiting calendar. Own full-cycle recruiting and employer brand, working closely with HR Generalist on onboarding and other duties in Coalville office.
Responsibilities list bullet points.
What You'll Bring: 2+ years recruiting or TA experience preferred (construction/trades plus), familiarity with ATS, LinkedIn Recruiter, MS Office, working knowledge of employment law and recruiting best practices, valid driver's license and ability to travel for events, Associate's degree in HR, Business, or related field required preferred (maybe required? It says "required preferred" ambiguous; we keep as stated), excellent communication skills, ability to engage candidates across channels including social media management and events, demonstrated ability to manage relationships with external partners and leverage talent acquisition platforms for lead generation, outgoing and energetic, natural ability to start conversations and build rapport, comfortable managing high volume of open reqs and shifting priorities quickly during peak hiring periods without losing attention to detail.
What You'll Get: Work Environment: in-person role based out of Coalville, UT office. When not representing Flare at job fair, campus visit, or recruiting event, you'll be working from Coalville office alongside HR team — not remote or hybrid. Candidates must be willing and able to report to Coalville office regularly. Approximately 10–15% travel required for job fairs, campus visits, recruiting events.
Why Flare: Flare Construction has been building Western US's infrastructure since 1976 — heavy civil, industrial, and energy construction across Utah, Idaho, Nevada, Wyoming, Arizona, and surrounding states. We're growing, and this role is part of how we're getting ready for it.
Benefits list: 401(k), 401(k) matching, AD&D insurance, Dental insurance, Disability insurance, Employee assistance program, Employee discount, Flexible spending account, Health insurance, Health savings account, Life insurance, Paid time off, Corporate Discounts, Vision insurance.
We need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. So we can map:
- About the role: combine About Us and About This Role? Actually About Us is company description; About This Role is role description. Could put both under About the role.
- Responsibilities: What You'll Do.
- Requirements: What You'll Bring (includes experience, education, skills, driver's license, travel). Could also split into Qualifications and Skills but we prefer few sections.
- Benefits: Benefits list.
We must not include EEO boilerplate. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Equal Opportunity Employer" lines.
We must preserve all substantive information. So we need to include details: company established 1976, Quanta Services, full-service contractor heavy civil industrial energy construction in 12 western states, growth, retention, etc. Also About This Role: serving Oil & Gas Infrastructure and Civil & ROW Construction markets across Utah, Idaho, Nevada, Wyoming, Arizona, surrounding states since 1976. Looking for Recruiter who finds great people via relationships, networking, time at colleges, technical schools, community, industry events, building connections, thrives on being out in community, energized rather than drained by full recruiting calendar. Own full-cycle recruiting and employer brand, working closely with HR Generalist on onboarding and other duties in Coalville office.
Responsibilities list bullet points.
What You'll Bring: 2+ years recruiting or TA experience preferred (construction/trades plus), familiarity with ATS, LinkedIn Recruiter, MS Office, working knowledge of employment law and recruiting best practices, valid driver's license and ability to travel for events, Associate's degree in HR, Business, or related field required preferred (maybe required? It says "required preferred" ambiguous; we keep as stated), excellent communication skills, ability to engage candidates across channels including social media management and events, demonstrated ability to manage relationships with external partners and leverage talent acquisition platforms for lead generation, outgoing and energetic, natural ability to start conversations and build rapport, comfortable managing high volume of open reqs and shifting priorities quickly during peak hiring periods without losing attention to detail.
What You'll Get: Work Environment: in-person role based out of Coalville, UT office. When not representing Flare at job fair, campus visit, or recruiting event, you'll be working from Coalville office alongside HR team — not remote or hybrid. Candidates must be willing and able to report to Coalville office regularly. Approximately 10–15% travel required for job fairs, campus visits, recruiting events.
Why Flare: Flare Construction has been building Western US's infrastructure since 1976 — heavy civil, industrial, and energy construction across Utah, Idaho, Nevada, Wyoming, Arizona, and surrounding states. We're growing, and this role is part of how we're getting ready for it.
Benefits list: 401(k), 401(k) matching, AD&D insurance, Dental insurance, Disability insurance, Employee assistance program, Employee discount, Flexible spending account, Health insurance, Health savings account, Life insurance, Paid time off, Corporate Discounts, Vision insurance.
We need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
... combined About Us and About This Role ...
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
after Requirements without heading? The instruction says use
for section headings; doesn't forbid plain
sections without heading? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. So we can have prose paragraphs under headings. So we could add a
under Requirements for work environment details. But the work environment is not a requirement; it's more about job conditions. Could be part of About the role? Might be okay to add a separate section "Work Environment" but not in list; but we could still use
with custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but suggests using those. Safer to stick to those. So we could incorporate work environment details into About the role or Responsibilities. Perhaps add a sentence in About the role about location: "This is an in-person role based out of our Coalville, UT office, with approximately 10–15% travel required for job fairs, campus visits, and recruiting events." That fits.
Thus About the role paragraph will include company description, role description, and work environment/travel.
Now Benefits list: need to list each benefit once.
Benefits: 401(k), 401(k) matching, AD&D insurance, Dental insurance, Disability insurance, Employee assistance program, Employee discount, Flexible spending account, Health insurance, Health savings account, Life insurance, Paid time off, Corporate Discounts, Vision insurance.
We should ensure not duplicate 401(k) and 401(k) matching separate items.
Now produce HTML
for prose. So we can have prose paragraphs under headings. So we could add a
under Requirements for work environment details. But the work environment is not a requirement; it's more about job conditions. Could be part of About the role? Might be okay to add a separate section "Work Environment" but not in list; but we could still use