Sales Executive / Business Development (MSP)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must preserve all substantive info, remove boilerplate, navigation, EEO, etc. No job title heading. No Job ID as heading; can fold into short p or drop. So we need to parse the posting. Content: - Sr. Sales Exec / Business Development Location: Remote / WHF from IL, MN, OH, PA, KS, IA, MO - Company: National MSP focused on the Healthcare industry - Compensation: Lucrative base plus uncapped commissions, and great benefits - Position Type: Full-Time/Perm - Position ID: 1792 (we can drop or put in p) - Then description: "We’re searching for a proven Sales / Business Development Executive who knows how to win new clients and close high-value managed-services agreements." - Then bullet list (actually lines) of "You may be a strong fit if you have:" then items: - A successful track record selling managed IT services (3+ years experience in MSP or MSSP) - Experience developing net-new business and closing ~$5K+ MRR deals (hunter mentality) - Strong relationships with CIOs and other technology leaders - Consistent quota achievement with stable employment history - OK with travel within the region (25% - 50% at times) - Sales experience in any of the following is a plus: Healthcare, cyber security services/solutions, compliance services - Then: "This is an excellent opportunity to represent a growing MSP with a strong portfolio of managed IT, cybersecurity, and/or compliance solutions." - Then: "Interested - or know someone exceptional? Send me a confidential message. If this sounds like you, Contact me." - Then contact info: Karel Lukas, Managing Partner, The Trevi Group, karel@thetrevigroup.com - Then referral program: "If this position is not the right match for you... then who comes to mind that should hear about it. Any recommendations you provide will be tagged confidentially with your name so that if we place that person within one year, we will send you a $1,000 Amex Gift Card to thank you for your help. Just know that when we contact people that you recommend to us, we contact them confidentially and never mention your name. Your referrals are handled in a completely confidential manner." - Then hashtags. We need to remove application instructions? The instruction says: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The contact info and "Send me a confidential message" might be considered application instructions? Possibly we should keep contact info? The instruction says remove application instructions. The posting includes "Interested - or know someone exceptional? Send me a confidential message. If this sounds like you, Contact me." That's basically an instruction to apply. So we should remove that. Also the referral program might be considered not application instruction but maybe keep? It's not exactly application instruction but it's a referral incentive. Might be considered part of posting; we can keep as it's substantive info about referral bonus. However it's somewhat like a call to action. The instruction says remove application instructions, not necessarily referral program. But the referral program includes instructions to refer. Might be considered similar. Safer to remove referral program as well? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The referral program is not exactly an application instruction for the job itself, but it's a referral incentive. Might be okay to keep. However the line "If this position is not the right match for you... then who comes to mind that should hear about it." is basically a referral request. Could be considered application instruction? I'd lean to keep it as it's substantive info about referral bonus. But to be safe, maybe keep it as a

under Benefits? Not exactly. Could be its own section like "Referral Program". But we only have allowed headings list; we cannot create new headings not in list. So we could fold it into Benefits or maybe into a

under Benefits? But Benefits section is for benefits like health insurance etc. The referral bonus is not a benefit to the employee but a referral incentive. Might be better to drop it as it's akin to application instruction. I'd drop it. Thus we keep: location, company, compensation, position type, description, requirements list, plus maybe the opportunity statement. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: could include description of role: "We’re searching for a proven Sales / Business Development Executive who knows how to win new clients and close high-value managed-services agreements." plus maybe the opportunity statement: "This is an excellent opportunity to represent a growing MSP with a strong portfolio of managed IT, cybersecurity, and/or compliance solutions." - Responsibilities: maybe not explicitly listed. The posting doesn't list specific responsibilities beyond winning new clients and closing deals. Could infer responsibilities: win new clients, close high-value managed-services agreements, develop net-new business, maintain relationships with CIOs, achieve quota, travel. But we must not invent or summarize away detail; we must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot create responsibilities that aren't explicitly stated. The posting does not have a separate responsibilities section; it's more about what you need to have. So we should not create a Responsibilities heading if there is no specific content. So we skip Responsibilities. - Requirements: we have the list of items under "You may be a strong fit if you have:" which are requirements. So we can put those under Requirements heading. - Qualifications: maybe overlapping with requirements; but we could treat the list as Qualifications. However we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have to use headings only if there is real specific content. We could put the list under Requirements and not have Qualifications. Or we could put under Qualifications and not Requirements. Which is more appropriate? The list includes experience, track record, relationships, quota achievement, travel, plus plus experience in healthcare etc. Those are qualifications/requirements. I'd choose Requirements as heading. - Skills: maybe we could extract skills like "selling managed IT services", "developing net-new business", "closing deals", "relationship building", "quota achievement", "travel". But those are already in the list. If we already used Requirements, we could skip Skills to avoid thin sections. - Benefits: we have "Lucrative base plus uncapped commissions, and great benefits". That's vague but mentions benefits. It's not specific like health insurance etc. The instruction says 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. Here they state "great benefits" but not specifics. Is that considered filler? It's vague but it's a statement that benefits are great. Might be considered placeholder? The instruction says avoid filler like "commensurate with experience", "not specified", etc. "great benefits" is vague but not exactly those phrases. However it's still not specific. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "great benefits". So we could include a Benefits section with that statement. But we should avoid filler/placeholder text like "great benefits" maybe considered placeholder? Not sure. I'd include it as a short

