Customer Support Continuous Improvement Specialist

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info. We need to parse the job posting. Key sections: - Intro: "Are you obsessed with data, partner success, taking action, and changing the game? If you have a whole lot of hustle and a touch of nerd, come work with Pattern! We want you to use your skills to push one of the fastest-growing companies headquartered in the US to the top of the list. Pattern accelerates brands on global ecommerce marketplaces leveraging proprietary technology and AI. Utilizing more than 66 trillion data points, sophisticated machine learning and AI models, Pattern optimizes and automates all levers of ecommerce growth for global brands, including advertising, content management, logistics and fulfillment, pricing, forecasting and customer service. Hundreds of global brands depend on Pattern’s ecommerce acceleration platform every day to drive profitable revenue growth across 60+ global marketplaces—including Amazon, Walmart.com , Target.com , eBay, Tmall, TikTok Shop, JD, and Mercado Libre. To learn more, visit pattern.com or email [email protected] . Pattern has been named one of the fastest growing tech companies headquartered in North America by Deloitte and one of best-led companies by Inc. We place employee experience at the center of our business model and have been recognized as one of Newsweek’s Global Most Loved Workplaces®." That's about the company, could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company overview under About the role. Then: "We need a Customer Support Continuous Improvement Specialist to help drive operational excellence across Pattern's Customer Support organization. We are looking for someone who spots inefficiencies, champions process improvements, and helps cultivate a culture of continuous, customer-obsessed problem-solving. Sitting at the intersection of frontline CS operations, automation initiatives, and cross-functional stakeholders, this role contributes to measurable gains in customer satisfaction, team efficiency, and business performance. This is a full-time role and will work a hybrid schedule (three days in office, two days remote per week) based in Lehi, Utah." That's role description. Then "What is a day in the life of a Customer Support Specialist?" followed by bullet list of duties. That's responsibilities. Then "What will I need to thrive in this role?" bullet list of requirements (education, experience, skills). Then "Preferred Qualifications" bullet list. Then "What does high performance look like?" bullet list of behaviors (maybe skills or expectations). Could be part of Requirements or Skills. Then "What is my potential for career growth?" paragraph. Then "What does success look like in the first 30, 60, 90 days?" bullet list. Then "What is the team like?" paragraph. Then "Sounds great! What's the company culture?" bullet list of values. Then "What is the hiring process?" list. Then "How can I stand out as an applicant?" bullet list. Then "Why should I work at Pattern? Benefits" list of benefits. Then "Pattern provides equal employment opportunities..." that's EEO boilerplate, must remove. Then "We may use artificial intelligence (AI) tools..." that's also boilerplate about hiring process, maybe part of hiring process but it's generic; we can keep hiring process details but remove generic AI statement? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI statement is about hiring process but it's generic; might be considered boilerplate. Safer to remove it. We need to preserve all substantive information; do not invent or summarize away detail. We must not create sections with filler like "commensurate with experience". Not present. We need to decide which sections to include. We have content for: - About the role (company overview + role description) - Responsibilities (day in the life duties) - Requirements (education, experience, basic skills) - Qualifications (Preferred Qualifications) - Skills (maybe combine high performance behaviors, or we could put under Skills) - Benefits (list) - Schedule (hybrid schedule mentioned) - Pay? Not mentioned specifically; only "Competitive Pay" in benefits list but no specifics. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay: we have "Competitive Pay" mentioned under benefits but not a specific number or range. Is that enough to create a Pay section? It says "Competitive Pay" as a benefit item. That is a statement about pay but not specific. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "states them" meaning actual content like salary range, schedule details, benefits details. "Competitive Pay" is vague but still states that pay is competitive. Might be considered stating pay? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they mention "Competitive Pay" as a benefit, we could include Pay section with that statement? But they also said "Prefer a few substantive sections over many thin ones." Might be better to include Pay under Benefits? But they want separate sections for Benefits, Pay, Schedule. However we have schedule info (hybrid schedule). So we can create Schedule section with that detail. Benefits we have list. Pay we have only "Competitive Pay" which is vague; maybe we can omit Pay section because it's not substantive detail. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive Pay". That is a statement about pay. So we could include Pay section with that line. But it's not a detailed description; still it's stated. I'd include it. Now we need to format. We must not repeat job title as heading. So no heading for "Customer Support Continuous Improvement Specialist". Use headings as per list. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

... company overview and role description ...

Responsibilities

• ...
...

