Enterprise National Account Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We have Company Overview, Position Overview, Key Responsibilities, Required Qualifications, Nice-to-Have, Compensation And Benefits, Application Process, EEO statement.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop Application Process and EEO statement. Also drop Company Overview? Not a heading but we can include as prose maybe under About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Thus we need sections: About the role (position overview), Responsibilities (key responsibilities), Requirements (maybe required qualifications?), Qualifications (maybe nice-to-have?), Skills (maybe technical skills?), Benefits, Pay, Schedule. But we should only include sections if posting has real specific content. Let's map: - About the role: Position Overview paragraph: "The Enterprise National Account Manager owns the full-cycle sales relationship...". That's substantive. - Responsibilities: Key Responsibilities list (multiple bullet points). Good. - Requirements: Could be Required Qualifications? The posting has "Required Qualifications". That includes years of experience, industry background, technical skills, education. That's suitable for Requirements. - Qualifications: Could be Nice-to-Have? That's "Nice-to-Have". That could be Qualifications section. - Skills: Could be technical skills? Already covered in Required Qualifications. Might be redundant. But we could still include Skills if there is distinct content like "CRM proficiency (Salesforce preferred) and comfort operating inside a metrics-driven, scorecard-based performance environment; excellent discovery and consultative selling skills". That's already in Required Qualifications. Might be okay to not have separate Skills. - Benefits: Compensation And Benefits section includes "Earning Potential: OTE of $115K-$135K+ with uncapped commissions", "Career Growth: Clear advancement pathways, mentorship, and ongoing training", "Health & Wellness: Comprehensive medical, dental, and vision insurance for you and your family", "Work-Life Balance: Generous PTO, paid holidays, and a collaborative, high-energy culture", "Meaningful Impact: Help healthcare providers improve compliance and focus on patient care". That's benefits. - Pay: Could be separate from Benefits? The posting includes earning potential (OTE). That's pay. Could be separate Pay section. But we already have Benefits includes earning potential? Actually they listed under Compensation And Benefits. Could split: Pay section for OTE, Benefits for other perks. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section? But they said include a section ONLY when posting has real specific content for it. We have both pay and benefits details. Could make two sections: Pay and Benefits. That's okay. - Schedule: No mention of schedule (e.g., full-time, remote). Not present, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications (nice-to-have), Benefits, Pay. We need to use
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions.
We need to include all details from each section.
Let's extract content.
About the role: Position Overview paragraph:
"The Enterprise National Account Manager owns the full-cycle sales relationship with mid-market and enterprise healthcare accounts, converting fragmented, incumbent-vendor compliance arrangements into a single, coordinated MedPro/MP1 partnership. This role exists to grow MedPro's regulated waste and compliance services footprint across multi-site healthcare organizations by combining disciplined inbound execution with proactive, self-sourced outbound pipeline-building. Success looks like a rep who runs a structured, discovery-driven sales process, consistently converts a defined inbound/plus-one mix into closed, recurring-revenue agreements, and reaches full individual quota (~$35K/month GP) within 90 days — directly fueling MP1 Solutions' growth as the category-defining Compliance Services Organization."
We'll put that in
.
Responsibilities: Key Responsibilities list (multiple sentences). Let's list each bullet as
- . Need to preserve all details.
Original bullet points (some run-on sentences). Let's break them:
- Own a full-cycle enterprise sales pipeline: prospect, qualify, propose, negotiate, and close multi-site regulated waste and compliance service agreements (RMW, shredding, pharmaceutical/Rx disposal, OSHA/HIPAA/BBP training) with mid-market and enterprise healthcare accounts (ASCs, FQHCs, multi-location practice groups, health systems).
- Carry and consistently deliver against an individual quota with a defined mix target across core inbound-sourced opportunities and self-sourced (“plus-one”) pipeline.
- Run a self-sourced outbound motion in addition to inbound lead work — closed-lost account win-back calling, partner referral channels, or account-based outbound calling segmented by vertical.
- Execute a structured, discovery-driven sales process: identify the caller’s core pain (new office setup vs. dissatisfaction with an incumbent vendor), confirm the decision-maker/gatekeeper, position MedPro’s Low Cost Guarantee and bundled service offering, and drive every call to a clear next step or a direct ask for the business.
- Maintain disciplined CRM hygiene and pipeline accuracy in Salesforce, including accurate stage, forecast, and next-step data.
- Meet weekly activity, pipeline-creation, and script-adherence standards tied to MedPro’s lead-access scorecard.
- Manage populated service addenda and proposal documentation for multi-site accounts, coordinating with internal teams (compliance, account setup, billing) through contract execution and onboarding handoff.
- Participate in ongoing sales enablement — script and objection-handling refinement, AI-assisted call coaching (Steel Trap) feedback, and collateral/process improvement input.
We'll keep as is.
Requirements: Required Qualifications section includes:
"Years of experience: 3+ years of full-cycle B2B sales experience carrying and consistently exceeding an individual quota, ideally in a solution-selling or multi-product/service environment rather than a single-SKU or single-product background
Industry background: Proven ability to manage a complex, multi-stakeholder sales cycle — identifying decision-makers and gatekeepers, navigating multi-site/multi-location accounts, and closing recurring-revenue service agreements (not just one-time transactions); strong outbound/self-sourcing discipline in addition to working inbound leads
Technical skills: CRM proficiency (Salesforce preferred) and comfort operating inside a metrics-driven, scorecard-based performance environment; excellent discovery and consultative selling skills — able to run a structured discovery conversation rather than a feature/price pitch
Education: Bachelor's degree preferred (business, healthcare administration, or related field) but not required in lieu of relevant experience"
We'll put each as
- maybe under a
. Or we could keep as prose but instruction: Use - for any list of duties/requirements/benefits. This is a list of requirements, so use list.
Qualifications: Nice-to-Have:
"Demonstrated experience selling into healthcare, medical, dental, or other regulated/compliance-driven verticals (or a clearly transferable regulated-services sales background); experience selling against an entrenched incumbent competitor (competitive displacement sales)
Familiarity with value-based, guarantee-backed, or price-lock sales models; prior experience with AI-assisted call coaching/QA tools"
We'll list as
- items.
Benefits: Compensation And Benefits section includes multiple bullet-like statements. We'll treat as list.
Items:
- Earning Potential: OTE of $115K-$135K+ with uncapped commissions
- Career Growth: Clear advancement pathways, mentorship, and ongoing training
- Health & Wellness: Comprehensive medical, dental, and vision insurance for you and your family
- Work-Life Balance: Generous PTO, paid holidays, and a collaborative, high-energy culture
- Meaningful Impact: Help healthcare providers improve compliance and focus on patient care
We'll list as
- .
Pay: Could be separate section for earning potential. But we already included earning potential in Benefits. To avoid duplication, maybe we should split: Pay section for OTE, Benefits for other perks. However the instruction says prefer few substantive sections over many thin ones. Having both Pay and Benefits may be thin. But we have distinct content: earning potential (pay) and other benefits. Could combine them into one Benefits section that includes pay as an item. That seems acceptable. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use all. We can choose to have Benefits section that includes pay. That's fine.
Thus we will not create a separate Pay section.
Schedule: omitted.
Thus final HTML:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Make sure to preserve all details exactly.
Check for any duplicated lines: none.
Remove boilerplate: Company Overview? We didn't include it as a section; but we might want to include some of that as prose under About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
Company Overview is not a heading but could be considered part of About the role? However the About the role section we used Position Overview. The Company Overview provides context about the company; maybe we should include it as part of About the role? The instruction says preserve ALL substantive information. If we drop Company Overview entirely, we lose substantive info about the company. So we should include it somewhere. Perhaps we can add a short paragraph under About the role before the Position Overview, or we could create an "About the company" section but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, etc. Not About the company. But we could fold minor metadata into a short
. Company Overview is not minor metadata; it's substantive. However we could treat it as part of About the role (makes sense). So we can prepend Company Overview paragraph(s) to the About the role
. Let's extract Company Overview:
"The Compliance Services Organization didn't exist. We built it. MP1 Solutions pioneered the Compliance Services Organization (CSO) — a new category of operating partner built to replace the fragmented vendor model that has defined compliance programs for decades. Built on the foundation of MedPro Disposal, the nation’s largest privately-held medical waste company serving 35,000+ providers across 48 states over the past 15 years, MP1 Solutions extends that operational infrastructure, vendor network, and customer trust into a category we’re actively building — and leading. What we do: We operate as the single compliance partner for non-acute healthcare facilities — consolidating every obligation into one coordinated program, assigning one dedicated account manager as the point of accountability, and actively managing
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. We need to include all details from each section. Let's extract content. About the role: Position Overview paragraph: "The Enterprise National Account Manager owns the full-cycle sales relationship with mid-market and enterprise healthcare accounts, converting fragmented, incumbent-vendor compliance arrangements into a single, coordinated MedPro/MP1 partnership. This role exists to grow MedPro's regulated waste and compliance services footprint across multi-site healthcare organizations by combining disciplined inbound execution with proactive, self-sourced outbound pipeline-building. Success looks like a rep who runs a structured, discovery-driven sales process, consistently converts a defined inbound/plus-one mix into closed, recurring-revenue agreements, and reaches full individual quota (~$35K/month GP) within 90 days — directly fueling MP1 Solutions' growth as the category-defining Compliance Services Organization." We'll put that in
. Responsibilities: Key Responsibilities list (multiple sentences). Let's list each bullet as
- . Or we could keep as prose but instruction: Use
- for any list of duties/requirements/benefits. This is a list of requirements, so use list. Qualifications: Nice-to-Have: "Demonstrated experience selling into healthcare, medical, dental, or other regulated/compliance-driven verticals (or a clearly transferable regulated-services sales background); experience selling against an entrenched incumbent competitor (competitive displacement sales) Familiarity with value-based, guarantee-backed, or price-lock sales models; prior experience with AI-assisted call coaching/QA tools" We'll list as
- items. Benefits: Compensation And Benefits section includes multiple bullet-like statements. We'll treat as list. Items: - Earning Potential: OTE of $115K-$135K+ with uncapped commissions - Career Growth: Clear advancement pathways, mentorship, and ongoing training - Health & Wellness: Comprehensive medical, dental, and vision insurance for you and your family - Work-Life Balance: Generous PTO, paid holidays, and a collaborative, high-energy culture - Meaningful Impact: Help healthcare providers improve compliance and focus on patient care We'll list as
- .
Pay: Could be separate section for earning potential. But we already included earning potential in Benefits. To avoid duplication, maybe we should split: Pay section for OTE, Benefits for other perks. However the instruction says prefer few substantive sections over many thin ones. Having both Pay and Benefits may be thin. But we have distinct content: earning potential (pay) and other benefits. Could combine them into one Benefits section that includes pay as an item. That seems acceptable. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use all. We can choose to have Benefits section that includes pay. That's fine. Thus we will not create a separate Pay section. Schedule: omitted. Thus final HTML:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Company Overview is not a heading but could be considered part of About the role? However the About the role section we used Position Overview. The Company Overview provides context about the company; maybe we should include it as part of About the role? The instruction says preserve ALL substantive information. If we drop Company Overview entirely, we lose substantive info about the company. So we should include it somewhere. Perhaps we can add a short paragraph under About the role before the Position Overview, or we could create an "About the company" section but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, etc. Not About the company. But we could fold minor metadata into a short
. Company Overview is not minor metadata; it's substantive. However we could treat it as part of About the role (makes sense). So we can prepend Company Overview paragraph(s) to the About the role
. Let's extract Company Overview: "The Compliance Services Organization didn't exist. We built it. MP1 Solutions pioneered the Compliance Services Organization (CSO) — a new category of operating partner built to replace the fragmented vendor model that has defined compliance programs for decades. Built on the foundation of MedPro Disposal, the nation’s largest privately-held medical waste company serving 35,000+ providers across 48 states over the past 15 years, MP1 Solutions extends that operational infrastructure, vendor network, and customer trust into a category we’re actively building — and leading. What we do: We operate as the single compliance partner for non-acute healthcare facilities — consolidating every obligation into one coordinated program, assigning one dedicated account manager as the point of accountability, and actively managing