Sales Development Representative

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (Required Qualifications), maybe Qualifications (Preferred Qualifications?), Benefits (Compensation & Benefits), Pay (if specific numbers given), Schedule (Hybrid work schedule). Also maybe "How Success Is Measured" could be part of responsibilities or separate? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - About The Role: paragraph. - What You'll Do: list of duties. - How Success Is Measured: list of metrics. Could be considered part of Responsibilities or maybe separate "Performance Metrics". Not in list of allowed headings but we could put under Responsibilities? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: About the role -> About The Role paragraph. Responsibilities -> What You'll Do list. Requirements -> Required Qualifications list. Qualifications -> Preferred Qualifications list. Skills maybe not needed; we could omit if no specific skills section. Benefits -> Compensation & Benefits list (benefits details). Pay -> Salary Description $62,000-$97,000 (specific numbers). Also "Competitive base salary with bonus potential Pay commensurate with experience". The posting includes both a range and statement. We have specific numbers, so we can include Pay section with that range. Schedule -> Hybrid work schedule (Leesburg, VA). Also mention "Hybrid work schedule (Leesburg, VA)". So we can include Schedule. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO etc. Also remove "Other duties as assigned" maybe keep as part of responsibilities? It's a line; we can keep as list item. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

The Sales Development Representative (SDR) generates qualified sales opportunities that support Vertosoft’s Government Sales pipeline. This role focuses on outbound prospecting, inbound lead qualification, and early-stage account engagement targeting federal, state, and local government prospects. As the primary top-of-funnel pipeline driver, the SDR executes structured sales campaigns in partnership with marketing, Inside Sales Representatives, and technology vendor partners. This is a metrics-driven role requiring strong communication skills, disciplined CRM management, and the ability to identify buying signals within the public sector procurement landscape. This position is designed as a foundational sales role with a clear path toward Inside Sales Representative (ISR) or other revenue-generating positions based on performance and development.

Responsibilities

• Execute outbound prospecting campaigns via phone, email, and LinkedIn targeting government decisionmakers
• Follow up on marketing-generated leads and campaign responses
• Identify and engage key stakeholders within assigned public sector accounts
• Apply established qualification frameworks to assess opportunity viability
• Gather and document budget, authority, need, timeline, and contract vehicle alignment details
• Schedule qualified discovery meetings for ISR or Account Executive team members
• Maintain accurate and timely records in Salesforce (or designated CRM)
• Track activities, meeting outcomes, and opportunity notes to ensure data integrity
• Collaborate with ISR, Account Executives, marketing, and vendor partners to support campaign execution
• Other duties as assigned

Requirements

• BA/BS degree in Business, Marketing, Communications, or related field
• Strong written and verbal communication skills
• Ability to manage time effectively in a metrics-driven environment
• High level of organization and attention to detail

Qualifications

• Internship or experience in sales, customer service, or business development
• Familiarity with CRM platforms (Salesforce, HubSpot)
• Interest in government procurement or public sector technology

Benefits

• Comprehensive benefits package including health, dental, vision
• 401(k) with company match
• Paid Time Off (PTO) and all Federal holidays
• Career development, certifications, and growth opportunities
• Successful SDRs may be eligible for promotion to ISR or Account Executive roles based on performance, completion of required training program, and tenure.

Pay

$62,000-$97,000 (competitive base salary with bonus potential, pay commensurate with experience)

Schedule

Hybrid work schedule (Leesburg, VA)

