Senior Solution Consultant
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real, specific content. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove "Click here to view a summary overview of our Benefits." etc. Also remove "What Happens After You Apply", "Stay Connected", "Employee Referral", "About Genesys", "Reasonable Accommodations", "Genesys is an equal opportunity employer..." etc. Also remove "Compensation: This role has a market-competitive salary..." but we need to keep Pay section if actual numbers given. The posting includes: "Compensation: This role has a market-competitive salary with an anticipated base compensation range listed below. Actual salaries will vary depending on a candidate’s experience, qualifications, skills, and location. This role might also be eligible for a commission or performance-based bonus opportunities. $99,600.00 - $175,200.00". So we have Pay info: range. So we should include a Pay section with that range. Also Benefits: they list benefits: Medical, Dental, and Vision Insurance. Telehealth coverage Flexible work schedules and work from home opportunities Development and career growth opportunities Open Time Off in addition to 10 paid holidays 401(k) matching program Adoption Assistance Fertility treatments. Also they say "Click here to view a summary overview of our Benefits." but we can ignore that link. So we have Benefits content.
Schedule: Not explicitly mentioned. There's "Flexible work schedules and work from home opportunities" under Benefits. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section unless posting actually states them. It does not give explicit schedule, so omit.
Qualifications vs Requirements vs Skills: The posting includes "What do you need to have to be successful?" which lists: A passion for technology and helping people solve problems; Interpersonal communication, polished verbal and written communication; Ability to work in a fast-paced, cross-functional team environment and able to multitask, prioritize and be detail-oriented; Have the technological know-how of IT-concepts, software-standards as well as database and networking technologies. Ability to understand customers security needs and articulate a solution; Bachelor’s degree and 5+ years of work experience, preferred experience implementing or integrating with CRMs and/or software implementation or coding experience; Ability to travel up to 50%; Experience working with Cloud or SaaS company preferred.
We can treat these as Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. There's an "About the role" paragraph at start: "Be the one building AI-powered experiences where they matter most...". That's descriptive. Could be About the role. Also there is "What will you be doing?" with subparts Discover, Design, Learn. That's Responsibilities. So we can have About the role (intro paragraph), Responsibilities (the three bullet points), Requirements/Qualifications/Skills (maybe combine). Since they ask to prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But they gave separate headings possible. We could have Requirements (or Qualifications) covering the needed skills/experience. Could also have Skills separate if we want. But better to have one section for Requirements/Qualifications that includes both hard and soft skills. Let's decide: Use "Requirements" heading for the list of needed qualifications/experience/skills. Could also include "Skills" but might be redundant. Since they said prefer few substantive sections, we can have About the role, Responsibilities, Requirements, Benefits, Pay. That's five sections.
Now we need to extract content precisely, preserving all substantive information, not inventing or summarizing away detail. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat the job title as a heading. The job title is Solutions Consultant (implied). Not to repeat.
We must not put Job ID/requisition numbers as headings.
We must remove boilerplate: like "Click here to view a summary overview of our Benefits." (that's a link, but it's navigation/instruction). Also remove "Learn more about our culture..." etc. Also remove "What Happens After You Apply", "Stay Connected", "Employee Referral", "About Genesys", "Reasonable Accommodations", EEO statement, etc.
We must keep the description about Genesys at start? That is part of About the role? The first paragraph: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day." That's about the company and role. Could be About the role.
Then "Do you have a passion for solving problems and understanding what customers need? Are you interested in working in an evolving technical space where you bring in new ideas to help your customers transform and innovate their business? As a Solutions Consultant, you will listen to customers to understand their needs and create compelling business solution roadmaps. We look for individuals who have a proven track record of finding creative ways of solving complex problems." That's also about role and expectations. Could be part of About the role.
Then "Why work for Genesys?" bullet list: "You will showcase your technical expertise and creative talents by developing and presenting dynamic demonstrations to the executives, stakeholders and key influencers. You will have a unique opportunity to understand our customers' strategies and help them drive their business using our unique solutions. You will have flexibility and independence in designing your work. You will be able to access on-demand and in-person training. You will have the internal resources you can call on to help you understand and solve technical challenges. You will have the ability to work closely with other brilliant individuals to collaboratively solve complex technical problems." That's also about role/benefits? Might be considered part of About the role or maybe Responsibilities? But it's more about what you'll get. Could be considered part of Benefits? But they already have Benefits section later. However these are more about role aspects: flexibility, training, resources, collaboration. Could be considered part of About the role or maybe Responsibilities? But we already have Responsibilities from "What will you be doing?" with Discover, Design, Learn. The "Why work for Genesys?" list is more about perks/experience. Could be considered part of Benefits? But Benefits already have medical etc. Might be better to treat "Why work for Genesys?" as part of About the role or maybe a separate section like "What you'll get"? But not in allowed headings. We could incorporate into About the role prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include the content from "Why work for Genesys?" somewhere. If we put it in About the role, we need to include those sentences. That's okay.
Now "What will you be doing?" with Discover, Design, Learn each with description. That's responsibilities. We'll make a Responsibilities section with subheadings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we should follow spec: only those headings. Could we include inner headings like ? Not specified; better to avoid extra headings. We can just list responsibilities as prose or list items. The Discover, Design, Learn are headings inside the posting; we could treat them as subheadings but not required. To preserve detail, we could keep them as or just as sentences. But we can also turn them into - with the heading as part of li text. Eg:
- Discover: You will run workshops...
. That preserves detail.
Now "What do you need to have to be successful?" list. We'll put that in Requirements section as - .
Now Benefits: list as
- .
Now Pay: we have the range. Could be a
with the range.
Now we must not include any filler like "commensurate with experience", "not specified", etc. We have actual range, so fine.
Now we need to ensure we don't include any boilerplate like "Click here to view a summary overview of our Benefits." We'll omit that sentence.
Also remove "Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." That's boilerplate.
Also remove "Working at Genesys AI at enterprise scale – Build, support and operate AI-powered technology used by more than 8,000 organizations worldwide. 150+ new AI features were released in the last fiscal year A flexible-first culture – Join a global team of nearly 7,000 employees with flexible ways of working designed to help people do their best work Growth in the AI era – Build future-ready skills through mentorship, learning programs, leadership development and education support Time to recharge and give back – Benefits include paid volunteer time, August Free Fridays, well-being resources and regionally tailored programs for employees and their families Recognized globally – Genesys is Great Place to Work® certified in 17 countries and 94% of employees are proud to tell others they work at Genesys". This is also boilerplate/culture description; we should remove as it's not specific to the role? It's about Genesys but could be considered part of About the role? However it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This culture blurb might be considered boilerplate but it's not explicitly listed. However it's generic promotional content not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is this substantive? It's about Genesys culture, not specific to the role. Might be considered boilerplate. Safer to remove it.
Also remove "Employee Referral If a Genesys employee referred you, please apply using the link they shared so we can connect your application to their referral." That's application instruction, remove.
Also remove "About Genesys: Genesys® empowers more than 8,000 organizations worldwide..." that's boilerplate.
Also remove "Reasonable Accommodations:" etc.
Also remove EEO statement.
Also remove "Click here to view a summary overview of our Benefits." (already).
Also remove "Get notified about relevant opportunities." etc.
Also remove "Stay Connected" etc.
Also remove "What Happens After You Apply" etc.
Also remove "Be the one building what's next - where AI, experience and impact come together." That's tagline, maybe part of About the role? Could be considered marketing fluff. Might be okay to keep as part of About the role? It's not specific to role but it's a tagline. I'd lean to remove as it's generic.
Now we need to ensure we don't duplicate content. The initial paragraph about Genesys appears again later in "Working at Genesys AI at enterprise scale". We'll keep only first occurrence.
Now craft HTML.
Structure:
About the role
Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve
for prose. We must not repeat the job title as a heading. The job title is Solutions Consultant (implied). Not to repeat. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: like "Click here to view a summary overview of our Benefits." (that's a link, but it's navigation/instruction). Also remove "Learn more about our culture..." etc. Also remove "What Happens After You Apply", "Stay Connected", "Employee Referral", "About Genesys", "Reasonable Accommodations", EEO statement, etc. We must keep the description about Genesys at start? That is part of About the role? The first paragraph: "Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve operational efficiency and build stronger customer relationships. Help build, support and operate technology used by more than 8,000 organizations in over 100 countries – moving AI from possibility to production in real-world enterprise environments every day." That's about the company and role. Could be About the role. Then "Do you have a passion for solving problems and understanding what customers need? Are you interested in working in an evolving technical space where you bring in new ideas to help your customers transform and innovate their business? As a Solutions Consultant, you will listen to customers to understand their needs and create compelling business solution roadmaps. We look for individuals who have a proven track record of finding creative ways of solving complex problems." That's also about role and expectations. Could be part of About the role. Then "Why work for Genesys?" bullet list: "You will showcase your technical expertise and creative talents by developing and presenting dynamic demonstrations to the executives, stakeholders and key influencers. You will have a unique opportunity to understand our customers' strategies and help them drive their business using our unique solutions. You will have flexibility and independence in designing your work. You will be able to access on-demand and in-person training. You will have the internal resources you can call on to help you understand and solve technical challenges. You will have the ability to work closely with other brilliant individuals to collaboratively solve complex technical problems." That's also about role/benefits? Might be considered part of About the role or maybe Responsibilities? But it's more about what you'll get. Could be considered part of Benefits? But they already have Benefits section later. However these are more about role aspects: flexibility, training, resources, collaboration. Could be considered part of About the role or maybe Responsibilities? But we already have Responsibilities from "What will you be doing?" with Discover, Design, Learn. The "Why work for Genesys?" list is more about perks/experience. Could be considered part of Benefits? But Benefits already have medical etc. Might be better to treat "Why work for Genesys?" as part of About the role or maybe a separate section like "What you'll get"? But not in allowed headings. We could incorporate into About the role prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include the content from "Why work for Genesys?" somewhere. If we put it in About the role, we need to include those sentences. That's okay. Now "What will you be doing?" with Discover, Design, Learn each with description. That's responsibilities. We'll make a Responsibilities section with subheadings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we should follow spec: only those headings. Could we include inner headings like ? Not specified; better to avoid extra headings. We can just list responsibilities as prose or list items. The Discover, Design, Learn are headings inside the posting; we could treat them as subheadings but not required. To preserve detail, we could keep them as or just as sentences. But we can also turn them into - with the heading as part of li text. Eg:
- Discover: You will run workshops...
. That preserves detail.
Now "What do you need to have to be successful?" list. We'll put that in Requirements section as - .
Now Benefits: list as
- .
Now Pay: we have the range. Could be a
with the range.
Now we must not include any filler like "commensurate with experience", "not specified", etc. We have actual range, so fine.
Now we need to ensure we don't include any boilerplate like "Click here to view a summary overview of our Benefits." We'll omit that sentence.
Also remove "Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." That's boilerplate.
Also remove "Working at Genesys AI at enterprise scale – Build, support and operate AI-powered technology used by more than 8,000 organizations worldwide. 150+ new AI features were released in the last fiscal year A flexible-first culture – Join a global team of nearly 7,000 employees with flexible ways of working designed to help people do their best work Growth in the AI era – Build future-ready skills through mentorship, learning programs, leadership development and education support Time to recharge and give back – Benefits include paid volunteer time, August Free Fridays, well-being resources and regionally tailored programs for employees and their families Recognized globally – Genesys is Great Place to Work® certified in 17 countries and 94% of employees are proud to tell others they work at Genesys". This is also boilerplate/culture description; we should remove as it's not specific to the role? It's about Genesys but could be considered part of About the role? However it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This culture blurb might be considered boilerplate but it's not explicitly listed. However it's generic promotional content not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is this substantive? It's about Genesys culture, not specific to the role. Might be considered boilerplate. Safer to remove it.
Also remove "Employee Referral If a Genesys employee referred you, please apply using the link they shared so we can connect your application to their referral." That's application instruction, remove.
Also remove "About Genesys: Genesys® empowers more than 8,000 organizations worldwide..." that's boilerplate.
Also remove "Reasonable Accommodations:" etc.
Also remove EEO statement.
Also remove "Click here to view a summary overview of our Benefits." (already).
Also remove "Get notified about relevant opportunities." etc.
Also remove "Stay Connected" etc.
Also remove "What Happens After You Apply" etc.
Also remove "Be the one building what's next - where AI, experience and impact come together." That's tagline, maybe part of About the role? Could be considered marketing fluff. Might be okay to keep as part of About the role? It's not specific to role but it's a tagline. I'd lean to remove as it's generic.
Now we need to ensure we don't duplicate content. The initial paragraph about Genesys appears again later in "Working at Genesys AI at enterprise scale". We'll keep only first occurrence.
Now craft HTML.
Structure:
About the role
Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve
- with the heading as part of li text. Eg:
- Discover: You will run workshops... . That preserves detail. Now "What do you need to have to be successful?" list. We'll put that in Requirements section as
- .
Now Benefits: list as
- .
Now Pay: we have the range. Could be a
with the range. Now we must not include any filler like "commensurate with experience", "not specified", etc. We have actual range, so fine. Now we need to ensure we don't include any boilerplate like "Click here to view a summary overview of our Benefits." We'll omit that sentence. Also remove "Learn more about our culture, AI innovation and sustainability commitments through our Careers site and Sustainability Report." That's boilerplate. Also remove "Working at Genesys AI at enterprise scale – Build, support and operate AI-powered technology used by more than 8,000 organizations worldwide. 150+ new AI features were released in the last fiscal year A flexible-first culture – Join a global team of nearly 7,000 employees with flexible ways of working designed to help people do their best work Growth in the AI era – Build future-ready skills through mentorship, learning programs, leadership development and education support Time to recharge and give back – Benefits include paid volunteer time, August Free Fridays, well-being resources and regionally tailored programs for employees and their families Recognized globally – Genesys is Great Place to Work® certified in 17 countries and 94% of employees are proud to tell others they work at Genesys". This is also boilerplate/culture description; we should remove as it's not specific to the role? It's about Genesys but could be considered part of About the role? However it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This culture blurb might be considered boilerplate but it's not explicitly listed. However it's generic promotional content not specific to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is this substantive? It's about Genesys culture, not specific to the role. Might be considered boilerplate. Safer to remove it. Also remove "Employee Referral If a Genesys employee referred you, please apply using the link they shared so we can connect your application to their referral." That's application instruction, remove. Also remove "About Genesys: Genesys® empowers more than 8,000 organizations worldwide..." that's boilerplate. Also remove "Reasonable Accommodations:" etc. Also remove EEO statement. Also remove "Click here to view a summary overview of our Benefits." (already). Also remove "Get notified about relevant opportunities." etc. Also remove "Stay Connected" etc. Also remove "What Happens After You Apply" etc. Also remove "Be the one building what's next - where AI, experience and impact come together." That's tagline, maybe part of About the role? Could be considered marketing fluff. Might be okay to keep as part of About the role? It's not specific to role but it's a tagline. I'd lean to remove as it's generic. Now we need to ensure we don't duplicate content. The initial paragraph about Genesys appears again later in "Working at Genesys AI at enterprise scale". We'll keep only first occurrence. Now craft HTML. Structure:
About the role
Be the one building AI-powered experiences where they matter most. At Genesys, we help organizations create better customer experiences through AI-powered experience orchestration. Our platform connects people, systems, data and AI to help organizations deliver more personalized service, improve
- .
Now Pay: we have the range. Could be a