Live Corporate Events, Account Manager
Production Resource Group · Antioch, TN · 4 wk ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description about PRG and role. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, scam warnings, etc. Also remove navigation/cookie etc. Keep substantive info.
We need to parse the posting: It includes company description, role description, responsibilities list, qualifications & skills, education & experience required, preferred, physical & travel requirements, role development, etc.
We need to decide sections: Possibly "About the role" (overview), "Responsibilities", "Qualifications", "Skills", "Education & Experience", "Physical & Travel Requirements", "Role Development". But we must only use allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add custom headings like Education & Experience or Physical & Travel Requirements unless they map to one of allowed headings. The allowed headings are limited. We can put education/experience under "Qualifications" maybe. Skills under "Skills". Responsibilities under "Responsibilities". About the role under "About the role". Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule specifics. So we should not include those sections.
"Requirements" heading could be used for mandatory qualifications? The posting has "Qualifications & Skills" and "Education & Experience Required". We could treat "Requirements" as the mandatory qualifications (education & experience). Then "Qualifications" could be for preferred? But we have both Qualifications and Skills headings allowed. We need to decide mapping.
We have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can use:
- About the role: overview of PRG and role description (first paragraphs).
- Responsibilities: list of key responsibilities (the bullet list).
- Requirements: mandatory qualifications (Education & Experience Required, plus maybe foundational knowledge etc? Actually those are qualifications/skills). But we can put mandatory experience/education here.
- Qualifications: maybe preferred qualifications? Or we could put "Qualifications & Skills" under Qualifications heading, and Skills under Skills heading? But we have both Qualifications and Skills headings; we could split: Qualifications for education/experience, Skills for skills/competencies. However we already used Requirements for education/experience. Might be overlapping.
Better: Use:
- About the role: overview.
- Responsibilities: responsibilities list.
- Qualifications: mandatory qualifications (education & experience, foundational knowledge, etc.)
- Skills: skills list (communication, organizational, CRM, etc.)
- Possibly Requirements: maybe physical & travel requirements? But we have Physical & Travel Requirements section in posting. Could map to Requirements heading (makes sense). However we already used Qualifications for mandatory qualifications. Could use Requirements for physical & travel requirements. But we also have "Requirements" heading allowed; we can use it for physical & travel requirements. Then we need another heading for mandatory qualifications? Could use "Qualifications" for mandatory qualifications, and "Skills" for skills. That seems plausible.
Thus:
About the role: company description + role overview.
Responsibilities: list of responsibilities.
Qualifications: Education & Experience Required + maybe foundational knowledge? Actually foundational knowledge is more of a qualification. We'll include Education & Experience Required and maybe "Foundational knowledge of live events..." as part of qualifications.
Skills: list of skills (communication, organizational, CRM, etc.)
Requirements: Physical & Travel Requirements (ability to lift, travel, etc.)
We should not include Benefits, Pay, Schedule.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warnings, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll need to wrap content in appropriate tags:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but maybe we can use other headings? It says "Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, scam warnings, etc. Also remove navigation/cookie etc. Keep substantive info.
We need to parse the posting: It includes company description, role description, responsibilities list, qualifications & skills, education & experience required, preferred, physical & travel requirements, role development, etc.
We need to decide sections: Possibly "About the role" (overview), "Responsibilities", "Qualifications", "Skills", "Education & Experience", "Physical & Travel Requirements", "Role Development". But we must only use allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add custom headings like Education & Experience or Physical & Travel Requirements unless they map to one of allowed headings. The allowed headings are limited. We can put education/experience under "Qualifications" maybe. Skills under "Skills". Responsibilities under "Responsibilities". About the role under "About the role". Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule specifics. So we should not include those sections.
"Requirements" heading could be used for mandatory qualifications? The posting has "Qualifications & Skills" and "Education & Experience Required". We could treat "Requirements" as the mandatory qualifications (education & experience). Then "Qualifications" could be for preferred? But we have both Qualifications and Skills headings allowed. We need to decide mapping.
We have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can use:
- About the role: overview of PRG and role description (first paragraphs).
- Responsibilities: list of key responsibilities (the bullet list).
- Requirements: mandatory qualifications (Education & Experience Required, plus maybe foundational knowledge etc? Actually those are qualifications/skills). But we can put mandatory experience/education here.
- Qualifications: maybe preferred qualifications? Or we could put "Qualifications & Skills" under Qualifications heading, and Skills under Skills heading? But we have both Qualifications and Skills headings; we could split: Qualifications for education/experience, Skills for skills/competencies. However we already used Requirements for education/experience. Might be overlapping.
Better: Use:
- About the role: overview.
- Responsibilities: responsibilities list.
- Qualifications: mandatory qualifications (education & experience, foundational knowledge, etc.)
- Skills: skills list (communication, organizational, CRM, etc.)
- Possibly Requirements: maybe physical & travel requirements? But we have Physical & Travel Requirements section in posting. Could map to Requirements heading (makes sense). However we already used Qualifications for mandatory qualifications. Could use Requirements for physical & travel requirements. But we also have "Requirements" heading allowed; we can use it for physical & travel requirements. Then we need another heading for mandatory qualifications? Could use "Qualifications" for mandatory qualifications, and "Skills" for skills. That seems plausible.
Thus:
About the role: company description + role overview.
Responsibilities: list of responsibilities.
Qualifications: Education & Experience Required + maybe foundational knowledge? Actually foundational knowledge is more of a qualification. We'll include Education & Experience Required and maybe "Foundational knowledge of live events..." as part of qualifications.
Skills: list of skills (communication, organizational, CRM, etc.)
Requirements: Physical & Travel Requirements (ability to lift, travel, etc.)
We should not include Benefits, Pay, Schedule.
We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warnings, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll need to wrap content in appropriate tags: About the role
then
... maybe multiple paragraphs. For lists,
- ...