Manager, Customer Success
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
The posting begins with description of Shipfusion, then "The Opportunity: We are looking for a highly motivated Client Service Site Manager to join our Customer Success team! Reporting to the VP of Client Success you will be a key part of managing the success of Shipfusion’s clients in our brand new fulfillment centre. In this role you will…" Then bullet list of responsibilities.
Then "What You’ll Bring to the Team (Required Skills):" list of required skills.
Then "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." etc. Then list of benefits.
Thus we have sections: About the role (maybe a brief description), Responsibilities, Requirements (or Qualifications/Skills), Benefits. Pay? The posting mentions "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a statement about salary but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a statement about salary but not a specific figure. Is that considered stating them? It says "competitive and rewarding salary package." That's vague but still states that there is a salary package. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary, albeit vague. Should we include a Pay section? The instruction: "Prefer a few substantive sections over many thin ones." Also "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "competitive and rewarding salary package" is not filler? It's somewhat generic but still states that there is a salary package. I'd lean to include a Pay section with that statement as prose. However, we could also fold it into About the role or Benefits? Benefits section already includes health, dental, vacation, etc. Pay could be separate.
Schedule: not mentioned. So no Schedule section.
Thus sections: About the role (maybe a short paragraph describing the role and reporting line), Responsibilities (list), Requirements (list), Benefits (list). Possibly also Qualifications/Skills but we can combine Requirements and Skills into one section titled Requirements (or Qualifications). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to use. We need to avoid thin sections. Could combine Requirements and Skills into one heading "Requirements". Or we could have "Requirements" and "Skills" separate but that may be thin. Better to combine.
Thus:
About the role
Shipfusion is looking for a highly motivated Client Service Site Manager to join the Customer Success team, reporting to the VP of Client Success. The role is based in the brand‑new fulfillment centre and involves managing medium‑ to high‑revenue accounts, onboarding, training, support, escalations, project management, and process improvement.
Then Responsibilities as - ... each bullet.
Then Requirements (or Qualifications/Skills) as
- ... each bullet.
Then Benefits as
- ... each bullet.
Pay: we could include a short
under About the role or separate Pay section. Since they mention salary package, we could add a Pay section with that statement. But we need to avoid filler. The statement "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." is somewhat generic but still specific about having a competitive package. I'd include a Pay section with that as prose.
Thus:
Pay
Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package.
But we need to ensure we don't create a section with filler. This is not filler like "commensurate with experience". It's a statement about salary. I'd keep it.
Now we need to remove boilerplate: The initial paragraph about Shipfusion giving brands tools etc. That's about the company, not the role. Should we include that? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? It's about the company, not the role. Might be considered background. Could be included in About the role or maybe omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's about the company. Might be relevant to include as part of About the role? However, the "About the role" heading is for role description, not company. But we could include a short paragraph about the company under About the role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects role description. The company description could be considered part of the role context. I'd include a brief sentence about Shipfusion's mission within About the role.
Thus About the role paragraph: "Shipfusion provides brands with tools for building successful eCommerce operations, founded by eCommerce and logistics professionals who believe retailers should trust their fulfillment partners as much as their in‑house team. The company values entrepreneurship and innovation and is seeking a Client Service Site Manager to join the Customer Success team, reporting to the VP of Client Success, to manage client success in the new fulfillment centre."
That preserves the company description.
Now responsibilities: list each bullet from "In this role you will…" then the bullet list.
Let's extract responsibilities:
- Be responsible for managing the day to day functions of accounts ranging from medium to high revenue on a monthly basis
- Provide Shipfusion onboarding and continued education/training throughout lifecycle
- Provide world class customer support to clients, handling all questions and escalated issues as required
- Work directly with our Support and Warehouse teams to ensure deliverables are being achieved
- Work alongside the Sales team to provide product demonstrations to prospective clients
- Help strategize with customers on how to optimize the Shipfusion portal
- Managing customer projects through our proprietary customer portal
- Be able to succeed in a high pressure, entrepreneurial environment.
- Build strong, trusted relationships with key customers and serve as a senior point of contact for escalations and complex client needs.
- Develop and standardize Customer Success processes, playbooks, reporting, and best practices.
- Monitor customer health and identify risks early, creating clear action plans to address at-risk accounts.
- Lead regular account reviews and ensure the team is effectively communicating performance, opportunities, risks, and recommendations to customers.
- Track and report on key Customer Success metrics and team performance.
- Coach and support Account Managers and Support team members
- Be the advocate for Client Services and our clients within the local operation
- Additional duties as requested by the business as dictated by business needs
We need to preserve all substantive information. The last bullet "Additional duties as requested by the business as dictated by business needs" is generic but still part of posting. It's not filler like "N/A". It's a statement. We'll keep it.
Now requirements: list from "What You’ll Bring to the Team (Required Skills):"
- 5+ years of client services, or project management experience
- 2+ years of experience managing and developing customer-facing teams.
- Proficient with technology including G-Suite and data manipulation via Spreadsheet
- Strong communication and client management skills
- A self starter who can work independently
- Ability to quickly adopt to new technical processes and roll out new technical workflows to clients
- Desire to work in a fast-paced, tech-oriented culture
- Experience managing complex accounts, escalations, and competing priorities.
- Strong leadership and coaching skills with a track record of developing high-performing teams.
We should keep all.
Now benefits: list from "Attractive Salary and Lucrative Compensation Plan:" etc.
- Earn what you deserve with our competitive and rewarding salary package.
- Comprehensive Health and Dental Coverage: Enjoy peace of mind with health and dental benefits for you and your loved ones, starting from day one.
- Generous Vacation Time: Recharge and explore with 15 days of paid vacation and 5 paid wellness days.
- Vibrant Company Social Events: Connect and celebrate with exciting social events that bring our team together.
- Exclusive Employee Discounts: Enjoy special savings with our employee discount program on your favorite products.
- Employee Assistance Program (EAP): Access to comprehensive support services that promote employee well-being and work-life balance.
- Calm App Subscription: Receive 100% coverage for the Calm app, providing you with resources for meditation, sleep improvement, and stress management.
- Positive Company Culture: Join a workplace known for its supportive, inclusive, and dynamic culture.
- High Employee Retention Rates: Be part of a company where employees are valued and tend to stay, reflecting our commitment to employee satisfaction and growth.
Note: The first bullet about salary is duplicated? Actually the heading "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a sentence. Then the list includes "Earn what you deserve with our competitive and rewarding salary package." as a bullet. That seems redundant. We need to preserve all substantive information; we can keep both but maybe combine. However, we should not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The sentence and the bullet are essentially same. We'll keep only one instance. Perhaps keep the bullet under Benefits (or Pay) and drop the heading sentence. Since we have a Pay section, we can put the salary statement there, and not duplicate in Benefits.
Thus Benefits list will exclude the salary bullet.
Now Pay section: we can have a short paragraph: "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package."
Now we need to ensure we don't create thin sections. We have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. Could we combine Pay into Benefits? But the instruction says prefer a few substantive sections over many thin ones. Pay is a single sentence; could be thin. However, we could incorporate it into Benefits as a bullet, but we removed duplicate. We could add it as a bullet under Benefits: "Competitive and rewarding salary package". That would avoid a thin Pay section. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary, but we can include it under Benefits as a bullet. That would reduce sections. Let's do that: Benefits section includes salary bullet plus other benefits.
Thus we will have sections: About the role, Responsibilities, Requirements, Benefits.
Now we
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. The posting begins with description of Shipfusion, then "The Opportunity: We are looking for a highly motivated Client Service Site Manager to join our Customer Success team! Reporting to the VP of Client Success you will be a key part of managing the success of Shipfusion’s clients in our brand new fulfillment centre. In this role you will…" Then bullet list of responsibilities. Then "What You’ll Bring to the Team (Required Skills):" list of required skills. Then "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." etc. Then list of benefits. Thus we have sections: About the role (maybe a brief description), Responsibilities, Requirements (or Qualifications/Skills), Benefits. Pay? The posting mentions "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a statement about salary but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a statement about salary but not a specific figure. Is that considered stating them? It says "competitive and rewarding salary package." That's vague but still states that there is a salary package. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about salary, albeit vague. Should we include a Pay section? The instruction: "Prefer a few substantive sections over many thin ones." Also "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "competitive and rewarding salary package" is not filler? It's somewhat generic but still states that there is a salary package. I'd lean to include a Pay section with that statement as prose. However, we could also fold it into About the role or Benefits? Benefits section already includes health, dental, vacation, etc. Pay could be separate. Schedule: not mentioned. So no Schedule section. Thus sections: About the role (maybe a short paragraph describing the role and reporting line), Responsibilities (list), Requirements (list), Benefits (list). Possibly also Qualifications/Skills but we can combine Requirements and Skills into one section titled Requirements (or Qualifications). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to use. We need to avoid thin sections. Could combine Requirements and Skills into one heading "Requirements". Or we could have "Requirements" and "Skills" separate but that may be thin. Better to combine. Thus:
About the role
Shipfusion is looking for a highly motivated Client Service Site Manager to join the Customer Success team, reporting to the VP of Client Success. The role is based in the brand‑new fulfillment centre and involves managing medium‑ to high‑revenue accounts, onboarding, training, support, escalations, project management, and process improvement.
Then Responsibilities as- ... each bullet.
Then Requirements (or Qualifications/Skills) as
- ... each bullet.
Then Benefits as
- ... each bullet.
Pay: we could include a short
under About the role or separate Pay section. Since they mention salary package, we could add a Pay section with that statement. But we need to avoid filler. The statement "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." is somewhat generic but still specific about having a competitive package. I'd include a Pay section with that as prose. Thus:
Pay
Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package.
But we need to ensure we don't create a section with filler. This is not filler like "commensurate with experience". It's a statement about salary. I'd keep it. Now we need to remove boilerplate: The initial paragraph about Shipfusion giving brands tools etc. That's about the company, not the role. Should we include that? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? It's about the company, not the role. Might be considered background. Could be included in About the role or maybe omitted? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not boilerplate; it's about the company. Might be relevant to include as part of About the role? However, the "About the role" heading is for role description, not company. But we could include a short paragraph about the company under About the role? The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects role description. The company description could be considered part of the role context. I'd include a brief sentence about Shipfusion's mission within About the role. Thus About the role paragraph: "Shipfusion provides brands with tools for building successful eCommerce operations, founded by eCommerce and logistics professionals who believe retailers should trust their fulfillment partners as much as their in‑house team. The company values entrepreneurship and innovation and is seeking a Client Service Site Manager to join the Customer Success team, reporting to the VP of Client Success, to manage client success in the new fulfillment centre." That preserves the company description. Now responsibilities: list each bullet from "In this role you will…" then the bullet list. Let's extract responsibilities: - Be responsible for managing the day to day functions of accounts ranging from medium to high revenue on a monthly basis - Provide Shipfusion onboarding and continued education/training throughout lifecycle - Provide world class customer support to clients, handling all questions and escalated issues as required - Work directly with our Support and Warehouse teams to ensure deliverables are being achieved - Work alongside the Sales team to provide product demonstrations to prospective clients - Help strategize with customers on how to optimize the Shipfusion portal - Managing customer projects through our proprietary customer portal - Be able to succeed in a high pressure, entrepreneurial environment. - Build strong, trusted relationships with key customers and serve as a senior point of contact for escalations and complex client needs. - Develop and standardize Customer Success processes, playbooks, reporting, and best practices. - Monitor customer health and identify risks early, creating clear action plans to address at-risk accounts. - Lead regular account reviews and ensure the team is effectively communicating performance, opportunities, risks, and recommendations to customers. - Track and report on key Customer Success metrics and team performance. - Coach and support Account Managers and Support team members - Be the advocate for Client Services and our clients within the local operation - Additional duties as requested by the business as dictated by business needs We need to preserve all substantive information. The last bullet "Additional duties as requested by the business as dictated by business needs" is generic but still part of posting. It's not filler like "N/A". It's a statement. We'll keep it. Now requirements: list from "What You’ll Bring to the Team (Required Skills):" - 5+ years of client services, or project management experience - 2+ years of experience managing and developing customer-facing teams. - Proficient with technology including G-Suite and data manipulation via Spreadsheet - Strong communication and client management skills - A self starter who can work independently - Ability to quickly adopt to new technical processes and roll out new technical workflows to clients - Desire to work in a fast-paced, tech-oriented culture - Experience managing complex accounts, escalations, and competing priorities. - Strong leadership and coaching skills with a track record of developing high-performing teams. We should keep all. Now benefits: list from "Attractive Salary and Lucrative Compensation Plan:" etc. - Earn what you deserve with our competitive and rewarding salary package. - Comprehensive Health and Dental Coverage: Enjoy peace of mind with health and dental benefits for you and your loved ones, starting from day one. - Generous Vacation Time: Recharge and explore with 15 days of paid vacation and 5 paid wellness days. - Vibrant Company Social Events: Connect and celebrate with exciting social events that bring our team together. - Exclusive Employee Discounts: Enjoy special savings with our employee discount program on your favorite products. - Employee Assistance Program (EAP): Access to comprehensive support services that promote employee well-being and work-life balance. - Calm App Subscription: Receive 100% coverage for the Calm app, providing you with resources for meditation, sleep improvement, and stress management. - Positive Company Culture: Join a workplace known for its supportive, inclusive, and dynamic culture. - High Employee Retention Rates: Be part of a company where employees are valued and tend to stay, reflecting our commitment to employee satisfaction and growth. Note: The first bullet about salary is duplicated? Actually the heading "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." That's a sentence. Then the list includes "Earn what you deserve with our competitive and rewarding salary package." as a bullet. That seems redundant. We need to preserve all substantive information; we can keep both but maybe combine. However, we should not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The sentence and the bullet are essentially same. We'll keep only one instance. Perhaps keep the bullet under Benefits (or Pay) and drop the heading sentence. Since we have a Pay section, we can put the salary statement there, and not duplicate in Benefits. Thus Benefits list will exclude the salary bullet. Now Pay section: we can have a short paragraph: "Attractive Salary and Lucrative Compensation Plan: Earn what you deserve with our competitive and rewarding salary package." Now we need to ensure we don't create thin sections. We have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections. Could we combine Pay into Benefits? But the instruction says prefer a few substantive sections over many thin ones. Pay is a single sentence; could be thin. However, we could incorporate it into Benefits as a bullet, but we removed duplicate. We could add it as a bullet under Benefits: "Competitive and rewarding salary package". That would avoid a thin Pay section. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary, but we can include it under Benefits as a bullet. That would reduce sections. Let's do that: Benefits section includes salary bullet plus other benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits. Now we
- ... each bullet.
Pay: we could include a short
- ... each bullet.
Then Benefits as