under Benefits. - Pay: they state "Lucrative base plus uncapped commissions". That's compensation info. So we can have Pay section with that statement. - Schedule: they mention "Full-Time/Perm" and location remote with travel 25%-50% at times. That's schedule info. So we can have Schedule section with that. - Also location info: Remote / WHF from IL, MN, OH, PA, KS, IA, MO. Could be part of About the role or maybe a separate section? Not in headings list. Could fold into About the role

. - Company: National MSP focused on the Healthcare industry. Could be in About the role. - Position ID: we can drop. Thus we will produce sections: About the role, Requirements, Benefits, Pay, Schedule. We must not repeat job title as heading. We must use

for section headings. Use

• for any list of duties/requirements/benefits. For Benefits we have just a statement, not a list, so use

  . For Requirements we have list, so

  • . For Pay and Schedule we have statements, use

    . We must preserve all substantive information: location, company, compensation, position type, description, opportunity statement, requirements list, benefits statement, pay statement, schedule statement. We must not include boilerplate like contact info, referral program, hashtags. Let's craft. About the role

    About the role

    Sr. Sales Exec / Business Development – Remote (eligible to work from IL, MN, OH, PA, KS, IA, MO). National MSP focused on the Healthcare industry. We’re searching for a proven Sales / Business Development Executive who knows how to win new clients and close high-value managed-services agreements. This is an excellent opportunity to represent a growing MSP with a strong portfolio of managed IT, cybersecurity, and/or compliance solutions.

    Requirements

    Requirements

    • A successful track record selling managed IT services (3+ years experience in MSP or MSSP)
    • Experience developing net-new business and closing ~$5K+ MRR deals (hunter mentality)
    • Strong relationships with CIOs and other technology leaders
    • Consistent quota achievement with stable employment history
    • OK with travel within the region (25% - 50% at times)
    • Sales experience in any of the following is a plus: Healthcare, cyber security services/solutions, compliance services
    Benefits

    Benefits

    Lucrative base plus uncapped commissions, and great benefits.

    Pay

    Pay

    Lucrative base plus uncapped commissions.

    Schedule

    Schedule

    Full‑time permanent position with remote work eligibility (IL, MN, OH, PA, KS, IA, MO) and occasional regional travel (25%‑50% of time).

    Check duplication: Benefits and Pay both have similar text; Benefits includes "great benefits" plus the pay line; Pay repeats the pay line. Might be redundant but we must preserve all substantive info. The posting says "Compensation: Lucrative base plus uncapped commissions, and great benefits". So we could combine into one Benefits section that includes both pay and benefits. But we have separate Pay and Benefits headings allowed. If we split, we might duplicate the pay line. Could we instead put pay in Pay section and benefits in Benefits section? Benefits section could just say "great benefits". But that's vague. However we must not create Benefits section unless posting actually states them; it does state "great benefits". So we can put that. Pay section can state "Lucrative base plus uncapped commissions". That avoids duplication. Good. Thus Benefits

    great benefits.

    Pay

    Lucrative base plus uncapped commissions.

    Schedule as above. Now ensure we didn't miss any substantive info: location remote with states list included in About the role and Schedule. Company included. Opportunity statement included. Description included. Requirements list included. Good. Now output only HTML fragment, no markdown fences. Let's produce.