Customer Service Specialist
Koala® · New York, United States · 3 wk ago
RemoteRemoteOTHRFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines and application instructions. Must preserve all substantive info.
Let's parse the posting.
Content:
- Intro about Koala (company description). Could be "About the role"? Actually "Role Description" section: "To provide exceptional service to Koala’s customers ensuring we continually surprise and delight them with every interaction with us across every platform. Our number one priority (after making amazing products) is the customer experience. We are a brand that deeply cares about our customers and we strive to do anything to deliver happiness and satisfaction. Within our team we provide both exceptional inbound Customer Service and also outbound Customer Engagement roles. We’re looking for full-time remote service specialists located on the East Coast (EST time zone) to join Koala to support the team as the business is growing."
That's description of role. Could be "About the role" heading.
- Key Responsibilities: list bullet points.
- Ideal background: list bullet points (requirements/qualifications/skills). Could be "Requirements" or "Qualifications" or "Skills". We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can pick appropriate ones.
We have responsibilities list. We have ideal background list (experience, skills). Could split into Requirements (experience) and Skills (specific skills). But we can also combine into one "Requirements" section. However we should prefer few substantive sections over many thin ones. So maybe we have: About the role, Responsibilities, Requirements (including ideal background), Benefits (perks and privileges). Also maybe "Why Join Koala?" could be part of Benefits or separate? It's more about culture; could be part of Benefits or maybe "About the role"? But we already have About the role. Could add a section "Why Join Koala?" but not in list of allowed headings; but we could treat as Benefits? The instruction says use those headings; but we can also add other headings if needed? It says "use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines and application instructions. Must preserve all substantive info.
Let's parse the posting.
Content:
- Intro about Koala (company description). Could be "About the role"? Actually "Role Description" section: "To provide exceptional service to Koala’s customers ensuring we continually surprise and delight them with every interaction with us across every platform. Our number one priority (after making amazing products) is the customer experience. We are a brand that deeply cares about our customers and we strive to do anything to deliver happiness and satisfaction. Within our team we provide both exceptional inbound Customer Service and also outbound Customer Engagement roles. We’re looking for full-time remote service specialists located on the East Coast (EST time zone) to join Koala to support the team as the business is growing."
That's description of role. Could be "About the role" heading.
- Key Responsibilities: list bullet points.
- Ideal background: list bullet points (requirements/qualifications/skills). Could be "Requirements" or "Qualifications" or "Skills". We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can pick appropriate ones.
We have responsibilities list. We have ideal background list (experience, skills). Could split into Requirements (experience) and Skills (specific skills). But we can also combine into one "Requirements" section. However we should prefer few substantive sections over many thin ones. So maybe we have: About the role, Responsibilities, Requirements (including ideal background), Benefits (perks and privileges). Also maybe "Why Join Koala?" could be part of Benefits or separate? It's more about culture; could be part of Benefits or maybe "About the role"? But we already have About the role. Could add a section "Why Join Koala?" but not in list of allowed headings; but we could treat as Benefits? The instruction says use those headings; but we can also add other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use others if appropriate, but better to stick to those. "Why Join Koala?" could be considered part of Benefits or maybe "About the role". I'd incorporate that into Benefits or maybe a separate "About the role" includes why join? Might be okay.
We have "Perks and Privileges" section: includes Work From SofaBed, time off, surprise & delight, support & wellbeing, competitive 401k matching, health insurance, learning management, community & connection, BCorp etc. That's benefits.
We have no explicit Pay or Schedule info. So we should not create those sections.
We need to remove boilerplate: equal opportunity employer, etc. Also remove duplicated lines: there is a duplicated line: "We believe that simply doing ‘no harm’ isn’t good enough So, how are we doing our part? We believe that simply doing ‘no harm’ isn’t good enough So, how are we doing our part?" We'll keep only one instance.
Also remove navigation/cookie/legal etc. Not present.
We need to preserve all substantive info: company description, role description, responsibilities, ideal background, perks/privileges, why join koala (maybe incorporate). Also note location: full-time remote service specialists located on the East Coast (EST time zone). That's schedule? It's location/timezone. Could be part of About the role or Requirements. We'll include in About the role.
Now craft HTML.
Structure:
About the role
About the role
Koala is a global furniture brand ... (company description) ... We’re looking for full-time remote service specialists located on the East Coast (EST time zone) to join Koala to support the team as the business is growing.
But we need to avoid repeating job title. Not needed. ThenResponsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...