Manager, Workforce & Organizational Transformation
Jobgether · United States · 3 wk ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Employment eligibility verification through E-Verify."? That's maybe part of benefits? It's a statement but not a benefit; could be considered boilerplate. Probably remove. Also remove "Fully remote position based in the United States." That's schedule? Actually it's location/remote, maybe schedule? It's not pay or schedule. Could be part of Benefits? It's a work arrangement. Could be considered a benefit? Might include under Benefits? But we only include sections if posting has real specific content. The posting includes "Fully remote position based in the United States." That's a detail about schedule/location. Could be placed under Schedule? Not exactly schedule. Could be under Benefits? Might be considered a benefit (remote work). However guidelines: include Pay/Schedule/Benefits sections only if posting actually states them. It states remote work, which is a work arrangement, maybe schedule? Not exactly schedule. Could treat as Benefit (remote work). But we have a Benefits section already with list. We could add remote work as a bullet under Benefits.
We need to preserve all substantive information: responsibilities list, requirements list, qualifications? The posting includes "Requirements" and also "Benefits". There's also "Qualifications" maybe overlapping with Requirements. The posting includes "Requirements" bullet list. Also "Experience with ..." etc. There's also "Skills" maybe implied but not explicit. We could create a Skills section for skills like strong written, verbal, analytical, presentation skills, ability to manage multiple priorities, etc. But those are in Requirements. Might be better to keep Requirements section covering those. Qualifications maybe not separate. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have About the role: the initial paragraph describing role. That's substantive.
Responsibilities: the list under "Accountabilities". That's responsibilities.
Requirements: the list under "Requirements". That's qualifications.
Qualifications: maybe we could split education vs experience? But we can just have Requirements covering both. Qualifications maybe not needed.
Skills: we could extract skills like strong written, verbal, analytical, presentation skills, ability to manage multiple priorities, identify risks, deliver high-quality work, etc. Those are in Requirements. Could put them under Skills.
Benefits: we have list under "Benefits". Also remote work.
Pay: not specified (only "Competitive compensation determined based on experience...") That's vague but it's stating compensation determined based on factors. That's not a specific number or range. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include Pay section because it's not specific.
Schedule: we have remote work but not schedule details like hours. Could treat remote as benefit not schedule. So we may omit Schedule.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3). Possibly Skills (h3) if we want to separate skills from requirements. But we could incorporate skills into Requirements. The instruction: Prefer a few substantive sections over many thin ones. So better to combine.
Thus we will output:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", data privacy notice, etc. Also remove "Employment eligibility verification through E-Verify."? That's maybe part of benefits? It's a statement but not a benefit; could be considered boilerplate. Probably remove. Also remove "Fully remote position based in the United States." That's schedule? Actually it's location/remote, maybe schedule? It's not pay or schedule. Could be part of Benefits? It's a work arrangement. Could be considered a benefit? Might include under Benefits? But we only include sections if posting has real specific content. The posting includes "Fully remote position based in the United States." That's a detail about schedule/location. Could be placed under Schedule? Not exactly schedule. Could be under Benefits? Might be considered a benefit (remote work). However guidelines: include Pay/Schedule/Benefits sections only if posting actually states them. It states remote work, which is a work arrangement, maybe schedule? Not exactly schedule. Could treat as Benefit (remote work). But we have a Benefits section already with list. We could add remote work as a bullet under Benefits.
We need to preserve all substantive information: responsibilities list, requirements list, qualifications? The posting includes "Requirements" and also "Benefits". There's also "Qualifications" maybe overlapping with Requirements. The posting includes "Requirements" bullet list. Also "Experience with ..." etc. There's also "Skills" maybe implied but not explicit. We could create a Skills section for skills like strong written, verbal, analytical, presentation skills, ability to manage multiple priorities, etc. But those are in Requirements. Might be better to keep Requirements section covering those. Qualifications maybe not separate. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have About the role: the initial paragraph describing role. That's substantive.
Responsibilities: the list under "Accountabilities". That's responsibilities.
Requirements: the list under "Requirements". That's qualifications.
Qualifications: maybe we could split education vs experience? But we can just have Requirements covering both. Qualifications maybe not needed.
Skills: we could extract skills like strong written, verbal, analytical, presentation skills, ability to manage multiple priorities, identify risks, deliver high-quality work, etc. Those are in Requirements. Could put them under Skills.
Benefits: we have list under "Benefits". Also remote work.
Pay: not specified (only "Competitive compensation determined based on experience...") That's vague but it's stating compensation determined based on factors. That's not a specific number or range. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include Pay section because it's not specific.
Schedule: we have remote work but not schedule details like hours. Could treat remote as benefit not schedule. So we may omit Schedule.
Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), Benefits (h3). Possibly Skills (h3) if we want to separate skills from requirements. But we could incorporate skills into Requirements. The instruction: Prefer a few substantive sections over many thin ones. So better to combine.
Thus we will output:
About the role
... (the description)
Responsibilities
- ... each accountability item
Requirements
- ... each requirement item
Benefits
- ... each benefit item