Project Executive- Commercial and Industrial Electrical Construction
Kelso Industries · Atlanta, GA · 1 mo ago
On-siteSales$150k–$175k/yrFull-time
We need to output only HTML fragment, with sections for headings where content exists. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content.
The posting includes:
- Intro paragraph about Kelso Industries and Wallace Electric Company seeking Project Executive. That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content.
The posting includes:
- Intro paragraph about Kelso Industries and Wallace Electric Company seeking Project Executive. That's about the role. So we can have About the role
with paragraphs.
- Responsibilities: there is a "Key Responsibilities" section with subpoints. We'll put under Responsibilities
with - items.
- Qualifications: there is a "Qualifications" section with Education, Experience, Preferred Qualifications, Preferred Certifications and Licenses, Technical Knowledge, Required Competencies, Physical & Work Environment, KPIs, Reports To, Compensation Package. Many of these could be considered Qualifications or Requirements. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings.
We need to include sections only when posting has real, specific content. Avoid filler like "commensurate with experience". We have actual content for many.
We need to decide which headings to use: About the role, Responsibilities, Qualifications (maybe also Requirements?), Skills, Benefits, Pay, Schedule.
We have Pay: "Compensation Package: Salary: $150,000-$175,000/yr with bonus. Bonus is discretionary and will be based on performance. Compensation includes comprehensive benefits-medical, dental, vision, matching 401k, company vehicle or monthly car allowance, fuel/expense card(s), and vacation days." That's pay and benefits. So we can have
Pay
with salary range and bonus info. And Benefits
with list of benefits.
Schedule: Not mentioned explicitly. There's "Ability to travel as necessary". No schedule like full-time, part-time, shift. So we should not create Schedule section.
Skills: Could be under "Required Competencies" and "Technical Knowledge". We could put under Skills
a list of competencies and technical knowledge.
Requirements: Could be Education, Experience, etc. But we already have Qualifications. Perhaps we can combine Education/Experience under Requirements, and preferred qualifications under Qualifications? But we need to avoid duplication. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. Let's think: Requirements could be mandatory: Education (Bachelor's degree or equivalent), Experience (10+ years progressive, 5+ years leadership, demonstrated success managing $5M-$100M+). Qualifications could be preferred qualifications (preferred degree, 10-15 years, etc.) plus certifications, technical knowledge, competencies. That seems reasonable.
Skills: Could be the "Required Competencies" list.
Benefits: list of benefits.
Pay: salary range and bonus.
We also have "Reports To: President of Wallace Electric Co". That could be part of About the role or maybe a separate metadata but we can fold into About the role paragraph.
We need to preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all details from the posting, except boilerplate like recruiter notice, EEO, etc. We must keep the intro about Kelso Industries, Wallace Electric Company seeking Accomplished AND Results-Driven Project Executive, etc. Also the "Why Join Kelso Industries?" section at end includes growth opportunities, culture, impact, competitive compensation & benefits, diversity statement. That's substantive; we should include that maybe under About the role or a separate section? Could be part of About the role or maybe a separate "Why Join Kelso Industries?" but we only allowed headings from list. Could incorporate into About the role as additional paragraphs.
We must not repeat the job title as a heading. The job title is "Accomplished AND Results-Driven Project Executive". We should not put that as heading.
We must not put Job ID/requisition numbers as headings; none present.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Recruiter Notice: We respectfully ask external recruiters and staffing agencies not to submit candidates. We only accept direct applications." That's a notice but not exactly boilerplate; it's a instruction to recruiters. Should we keep? It's not about the job; it's a notice. The instruction says remove application instructions. This is a notice to recruiters, maybe considered boilerplate? It's not EEO but still a notice. Safer to remove it.
Also "Please contact Shon by email or phone. Email: scomer@wallaceelectric.com Contact #: 334-750-7390." That's application instruction; remove.
Also "Why Join Kelso Industries?" section includes growth opportunities etc. Keep.
Also diversity statement at end: "Kelso Industries celebrates diversity and is committed to creating an inclusive environment..." That's EEO boilerplate? It's a diversity statement; might be considered EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that diversity statement.
Also the earlier "Together We Build – Partnership, Innovation, Excellence, and Safety At Kelso Industries, 5,000+ employees across 40+ companies work together..." That's intro about company; keep.
Now we need to output HTML fragment only.
Let's structure:
About the role
...
Then Responsibilities
- ... each responsibility
Then Requirements
- Education: Bachelor's Degree from an accredited institution. Will substitute degree for experience. Equivalent combination of education and industry experience considered.
- Experience: 10+ years of progressive experience in commercial and industrial electrical construction.
- Experience: 5+ years of leadership experience managing multiple projects and project teams.
- Experience: Demonstrated success managing large-scale electrical projects ranging from $5M to $100M+.
- Experience: Experience with commercial and industrial facilities, power distribution systems, data centers, healthcare, and automotive preferred.
But we need to preserve all details; we can combine into sentences.
Better to keep as for prose and
for list. The instruction: Use - for any list of duties/requirements/benefits, and
for prose. So for requirements we should use list.
We have many requirement items; we can list each bullet.
Now
Qualifications
We need to list preferred qualifications, certifications, technical knowledge, required competencies, physical & work environment, KPIs, reports to? Actually reports to maybe part of About the role.
We'll list preferred qualifications as bullet list.
Then certifications as bullet list.
Then technical knowledge as bullet list.
Then required competencies as bullet list.
Then physical & work environment as bullet list.
Then KPIs as bullet list.
We must not create sections with filler; all have content.
Now Skills
We could list the required competencies as skills; but we already have them under Qualifications. Might be duplication. Perhaps better to put Required Competencies under Skills, and keep Qualifications for preferred qualifications, certifications, technical knowledge. Let's decide.
We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to allocate content accordingly.
Let's map:
- About the role: intro paragraph about Kelso, Wallace Electric, role purpose, reporting to President, maybe also "Why Join Kelso Industries?" (growth opportunities, culture, impact, competitive compensation & benefits, diversity statement removed). We'll keep growth opportunities, culture, impact, competitive compensation & benefits (but compensation & benefits already covered in Pay/Benefits; we can mention that they offer competitive compensation & benefits but not repeat details). We'll keep it brief.
- Responsibilities: list of key responsibilities (Leadership & Operations, Project Management, Financial Management, Client Relations & Business Development, Contract & Risk Management, Safety & Quality). We'll break into bullet list.
- Requirements: mandatory qualifications: Education, Experience (10+ years progressive, 5+ years leadership, demonstrated success managing $5M-$100M+, experience with certain facilities preferred). We'll list.
- Qualifications: preferred qualifications (Bachelor's degree in specific fields, Master's preferred, 10-15 years experience, managing portfolios >$50M, overseeing $25M-$100M+, diverse portfolio, understanding of power distribution, advanced knowledge of financial management, experience with delivery methods, mentoring, relationships, negotiating contracts, proficiency with software, business growth, communication skills, regulated environments, advanced training, developing teams, ability to travel, security clearance plus). We'll list.
- Skills: maybe the "Required Competencies" list (Executive leadership and team development, Strategic planning and decision-making, Financial and business acumen, Client relationship management, Contract negotiation and administration, Risk management, Communication and presentation skills, Conflict resolution and problem-solving, Organizational and time management skills, Safety leadership and compliance). Also maybe Technical Knowledge? But we can put Technical Knowledge under Qualifications or Skills. Let's put Technical Knowledge under Skills as well, but we need to avoid duplication. Could split: Skills = Required Competencies + Technical Knowledge. That seems okay.
- Benefits: list of benefits from compensation package: medical, dental, vision, matching 401k, company vehicle or monthly car allowance, fuel/expense card(s), vacation days.
- Pay: salary range $150,000-$175,000/yr with bonus discretionary based on performance.
- Schedule: not present, so omit.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits stated, so include them.
Now we need to ensure we don't repeat info. For example, "competitive compensation & benefits" in Why Join Kelso Industries is generic; we can keep that sentence but not repeat specifics.
Now we need to strip out boilerplate: Recruiter Notice, contact info, EEO/diversity statement, maybe also "Together We Build – Partnership, Innovation, Excellence, and Safety At Kelso Industries, 5,000+ employees across 40+ companies work together to deliver exceptional HVAC, mechanical, plumbing, refrigeration, and electrical solutions nationwide. Join us to grow your career, make an impact, and be part of a team where innovation, excellence, and safety come first." That's fine.
Also "Why Join Kelso Industries? Join us and be part of a team dedicated to creating efficient, sustainable, and high-performance environments that make a lasting impact across the industrial, commercial, and institutional sectors. Here you will experience:" then bullet list: Growth Opportunities, Company Culture, Impact, Competitive Compensation & Benefits. We'll keep those as prose under About the role maybe.
Now we need to ensure we don't include duplicated lines. The posting has some duplicated lines like "Experience 10+ years of progressive experience in commercial and industrial electrical construction." appears both in Qualifications and Requirements? Actually it's in Qualifications under Experience and also under PREFERRED QUALIFICATIONS. We'll keep only once in Requirements (mandatory) and maybe also in Qualifications as preferred? But we need to preserve all substantive information; if we omit a duplicate, we might be losing info but it's duplicate so okay. We'll keep the mandatory experience in Requirements; the preferred experience (10-1
Pay
with salary range and bonus info. AndBenefits
with list of benefits. Schedule: Not mentioned explicitly. There's "Ability to travel as necessary". No schedule like full-time, part-time, shift. So we should not create Schedule section. Skills: Could be under "Required Competencies" and "Technical Knowledge". We could put underSkills
a list of competencies and technical knowledge. Requirements: Could be Education, Experience, etc. But we already have Qualifications. Perhaps we can combine Education/Experience under Requirements, and preferred qualifications under Qualifications? But we need to avoid duplication. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. Let's think: Requirements could be mandatory: Education (Bachelor's degree or equivalent), Experience (10+ years progressive, 5+ years leadership, demonstrated success managing $5M-$100M+). Qualifications could be preferred qualifications (preferred degree, 10-15 years, etc.) plus certifications, technical knowledge, competencies. That seems reasonable. Skills: Could be the "Required Competencies" list. Benefits: list of benefits. Pay: salary range and bonus. We also have "Reports To: President of Wallace Electric Co". That could be part of About the role or maybe a separate metadata but we can fold into About the role paragraph. We need to preserve all substantive information, not invent or summarize away detail. Must not omit any substantive info. So we need to include all details from the posting, except boilerplate like recruiter notice, EEO, etc. We must keep the intro about Kelso Industries, Wallace Electric Company seeking Accomplished AND Results-Driven Project Executive, etc. Also the "Why Join Kelso Industries?" section at end includes growth opportunities, culture, impact, competitive compensation & benefits, diversity statement. That's substantive; we should include that maybe under About the role or a separate section? Could be part of About the role or maybe a separate "Why Join Kelso Industries?" but we only allowed headings from list. Could incorporate into About the role as additional paragraphs. We must not repeat the job title as a heading. The job title is "Accomplished AND Results-Driven Project Executive". We should not put that as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Recruiter Notice: We respectfully ask external recruiters and staffing agencies not to submit candidates. We only accept direct applications." That's a notice but not exactly boilerplate; it's a instruction to recruiters. Should we keep? It's not about the job; it's a notice. The instruction says remove application instructions. This is a notice to recruiters, maybe considered boilerplate? It's not EEO but still a notice. Safer to remove it. Also "Please contact Shon by email or phone. Email: scomer@wallaceelectric.com Contact #: 334-750-7390." That's application instruction; remove. Also "Why Join Kelso Industries?" section includes growth opportunities etc. Keep. Also diversity statement at end: "Kelso Industries celebrates diversity and is committed to creating an inclusive environment..." That's EEO boilerplate? It's a diversity statement; might be considered EEO/equal-opportunity boilerplate. The instruction says remove EEO/equal-opportunity boilerplate. So we should remove that diversity statement. Also the earlier "Together We Build – Partnership, Innovation, Excellence, and Safety At Kelso Industries, 5,000+ employees across 40+ companies work together..." That's intro about company; keep. Now we need to output HTML fragment only. Let's structure:About the role
...
ThenResponsibilities
- ... each responsibility
Requirements
- Education: Bachelor's Degree from an accredited institution. Will substitute degree for experience. Equivalent combination of education and industry experience considered.
- Experience: 10+ years of progressive experience in commercial and industrial electrical construction.
- Experience: 5+ years of leadership experience managing multiple projects and project teams.
- Experience: Demonstrated success managing large-scale electrical projects ranging from $5M to $100M+.
- Experience: Experience with commercial and industrial facilities, power distribution systems, data centers, healthcare, and automotive preferred.
for prose and
- for list. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So for requirements we should use list. We have many requirement items; we can list each bullet. Now
Qualifications
We need to list preferred qualifications, certifications, technical knowledge, required competencies, physical & work environment, KPIs, reports to? Actually reports to maybe part of About the role. We'll list preferred qualifications as bullet list. Then certifications as bullet list. Then technical knowledge as bullet list. Then required competencies as bullet list. Then physical & work environment as bullet list. Then KPIs as bullet list. We must not create sections with filler; all have content. NowSkills
We could list the required competencies as skills; but we already have them under Qualifications. Might be duplication. Perhaps better to put Required Competencies under Skills, and keep Qualifications for preferred qualifications, certifications, technical knowledge. Let's decide. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to allocate content accordingly. Let's map: - About the role: intro paragraph about Kelso, Wallace Electric, role purpose, reporting to President, maybe also "Why Join Kelso Industries?" (growth opportunities, culture, impact, competitive compensation & benefits, diversity statement removed). We'll keep growth opportunities, culture, impact, competitive compensation & benefits (but compensation & benefits already covered in Pay/Benefits; we can mention that they offer competitive compensation & benefits but not repeat details). We'll keep it brief. - Responsibilities: list of key responsibilities (Leadership & Operations, Project Management, Financial Management, Client Relations & Business Development, Contract & Risk Management, Safety & Quality). We'll break into bullet list. - Requirements: mandatory qualifications: Education, Experience (10+ years progressive, 5+ years leadership, demonstrated success managing $5M-$100M+, experience with certain facilities preferred). We'll list. - Qualifications: preferred qualifications (Bachelor's degree in specific fields, Master's preferred, 10-15 years experience, managing portfolios >$50M, overseeing $25M-$100M+, diverse portfolio, understanding of power distribution, advanced knowledge of financial management, experience with delivery methods, mentoring, relationships, negotiating contracts, proficiency with software, business growth, communication skills, regulated environments, advanced training, developing teams, ability to travel, security clearance plus). We'll list. - Skills: maybe the "Required Competencies" list (Executive leadership and team development, Strategic planning and decision-making, Financial and business acumen, Client relationship management, Contract negotiation and administration, Risk management, Communication and presentation skills, Conflict resolution and problem-solving, Organizational and time management skills, Safety leadership and compliance). Also maybe Technical Knowledge? But we can put Technical Knowledge under Qualifications or Skills. Let's put Technical Knowledge under Skills as well, but we need to avoid duplication. Could split: Skills = Required Competencies + Technical Knowledge. That seems okay. - Benefits: list of benefits from compensation package: medical, dental, vision, matching 401k, company vehicle or monthly car allowance, fuel/expense card(s), vacation days. - Pay: salary range $150,000-$175,000/yr with bonus discretionary based on performance. - Schedule: not present, so omit. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits stated, so include them. Now we need to ensure we don't repeat info. For example, "competitive compensation & benefits" in Why Join Kelso Industries is generic; we can keep that sentence but not repeat specifics. Now we need to strip out boilerplate: Recruiter Notice, contact info, EEO/diversity statement, maybe also "Together We Build – Partnership, Innovation, Excellence, and Safety At Kelso Industries, 5,000+ employees across 40+ companies work together to deliver exceptional HVAC, mechanical, plumbing, refrigeration, and electrical solutions nationwide. Join us to grow your career, make an impact, and be part of a team where innovation, excellence, and safety come first." That's fine. Also "Why Join Kelso Industries? Join us and be part of a team dedicated to creating efficient, sustainable, and high-performance environments that make a lasting impact across the industrial, commercial, and institutional sectors. Here you will experience:" then bullet list: Growth Opportunities, Company Culture, Impact, Competitive Compensation & Benefits. We'll keep those as prose under About the role maybe. Now we need to ensure we don't include duplicated lines. The posting has some duplicated lines like "Experience 10+ years of progressive experience in commercial and industrial electrical construction." appears both in Qualifications and Requirements? Actually it's in Qualifications under Experience and also under PREFERRED QUALIFICATIONS. We'll keep only once in Requirements (mandatory) and maybe also in Qualifications as preferred? But we need to preserve all substantive information; if we omit a duplicate, we might be losing info but it's duplicate so okay. We'll keep the mandatory experience in Requirements; the preferred experience (10-1