Requirements

• ...
...

Preferred Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

Competitive Pay

Schedule

Hybrid schedule: three days in office, two days remote per week (based in Lehi, Utah).

We need to ensure we preserve all substantive info. Let's extract each piece. Company overview paragraph: "Are you obsessed with data, partner success, taking action, and changing the game? If you have a whole lot of hustle and a touch of nerd, come work with Pattern! We want you to use your skills to push one of the fastest-growing companies headquartered in the US to the top of the list. Pattern accelerates brands on global ecommerce marketplaces leveraging proprietary technology and AI. Utilizing more than 66 trillion data points, sophisticated machine learning and AI models, Pattern optimizes and automates all levers of ecommerce growth for global brands, including advertising, content management, logistics and fulfillment, pricing, forecasting and customer service. Hundreds of global brands depend on Pattern’s ecommerce acceleration platform every day to drive profitable revenue growth across 60+ global marketplaces—including Amazon, Walmart.com , Target.com , eBay, Tmall, TikTok Shop, JD, and Mercado Libre. To learn more, visit pattern.com or email [email protected] . Pattern has been named one of the fastest growing tech companies headquartered in North America by Deloitte and one of best-led companies by Inc. We place employee experience at the center of our business model and have been recognized as one of Newsweek’s Global Most Loved Workplaces®." That's a lot; we keep it. Role description: "We need a Customer Support Continuous Improvement Specialist to help drive operational excellence across Pattern's Customer Support organization. We are looking for someone who spots inefficiencies, champions process improvements, and helps cultivate a culture of continuous, customer-obsessed problem-solving. Sitting at the intersection of frontline CS operations, automation initiatives, and cross-functional stakeholders, this role contributes to measurable gains in customer satisfaction, team efficiency, and business performance. This is a full-time role and will work a hybrid schedule (three days in office, two days remote per week) based in Lehi, Utah." We could combine schedule line here but we also have separate Schedule section. Might duplicate. Better to keep schedule in Schedule section and not duplicate. So we can omit schedule from role description paragraph, but we must preserve all substantive info; if we remove schedule from there, we still have it in Schedule section. That's okay as long as we keep the info somewhere. The role description still mentions full-time role; we can keep that. Thus About the role paragraph will include company overview + role description minus schedule line. Now Responsibilities: list from "What is a day in the life of a Customer Support Specialist?" bullet points: - Respond to and resolve customer escalations and brand partner support tickets in Zendesk, following SOPs and macros to deliver consistent, on-brand communication - Keep SOPs and macros current; address gaps, provide edits, and update documentation as processes change - Manage the Quality Audit process by keeping the scorecard up-to-date, creating and reviewing audit assignments with Seniors, Team Leads, and Account Leads, providing agents with constructive feedback, and leading calibration sessions with CS leadership - Own the brand onboarding process: prepare for and lead onboarding calls, upload brand resources, follow up on open questions, and set up reporting needs - Help build and deliver training content (written, video, live) for new hires and existing teammates when new tools or processes roll out - Manage manual and automated reporting, including brand follow-ups, and help catch and resolve negative trends before they become bigger issues - Partner with Account Leads, Team Leads, and Seniors in Focus Groups to identify recurring pain points in tickets and processes and recommend and implement improvements Now Requirements: from "What will I need to thrive in this role?" bullet list: - Bachelor’s degree in Business, Communications, or a related field; equivalent experience considered - 1-2 years of experience in customer support, customer success, or a related client-facing role - Comfortable working in ticketing/helpdesk tools and basic Excel/Google Sheets for reporting and data tracking - Strong written communication skills and the judgment to keep tone consistent across customer interactions - Detail-oriented, with the discipline to follow documented processes and the curiosity to help improve them - A team player who takes feedback well and holds themselves accountable to teammates and partners Now Preferred Qualifications: bullet list: - Working history with Zendesk, Asana, or similar CS/ticketing platforms - Familiarity with marketplace platforms (Amazon, Walmart, Target, etc.) and Shopify - Exposure to quality assurance or audit processes - Comfortable using AI tools to support day-to-day customer service workflows Now Skills: maybe from "What does high performance look like?" bullet list: - You follow SOPs precisely, and when something doesn’t work, you flag it instead of quietly working around it - You give every customer and brand a timely, clear, and empathetic response - You take full ownership of your tickets and tasks and follow through to resolution - You seek out feedback, act on it quickly, and hold a high bar for your own work -