Sr Enterprise HCM Consultant - Detroit
Paychex · Detroit, MI · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes overview (maybe "About the role" content). It has responsibilities section. It has qualifications (including H.S. Diploma, Bachelor's, etc). It has skills (list of preferences). It has benefits (the "What's in it for you?" section). It does not have explicit Pay or Schedule details. So we should not include Pay or Schedule sections. Also we should not repeat job title. No Job ID. Remove boilerplate like EEO etc. Also remove "Note: The benefits described apply to full-time employees..." maybe keep? It's part of benefits description; it's substantive? It says benefits for part-time may vary. Might keep as part of benefits paragraph. Also remove "Paychex is an equal opportunity employer..." etc. Also remove "Live the Paychex Values" maybe that's values but not a section heading; could be part of overview? It's a list of values; could be included under "About the role" maybe. But we need to preserve all substantive information; we can include it as a paragraph under overview.
We need to use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (overview), Responsibilities, Requirements (maybe qualifications?), Qualifications (maybe separate?), Skills, Benefits. The posting has "Qualifications" list and also "Why This Role Unlimited earning potential..." which is more like benefits? Actually that is more like "Why this role" maybe could be part of overview. But we can treat as part of overview.
We have "What It Takes To Win" which is like requirements. Then "Qualifications" list. Then "Live the Paychex Values". Then "What's in it for you?" benefits.
Thus sections: About the role (overview + maybe why this role), Responsibilities, Requirements (What It Takes To Win), Qualifications (H.S. Diploma etc), Skills (list of preferences), Benefits (What's in it for you?). Ensure we don't create empty sections.
We must not include headings with filler like "commensurate with experience". Not present.
Now extract content.
Overview: The first paragraph(s) up to "Overview Where Complexity Meets Structure and Top Performers Win". Actually the heading "Overview Where Complexity Meets Structure and Top Performers Win" seems like a heading but we should not repeat job title; we can treat that as part of About the role heading. We'll put
About the role
then paragraphs.
Let's capture overview text: "Paychex is reimagining how businesses manage their workforce by bringing payroll, HR, benefits, and advisory services together into a single connected HCM platform. As Paychex and Paycor come together, we're combining innovative technology, data-driven insights, AI, and human expertise to help organizations work smarter, support their people, and achieve better business outcomes. This is an exciting time to join our team as we continue to invest in innovation, simplify client experiences, and shape the future of work. At Paychex, you'll have the opportunity to grow your career, make a meaningful impact, and be part of something bigger as One Paychex."
Then maybe also include the paragraph after overview: "Where Complexity Meets Structure and Top Performers Win There is a reason enterprise buyers are moving to Paycor. We built something no one else in the market can replicate: AI-enabled enterprise technology backed by the deepest operational expertise in the HCM industry. Our platform is purpose-built for how enterprise HR and finance actually work. When you sell for Paycor, you are not asking buyers to take a leap of faith. You are bringing them the answer the market has been waiting for. Enterprise Sales at Paycor is built for experienced sellers who want to operate at a higher level. You’ll partner with organizations of 100+ employees, helping them solve complex workforce challenges through a modern, end-to-end HCM platform and service experience. This is a true new-logo, advisory services role, focused on building a pipeline, running disciplined sales cycles, and closing high-impact deals. You’ll work within a structured selling environment with defined territories, clear go-to-market plays, integrated sales support tools, and opportunities to develop Centers of Influence (COI) partnerships and expand your professional network—so you can focus on what matters most: winning."
That seems like part of about the role.
Then responsibilities: list bullet points under "Responsibilities What You’ll Do". We'll extract bullet points:
- Hunt and close net-new enterprise business with organizations 100 to 5,000+ employees across defined territories
- Run disciplined full-cycle sales from executive-level prospecting through multi-stakeholder discovery, demo, and close
- Build high-value solution bundles or standalone solutions across the full One Paychex Portfolio, including PEO, HR Solutions, Managed Payroll, Benefits, Retirement, Merchant Services, and more, while earning accelerators on every module you attach.
- Partner with Solutions Engineers, RevOps, and a world-class channel ecosystem, including 700+ active broker relationships and financial services firms in a GTM team-selling environment, so you are never building alone.
- Own your pipeline with rigorous forecasting, disciplined front-end prospecting, and deal control through the close.
Now "What It Takes To Win" is requirements. Extract bullet points:
- 5+ years of quota-carrying experience or complex B2B sales with a verifiable track record of hunting, building a pipeline, and closing
- Proven ability to engage economic buyers at the C-level and navigate multi-stakeholder engagement
- Experience selling into organizations of 100+ employees
- High accountability, resilience, and ownership of results because this team sets high expectations and meets them
Now "Why This Role Unlimited earning potential..." maybe could be part of overview or benefits but we can include as part of About the role? It's more like selling points. Could be included under About the role as additional paragraph. Let's capture that text:
"Unlimited earning potential tied to performance and results with a focus on career development
World-Class Club Experiences for Top Performers
Access to larger, more strategic deals with real business impact
More ways to win! We offer a broad portfolio of products and services beyond tech to increase deal size
An AI-Powered Platform That Closes Deals Faster
A Commission Plan Engineered for Top Performers"
We can format as a paragraph or list? It's a list of bullet-like statements. Could be - . But the instruction: use
- for any list of duties/requirements/benefits. This is more like benefits/perks. Could treat as benefits. But we already have a Benefits section later. Might combine? However the Benefits section later is about wellness, PTO, etc. This "Why This Role" is more about role-specific perks. Could be part of About the role. We'll keep as a paragraph with
- maybe under About the role? But we already have About the role as prose; we could add a
inside? The instruction: Use - for any list of duties/requirements/benefits. So if we treat these as benefits (role-specific), we could put them under Benefits section. But we already have Benefits section for wellness etc. Might be okay to have two benefit lists? But we should avoid duplicate sections. Could merge them into one Benefits section that includes both wellness and role perks. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine all benefits into one Benefits section. That would include both the wellness benefits and the role perks (unlimited earning potential, etc). That seems reasonable.
Thus Benefits section will contain both sets: the "What's in it for you?" wellness benefits and the "Why This Role" perks.
Now Qualifications: list includes:
- H.S. Diploma - Required
- Bachelor's Degree - Preferred
- 5 years of experience in relevant professional sales.
- 3 years of experience in HCM industry.
- Driver's License - Required
- Sales - Preferred
- Assertiveness - Preferred
- Business Acumen - Preferred
- Strong Work Ethic - Preferred
- Time Management - Preferred
- Sales Prospecting - Preferred
- Enterprise Sales - Preferred
- Sales Strategy - Preferred
- Customer Relationship Management - Preferred
- Selling Techniques - Preferred
- Closing (Sales) - Preferred
- Go-to-Market Strategy - Preferred
- Business To Business - Preferred
- Market Share - Preferred
- Cold Calling - Preferred
We need to output as list.
Skills: The posting didn't have a separate Skills section; the qualifications list includes many skill-like items. But we could treat those as Skills. However we already have Qualifications section for education/experience requirements. The list includes many "Preferred" items that are skills. Could we split? The instruction: Use sections only when posting has real specific content. The posting has a "Qualifications" heading with those items. It does not have a separate "Skills" heading. So we should not create a Skills section unless there is explicit content. The list under Qualifications includes both qualifications and skills. We'll keep them under Qualifications.
Thus sections: About the role, Responsibilities, Requirements (What It Takes To Win), Qualifications, Benefits.
Now we need to strip boilerplate: Remove EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "Live the Paychex Values" maybe? It's values list; could be considered part of About the role? It's a list of values; could be included as a paragraph. But it's not under a heading; we could include as a paragraph under About the role. However it's a list; we could format as
- . But it's not duties/requirements/benefits; it's values. Could be prose. We'll include as a paragraph.
Also remove "Note: The benefits described apply to full-time employees..." maybe keep as part of benefits paragraph.
Also remove "Not sure if you meet every requirement? ..." that's encouragement to apply; maybe consider boilerplate? It's not essential; could be removed. It's more like application encouragement. We'll remove.
Also remove "Paychex is an equal opportunity employer..." etc.
Now construct HTML.
We'll start with
About the role
then paragraphs.
We need to preserve all substantive information; we must not lose any.
Let's craft About the role content: combine the initial overview paragraph, the "Where Complexity Meets Structure..." paragraph, and the "Why This Role" perks? Actually we decided to put perks in Benefits. So About the role will include overview and the description of the role (the paragraph about enterprise sales). Also maybe include the values list.
Thus About the role paragraph(s):
Paragraph1: "Paychex is reimagining how businesses manage their workforce by bringing payroll, HR, benefits, and advisory services together into a single connected HCM platform. As Paychex and Paycor come together, we're combining innovative technology, data-driven insights, AI, and human expertise to help organizations work smarter, support their people, and achieve better business outcomes. This is an exciting time to join our team as we continue to invest in innovation, simplify client experiences, and shape the future of work. At Paychex, you'll have the opportunity to grow your career, make a meaningful impact, and be part of something bigger as One Paychex."
Paragraph2: "Where Complexity Meets Structure and Top Performers Win There is a reason enterprise buyers are moving to Paycor. We built something no one else in the market can replicate: AI-enabled enterprise technology backed by the deepest operational expertise in the HCM industry. Our platform is purpose-built for how enterprise HR and finance actually work. When you sell for Paycor, you are not asking buyers to take a leap of faith. You are bringing them the answer the market has been waiting
for prose. We need to decide sections: About the role (overview), Responsibilities, Requirements (maybe qualifications?), Qualifications (maybe separate?), Skills, Benefits. The posting has "Qualifications" list and also "Why This Role Unlimited earning potential..." which is more like benefits? Actually that is more like "Why this role" maybe could be part of overview. But we can treat as part of overview. We have "What It Takes To Win" which is like requirements. Then "Qualifications" list. Then "Live the Paychex Values". Then "What's in it for you?" benefits. Thus sections: About the role (overview + maybe why this role), Responsibilities, Requirements (What It Takes To Win), Qualifications (H.S. Diploma etc), Skills (list of preferences), Benefits (What's in it for you?). Ensure we don't create empty sections. We must not include headings with filler like "commensurate with experience". Not present. Now extract content. Overview: The first paragraph(s) up to "Overview Where Complexity Meets Structure and Top Performers Win". Actually the heading "Overview Where Complexity Meets Structure and Top Performers Win" seems like a heading but we should not repeat job title; we can treat that as part of About the role heading. We'll put
About the role
then paragraphs. Let's capture overview text: "Paychex is reimagining how businesses manage their workforce by bringing payroll, HR, benefits, and advisory services together into a single connected HCM platform. As Paychex and Paycor come together, we're combining innovative technology, data-driven insights, AI, and human expertise to help organizations work smarter, support their people, and achieve better business outcomes. This is an exciting time to join our team as we continue to invest in innovation, simplify client experiences, and shape the future of work. At Paychex, you'll have the opportunity to grow your career, make a meaningful impact, and be part of something bigger as One Paychex." Then maybe also include the paragraph after overview: "Where Complexity Meets Structure and Top Performers Win There is a reason enterprise buyers are moving to Paycor. We built something no one else in the market can replicate: AI-enabled enterprise technology backed by the deepest operational expertise in the HCM industry. Our platform is purpose-built for how enterprise HR and finance actually work. When you sell for Paycor, you are not asking buyers to take a leap of faith. You are bringing them the answer the market has been waiting for. Enterprise Sales at Paycor is built for experienced sellers who want to operate at a higher level. You’ll partner with organizations of 100+ employees, helping them solve complex workforce challenges through a modern, end-to-end HCM platform and service experience. This is a true new-logo, advisory services role, focused on building a pipeline, running disciplined sales cycles, and closing high-impact deals. You’ll work within a structured selling environment with defined territories, clear go-to-market plays, integrated sales support tools, and opportunities to develop Centers of Influence (COI) partnerships and expand your professional network—so you can focus on what matters most: winning." That seems like part of about the role. Then responsibilities: list bullet points under "Responsibilities What You’ll Do". We'll extract bullet points: - Hunt and close net-new enterprise business with organizations 100 to 5,000+ employees across defined territories - Run disciplined full-cycle sales from executive-level prospecting through multi-stakeholder discovery, demo, and close - Build high-value solution bundles or standalone solutions across the full One Paychex Portfolio, including PEO, HR Solutions, Managed Payroll, Benefits, Retirement, Merchant Services, and more, while earning accelerators on every module you attach. - Partner with Solutions Engineers, RevOps, and a world-class channel ecosystem, including 700+ active broker relationships and financial services firms in a GTM team-selling environment, so you are never building alone. - Own your pipeline with rigorous forecasting, disciplined front-end prospecting, and deal control through the close. Now "What It Takes To Win" is requirements. Extract bullet points: - 5+ years of quota-carrying experience or complex B2B sales with a verifiable track record of hunting, building a pipeline, and closing - Proven ability to engage economic buyers at the C-level and navigate multi-stakeholder engagement - Experience selling into organizations of 100+ employees - High accountability, resilience, and ownership of results because this team sets high expectations and meets them Now "Why This Role Unlimited earning potential..." maybe could be part of overview or benefits but we can include as part of About the role? It's more like selling points. Could be included under About the role as additional paragraph. Let's capture that text: "Unlimited earning potential tied to performance and results with a focus on career development World-Class Club Experiences for Top Performers Access to larger, more strategic deals with real business impact More ways to win! We offer a broad portfolio of products and services beyond tech to increase deal size An AI-Powered Platform That Closes Deals Faster A Commission Plan Engineered for Top Performers" We can format as a paragraph or list? It's a list of bullet-like statements. Could be- . But the instruction: use
- for any list of duties/requirements/benefits. This is more like benefits/perks. Could treat as benefits. But we already have a Benefits section later. Might combine? However the Benefits section later is about wellness, PTO, etc. This "Why This Role" is more about role-specific perks. Could be part of About the role. We'll keep as a paragraph with
- maybe under About the role? But we already have About the role as prose; we could add a
- inside? The instruction: Use
- for any list of duties/requirements/benefits. So if we treat these as benefits (role-specific), we could put them under Benefits section. But we already have Benefits section for wellness etc. Might be okay to have two benefit lists? But we should avoid duplicate sections. Could merge them into one Benefits section that includes both wellness and role perks. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine all benefits into one Benefits section. That would include both the wellness benefits and the role perks (unlimited earning potential, etc). That seems reasonable.
Thus Benefits section will contain both sets: the "What's in it for you?" wellness benefits and the "Why This Role" perks.
Now Qualifications: list includes:
- H.S. Diploma - Required
- Bachelor's Degree - Preferred
- 5 years of experience in relevant professional sales.
- 3 years of experience in HCM industry.
- Driver's License - Required
- Sales - Preferred
- Assertiveness - Preferred
- Business Acumen - Preferred
- Strong Work Ethic - Preferred
- Time Management - Preferred
- Sales Prospecting - Preferred
- Enterprise Sales - Preferred
- Sales Strategy - Preferred
- Customer Relationship Management - Preferred
- Selling Techniques - Preferred
- Closing (Sales) - Preferred
- Go-to-Market Strategy - Preferred
- Business To Business - Preferred
- Market Share - Preferred
- Cold Calling - Preferred
We need to output as list.
Skills: The posting didn't have a separate Skills section; the qualifications list includes many skill-like items. But we could treat those as Skills. However we already have Qualifications section for education/experience requirements. The list includes many "Preferred" items that are skills. Could we split? The instruction: Use sections only when posting has real specific content. The posting has a "Qualifications" heading with those items. It does not have a separate "Skills" heading. So we should not create a Skills section unless there is explicit content. The list under Qualifications includes both qualifications and skills. We'll keep them under Qualifications.
Thus sections: About the role, Responsibilities, Requirements (What It Takes To Win), Qualifications, Benefits.
Now we need to strip boilerplate: Remove EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "Live the Paychex Values" maybe? It's values list; could be considered part of About the role? It's a list of values; could be included as a paragraph. But it's not under a heading; we could include as a paragraph under About the role. However it's a list; we could format as
- . But it's not duties/requirements/benefits; it's values. Could be prose. We'll include as a paragraph.
Also remove "Note: The benefits described apply to full-time employees..." maybe keep as part of benefits paragraph.
Also remove "Not sure if you meet every requirement? ..." that's encouragement to apply; maybe consider boilerplate? It's not essential; could be removed. It's more like application encouragement. We'll remove.
Also remove "Paychex is an equal opportunity employer..." etc.
Now construct HTML.
We'll start with
About the role
then paragraphs. We need to preserve all substantive information; we must not lose any. Let's craft About the role content: combine the initial overview paragraph, the "Where Complexity Meets Structure..." paragraph, and the "Why This Role" perks? Actually we decided to put perks in Benefits. So About the role will include overview and the description of the role (the paragraph about enterprise sales). Also maybe include the values list. Thus About the role paragraph(s): Paragraph1: "Paychex is reimagining how businesses manage their workforce by bringing payroll, HR, benefits, and advisory services together into a single connected HCM platform. As Paychex and Paycor come together, we're combining innovative technology, data-driven insights, AI, and human expertise to help organizations work smarter, support their people, and achieve better business outcomes. This is an exciting time to join our team as we continue to invest in innovation, simplify client experiences, and shape the future of work. At Paychex, you'll have the opportunity to grow your career, make a meaningful impact, and be part of something bigger as One Paychex." Paragraph2: "Where Complexity Meets Structure and Top Performers Win There is a reason enterprise buyers are moving to Paycor. We built something no one else in the market can replicate: AI-enabled enterprise technology backed by the deepest operational expertise in the HCM industry. Our platform is purpose-built for how enterprise HR and finance actually work. When you sell for Paycor, you are not asking buyers to take a leap of faith. You are bringing them the answer the market has been waiting
- . But it's not duties/requirements/benefits; it's values. Could be prose. We'll include as a paragraph.
Also remove "Note: The benefits described apply to full-time employees..." maybe keep as part of benefits paragraph.
Also remove "Not sure if you meet every requirement? ..." that's encouragement to apply; maybe consider boilerplate? It's not essential; could be removed. It's more like application encouragement. We'll remove.
Also remove "Paychex is an equal opportunity employer..." etc.
Now construct HTML.
We'll start with
- for any list of duties/requirements/benefits. So if we treat these as benefits (role-specific), we could put them under Benefits section. But we already have Benefits section for wellness etc. Might be okay to have two benefit lists? But we should avoid duplicate sections. Could merge them into one Benefits section that includes both wellness and role perks. However the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine all benefits into one Benefits section. That would include both the wellness benefits and the role perks (unlimited earning potential, etc). That seems reasonable.
Thus Benefits section will contain both sets: the "What's in it for you?" wellness benefits and the "Why This Role" perks.
Now Qualifications: list includes:
- H.S. Diploma - Required
- Bachelor's Degree - Preferred
- 5 years of experience in relevant professional sales.
- 3 years of experience in HCM industry.
- Driver's License - Required
- Sales - Preferred
- Assertiveness - Preferred
- Business Acumen - Preferred
- Strong Work Ethic - Preferred
- Time Management - Preferred
- Sales Prospecting - Preferred
- Enterprise Sales - Preferred
- Sales Strategy - Preferred
- Customer Relationship Management - Preferred
- Selling Techniques - Preferred
- Closing (Sales) - Preferred
- Go-to-Market Strategy - Preferred
- Business To Business - Preferred
- Market Share - Preferred
- Cold Calling - Preferred
We need to output as list.
Skills: The posting didn't have a separate Skills section; the qualifications list includes many skill-like items. But we could treat those as Skills. However we already have Qualifications section for education/experience requirements. The list includes many "Preferred" items that are skills. Could we split? The instruction: Use sections only when posting has real specific content. The posting has a "Qualifications" heading with those items. It does not have a separate "Skills" heading. So we should not create a Skills section unless there is explicit content. The list under Qualifications includes both qualifications and skills. We'll keep them under Qualifications.
Thus sections: About the role, Responsibilities, Requirements (What It Takes To Win), Qualifications, Benefits.
Now we need to strip boilerplate: Remove EEO, equal opportunity, scam warning, navigation, cookie, legal, duplicated lines, application instructions. Also remove "Live the Paychex Values" maybe? It's values list; could be considered part of About the role? It's a list of values; could be included as a paragraph. But it's not under a heading; we could include as a paragraph under About the role. However it's a list; we could format as
- maybe under About the role? But we already have About the role as prose; we could add a
- for any list of duties/requirements/benefits. This is more like benefits/perks. Could treat as benefits. But we already have a Benefits section later. Might combine? However the Benefits section later is about wellness, PTO, etc. This "Why This Role" is more about role-specific perks. Could be part of About the role. We'll keep as a paragraph with