Customer Success Manager
QA Ltd · Home, KS · 3 wk ago
OTHRFull-time
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. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting and extract content.
Let's identify sections:
- About The Role: description of role, context, etc.
- What you'll be doing: list of duties.
- A market with genuine momentum: maybe part of role description.
- We'll invest in your development too: development opportunities.
- Who tends to do well here? (list of traits) could be Requirements/Skills/Qualifications.
- The opportunity: maybe part of role.
- About Us: includes Wellbeing & benefits, Personal growth, Our people, Our Mission.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which content goes where.
We have no explicit Pay or Schedule info. So we should NOT include Pay or Schedule sections because posting does not state them. So we omit those.
Benefits: there is a "Wellbeing & benefits" section with list of benefits. So we include Benefits.
Responsibilities: from "What you'll be doing" bullet list.
Requirements/Qualifications/Skills: we have "Who tends to do well here?" list of traits, plus maybe "You should be able to demonstrate how you've managed complex customer needs..." etc. Also "Experience within learning, technology or workforce development would be valuable, but isn't essential." Also "You'll need to balance strong customer relationships with commercial outcomes..." etc. Also earlier "You'll need to balance strong customer relationships with commercial outcomes..." is part of responsibilities? Might be responsibilities.
We need to decide mapping: Requirements: maybe mandatory qualifications? Not many explicit. Qualifications: maybe education? Not given. Skills: list of skills/competencies.
We can combine: Requirements could be "Experience within learning, technology or workforce development would be valuable, but isn't essential." plus maybe "You should be able to demonstrate how you've managed complex customer needs, built credibility with stakeholders and made a measurable difference to customer satisfaction, retention or performance." That's more like required experience.
Qualifications maybe none specific; we could omit if no concrete.
Skills: list of traits: Passionate about delivering meaningful customer outcomes, Confident building relationships with senior stakeholders and decision-makers, Commercially minded, with an understanding of retention, contract performance and customer value, Comfortable managing complex customer relationships and competing priorities, Proactive in anticipating challenges and finding solutions, Curious about how organisations operate and what success looks like for them, Confident using data and customer insights to inform decisions and demonstrate value, Strong at bringing different teams together to achieve shared goals, Organised, accountable and comfortable taking ownership, Motivated by building long-term partnerships rather than simply managing transactions.
Also earlier: "You'll need to balance strong customer relationships with commercial outcomes, identifying risks early, protecting existing business and working alongside our sales teams to uncover opportunities for further growth." That's skill.
Also "You'll Work Across QA's Learning Portfolio, Which Includes Apprenticeships Instructor-led training Self-paced learning Hands-on labs" maybe responsibilities.
We need to preserve all substantive info; we can't invent.
We'll create sections:
About the role
with paragraphs describing role context.Responsibilities
with- list from "What you'll be doing" plus maybe other duty bullets.
Skills
with- list of traits.
Benefits
with- list from Wellbeing & benefits.
We might also include a section for "Development opportunities" maybe under Skills or About the role? But we have no heading for Development; could be part of About the role or Skills. The instruction says prefer few substantive sections over many thin ones. So we could incorporate development opportunities into About the role or Skills. But we have a separate "We'll invest in your development too" paragraph; we could include that in About the role as additional paragraph.
We must not create empty sections.
Thus final HTML:
About the role
... paragraphs ...
Responsibilities
- ... ...
Skills
- ... ...
Benefits
- ... ...
- list from Wellbeing & benefits.
We might also include a section for "Development opportunities" maybe under Skills or About the role? But we have no heading for Development; could be part of About the role or Skills. The instruction says prefer few substantive sections over many thin ones. So we could incorporate development opportunities into About the role or Skills. But we have a separate "We'll invest in your development too" paragraph; we could include that in About the role as additional paragraph.
We must not create empty sections.
Thus final HTML:
- list of traits.