We need to ensure we didn't include filler like "commensurate with experience" as placeholder? It's actual text from posting; it's okay. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - but that refers to headings with filler content. If we include Pay heading, we must have substantive content; we have the salary range plus note. That's okay. We also included "Competitive base salary with bonus potential Pay commensurate with experience" inside the Pay paragraph; that's not filler. Check for any duplicated lines: we removed "Other duties as assigned" kept as list item. We removed "About Vertosoft" paragraph? That's substantive but not in allowed headings; we could incorporate into About the role? The instruction: Prefer a few substantive sections over many thin ones. The About Vertosoft is company description; could be omitted? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Where could we put? Possibly under About the role? But that is about the role, not company. Could add another section like "About the company" but not in allowed headings. However we could incorporate into About the role as additional paragraph? The instruction says use headings from list; but we could add a paragraph without heading? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs without heading. It said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot have other headings, but we should follow the pattern. Safer to add another section like "About Vertosoft" but not in list; maybe we can treat it as "About the role" extended? However the About the role already defined; we could add a second paragraph under About the role describing the company. That would preserve info without new heading. Let's do that: after the About the role paragraph, add another paragraph describing Vertosoft. Thus About the role section will have two paragraphs: first about role, second about company. Check if any other substantive info: "Successful SDRs may be eligible for promotion to ISR or Account Executive roles based on performance, completion of required training program, and tenure." Already included in Benefits section (we added as bullet). Good. Also "Career development, certifications, and growth opportunities" included. We also have "Competitive base salary with bonus potential Pay commensurate with experience" we included in Pay paragraph. We also have "Hybrid work schedule (Leesburg, VA)" in Schedule. We also have "Paid Time Off (PTO) and all Federal holidays" in Benefits. We also have "401(k) with company match". We also have "Comprehensive benefits package including health, dental, vision". We also have "Successful SDRs may be eligible for promotion to ISR or Account Executive roles based on performance, completion of required training program, and tenure." Already. We also have "This position is designed as a foundational sales role with a clear path toward Inside Sales Representative (ISR) or other revenue-generating positions based on performance and development." Already in About the role. We also have "As the primary top-of-funnel pipeline driver, the SDR executes structured sales campaigns in partnership with marketing, Inside Sales Representatives, and technology vendor partners." Already. We also have "This is a metrics-driven role requiring strong communication skills, disciplined CRM management, and the ability to identify buying signals within the public sector procurement landscape." Already. We also have "Follow up on marketing-generated leads and campaign responses" etc. We also have "Identify and engage key stakeholders within assigned public sector accounts". We also have "Apply established qualification frameworks to assess opportunity viability". We also have "Gather and document budget, authority, need, timeline, and contract vehicle alignment details". We also have "Schedule qualified discovery meetings for ISR or Account Executive team members". We also have "Maintain accurate and timely records in Salesforce (or designated CRM)". We also have "Track activities, meeting outcomes, and opportunity notes to ensure data integrity". We also have "Collaborate with ISR, Account Executives, marketing, and vendor partners to support campaign execution". We also have "Other duties as assigned". We also have "How Success Is Measured" metrics: we haven't included that. That's substantive; we need to include it somewhere. Could be a separate section like "Performance Metrics" but not in allowed headings. Could incorporate into Responsibilities or Requirements? Probably better to add a section "Performance Metrics" but not allowed. However we could incorporate into Responsibilities as a list? But it's about how success measured, not duties. Could add a section with heading "Performance Metrics" but that deviates from allowed headings. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we must include all substantive information; we could incorporate the metrics into Responsibilities as a sub-list? Might be okay to add a separate section with heading "Performance Metrics" but risk violating instruction. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to include metrics under a heading like "Performance Metrics" but maybe they'd consider it extra heading not in list; but they said e.g., meaning examples, not exhaustive. I'd include a section "Performance Metrics" with

. It's substantive. Let's add:

Performance Metrics

• Meetings booked and accepted by ISR/AE
• Qualified opportunities generated
• Lead-to-opportunity conversion rate
• Activity volume (calls, emails, touches)
• CRM accuracy and compliance
• Demonstrated improvement in qualification quality over time

Now check if any other substantive info: "Successful SDRs may be eligible for promotion to ISR or Account Executive roles based on performance, completion of required training program, and tenure." Already in Benefits. Also "Career development, certifications, and growth opportunities" in Benefits. Also "Competitive base salary with bonus potential Pay commensurate with experience" we included. Also "Hybrid work schedule (Leesburg, VA)" in