Jobs · OTHR · Georgia

Customer Experience Specialist

Mohawk Industries · Calhoun, GA · 4 wk ago
OTHRFull-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 if posting has real specific content. We need to parse the job posting. Content: - Intro: "Are you looking for more? At Mohawk Industries, we’re committed to more – more customer solutions, more process improvements, more sustainable manufacturing and more opportunities for our team. As a Fortune 500, global flooring leader with some of the best-known brands in the industry, Mohawk is a great place to start or develop your career with an emphasis on more of what’s important to you. Whether you want to lead more, innovate more, learn more or create more, you can find your more with Mohawk." That's generic fluff; could be considered "About the role"? Actually it's about company. Could be "About the role" or "About the company". The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role? But we have "What We Need" then description of role. That could be "About the role". Then "What You’ll Do" is responsibilities. Then "What You Have" is qualifications/requirements. Then "What You’re Good At" is skills. Then "What else?" includes flexibility, location, etc. Could be "Benefits"? Not exactly benefits but maybe "Work Environment" but not in allowed list. We could treat as "Benefits"? Not really. The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. So we need to decide which sections have substantive content. We have: - About the role: Could be the "What We Need" paragraph describing role. That's substantive. - Responsibilities: "What You’ll Do" list of duties. That's substantive. - Requirements/Qualifications: "What You Have" includes Bachelor's degree, 2-4 years experience, previous customer service experience required. That's qualifications. - Skills: "What You’re Good At" includes knowledge, communication, problem solving, organizational, multitask, integrity, discretion, proficient MS Office. That's skills. - Benefits: Not explicitly mentioned. There's "While we’re a primarily in-office team, we thrive on flexibility and ensure our people can balance personal and professional time". That's a benefit (flexibility). Also location mention. Could be considered benefits but not explicit like health insurance, etc. The instruction: never create Benefits section unless posting actually states them. It does mention flexibility and location, which could be considered a benefit. But is that enough? It's not a typical benefit like health, 401k. However it's still a benefit statement. The rule: "Prefer a few substantive sections over many thin ones." Might be okay to include Benefits with that content. - Pay: Not mentioned. So omit. - Schedule: Not mentioned. Omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. But note: Requirements and Qualifications may overlap. The instruction list includes both Requirements and Qualifications as possible headings. We have content that could be split: "What You Have" includes education and experience (requirements) and also maybe "previous customer service experience required" (qualification). Could treat as Requirements (education/experience) and Qualifications (maybe skills?). But we already have Skills separate. Safer: Use Requirements for education/experience, Qualifications for maybe "previous customer service experience required"? But that's also a requirement. Could combine into one section "Requirements". However we have both headings allowed; we could use Requirements for education/experience and Qualifications for "previous customer service experience required". But that seems thin. Better: Use Requirements for education/experience, and Qualifications for "previous customer service experience required". But that's still thin. Might be better to just have one section "Requirements" containing all: Bachelor's degree, 2-4 years experience, previous customer service experience required. Then Skills separate. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from each section. Let's extract content. About the role: The "What We Need" paragraph: "The Customer Experience Specialist is an established performer that works to facilitate and support the Customer Experience function by coordinating with internal partners. This role is responsible for troubleshooting, resolving, advising, and helping to train on matters presented by external customers to promote customer satisfaction and drive business relations." We should keep that as prose under About the role. Responsibilities: "What You’ll Do" includes multiple sentences, each describing a duty. We need to turn each into list items? The instruction: Use

    • for any list of duties/requirements/benefits. So we should make a list. List items: - Investigate claims submitted by customers to determine root cause, identify possible solutions, and train to ensure matters are handled appropriately and support business by correcting future potential issues. - Communicate and follow up with Sales Agents during after-sales transactions, both internal and external. - Communicate and coordinate actions with necessary functions to resolve replacement or remedial claims caused by manufacturing defects, addressing any disputes, and negotiating any deductions relevant to the claim. - Coordinate customers’ shipping and scheduling requirements with Logistics, Mohawk Fleet, Field Services, and external contractor customers’ shipping requirements for delivery and installation of replacement orders. - Support department goals and initiatives that improve efficiency, simplify processes, and promote teamwork and overall business competitiveness. - May assist with the development and administration of training workshops as it relates to customer experience. - Structure content for internal and external correspondence with customers, vendors, and key stakeholders that include reports, presentations, and metrics. - Research items related to chargebacks, disputed invoices, product discrepancies, and other matters brought to the customer. - May process invoices and customer reports as needed and work with the credit department on accounts receivable. - May be responsible for compiling and reviewing primary and secondary data showing sales volume, inventory levels, and merchandising action plans to ensure effective and profitable maintenance of assigned accounts. - Assist with special projects as needed. - Perform other duties as needed. We need to keep all details exactly as in posting. Ensure punctuation. Requirements: "What You Have": Bachelor’s degree in a related field or equivalent education and/or experience. 2-4 years’ relevant experience or equivalent education and/or experience. Previous customer service experience required. We could make list items: - Bachelor’s degree in a related field or equivalent education and/or experience. - 2-4 years’ relevant experience or equivalent education and/or experience. - Previous customer service experience required. Skills: "What You’re Good At": Demonstrates strong knowledge of technical, process, and business principals, industry practices and standards. Excellent communication, problem solving, and organizational skills. Able to multitask, prioritize, and manage time effectively. High level of integrity and discretion in handling sensitive and confidential data. Proficient using Microsoft Office Suite products. Make list items: - Demonstrates strong knowledge of technical, process, and business principals, industry practices and standards. - Excellent communication, problem solving, and organizational skills. - Able to multitask, prioritize, and manage time effectively. - High level of integrity and discretion in handling sensitive and confidential data. - Proficient using Microsoft Office Suite products. Benefits: "What else?" includes: While we’re a primarily in-office team, we thrive on flexibility and ensure our people can balance personal and professional time. We’re located in a pretty great spot – check out this video to see what we mean. Then company description about Mohawk Industries (maybe not benefit). The instruction: remove boilerplate, duplicated lines, application instructions. The company description may be considered boilerplate? It's describing the company, not a benefit. Might be considered "About the company" but not in allowed headings. Could we include it under About the role? Already we used About the role for role description. Could we add a separate section "About the company"? Not allowed headings list. So we should omit that company description as it's not required heading. However we need to preserve ALL substantive information; but we can omit if not fitting allowed headings? The instruction: "Prefer a few substantive sections over many thin ones." It didn't say we must include all info; but earlier: "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we must keep all substantive info. However we cannot create headings outside the allowed list. But we could embed that info under an existing heading like About the role or Benefits? The company description is not about role but about company. Could we put it under About the role? Might be stretching but maybe acceptable as "About the role" includes company context? The earlier intro also had fluff about Mohawk. That could be considered "About the role" as well. But we already used About the role for role description. Could we combine both? The About the role heading could contain both the role description and company overview. That would preserve info. Thus we can put under About the role: the intro fluff + "What We Need" paragraph + company description. But we need to avoid duplication. Let's see. Intro fluff: "Are you looking for more? At Mohawk Industries, we’re committed to more – more customer solutions, more process improvements, more sustainable manufacturing and more opportunities for our team. As a Fortune 500, global flooring leader with some of the best-known brands in the industry, Mohawk is a great place to start or develop your career with an emphasis on more of what’s important to you. Whether you want to lead more, innovate more, learn more or create more, you can find your more with Mohawk." Then "What We Need" paragraph. Then company description: "Mohawk Industries is a leading global flooring manufacturer that creates products to enhance residential and commercial spaces around the world. Mohawk’s vertically integrated manufacturing and distribution processes provide competitive advantages in the production of carpet, rugs, ceramic tile, laminate, wood, stone and vinyl flooring. Our industry-leading innovation has yielded products and technologies that differentiate our brands in the marketplace and satisfy all remodeling and new construction requirements. Our brands are among the most recognized in the industry and include American Olean, Daltile, Durkan, IVC, Karastan, Marazzi, Mohawk, Mohawk Home, Pergo, and Quick-Step. During the past decade, Mohawk has transformed its business from an American carpet manufacturer into the world’s largest flooring company with operations in Australia, Brazil, Canada, Europe, India, Malaysia, Mexico, New Zealand, Russia and the United States." We could include that as prose under About the role. Then Benefits: flexibility and location statement. Thus we keep all substantive info. Now we must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is: "Mohawk Industries, Inc. is an Equal Opportunity Employer including disability/veteran committed to an inclusive workplace and a proud Drugs Don’t Work participant." That's EEO boilerplate; must remove. Also there may be duplicated lines? Not seeing. Now produce HTML fragment. Structure:

      About the role

      ... (combined intro fluff + What We Need + company description)

      Responsibilities

      • ...
      • ...

      Requirements

      • ...
      • ...

      Skills

      • ...
      • ...

      Benefits

      While we’re a primarily in-office team, we thrive on flexibility and ensure our people can balance personal and

Similar jobs