Environmental Practice Leader Transportation & Natural Resource
PRIME AE Group, Inc. · Akron, OH · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description of role, responsibilities, qualifications, etc. There's no explicit Benefits, Pay, Schedule. So we should not create those sections. We need sections: About the role (maybe a brief overview), Responsibilities (Key Responsibilities), Requirements/Qualifications (What You’ll Bring), Skills (maybe combine?), but we need to follow instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which headings to include based on content.
We have content: "Who We Are" etc. That's about company, not role. But we could put "About the role" summarizing the opportunity. The posting includes "The Opportunity:" paragraph. That could be About the role.
Responsibilities: "What You’ll Do:" and "Key Responsibilities:" combined.
Requirements/Qualifications: "What You’ll Bring:" includes education, experience, etc.
Skills: maybe we can extract skills from requirements: analytical, technical writing, communication, organizational, collaborative, mentoring, client relationships, business development.
But we must not invent content; we can list skills as bullet points from the text.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them into sections.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. The title is "Environmental Practice Leader – Transportation & Natural Resources". We should not put that as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's extract content:
Company description: "We Make Everything Around Us Better At PRIME AE, that’s not a slogan, it’s how we work..." etc. That's about company; could be placed under "About the company"? Not required headings. But we need to preserve all substantive information. Could include under "About the role" maybe? But better to have a section "About PRIME AE" but not in allowed headings list. However instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which headings to include based on content.
We have content: "Who We Are" etc. That's about company, not role. But we could put "About the role" summarizing the opportunity. The posting includes "The Opportunity:" paragraph. That could be About the role.
Responsibilities: "What You’ll Do:" and "Key Responsibilities:" combined.
Requirements/Qualifications: "What You’ll Bring:" includes education, experience, etc.
Skills: maybe we can extract skills from requirements: analytical, technical writing, communication, organizational, collaborative, mentoring, client relationships, business development.
But we must not invent content; we can list skills as bullet points from the text.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them into sections.
We must remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We must not repeat job title as heading. The title is "Environmental Practice Leader – Transportation & Natural Resources". We should not put that as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's extract content:
Company description: "We Make Everything Around Us Better At PRIME AE, that’s not a slogan, it’s how we work..." etc. That's about company; could be placed under "About the company"? Not required headings. But we need to preserve all substantive information. Could include under "About the role" maybe? But better to have a section "About PRIME AE" but not in allowed headings list. However 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 says use those for section headings. It might be okay to add other headings but they'd be non-standard. Safer to stick to those headings and place company info under About the role or maybe under a generic
without heading. But we need to preserve all info; we can include it in a
under About the role. Thus structure:
About the role
... company description + opportunity summary ...
Responsibilities
- ... each responsibility ...
Requirements
- ... each requirement ...
Skills
- ... each skill ...