Senior Business Development Representative

We need to output HTML fragment with sections using

for headings: About the role, e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. No filler like "commensurate with experience". We must not repeat job title as heading. No Job ID etc. Remove boilerplate (EEO, etc). Must preserve all substantive info. We need to parse the posting. Key parts: - The Opportunity: description of role, responsibilities, etc. - "Is this opportunity for you?" then "Role To help you establish whether this role is for you, these are the key foundational characteristics you will need to be set up for success:" then bullet list of characteristics. - "How You'll Show Us" then bullet list of evidence. - "What We Do" description. - "Who We Are" description. - "WHY JOIN US?" then bullet list of benefits and initiatives. We need to map to sections: About the role (maybe overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: could be the initial description: "Reporting directly to our BDR Team Lead and based in our Irving, TX office, we are seeking a proactive senior individual contributor and player-coach who will help build and scale our BDR function across AMS, whilst delivering against their own KPIs. This is a first among equals role. You will set the standard on the floor as a high-performing BDR, and act as the eyes and ears on the ground for the wider AMS team, supporting day-to-day execution, KPI delivery, and the onboarding and development of new BDRs. You will support the BDRs around you, but you will not carry direct line management responsibility for their reporting or outcomes. That accountability sits with the BDR Team Lead. Our ideal candidate brings a strong foundation in Enterprise B2B sales development, a solutions-focused and innovative mindset, and the ability to adapt as the sales landscape evolves." That's about role. - Responsibilities: the list after "In this two-pronged role of individual contributor and team support, you can expect to:" then bullet list of responsibilities (starting with "Own and consistently deliver your own pipeline target..." etc). That's responsibilities. - Requirements/Qualifications/Skills: The "Is this opportunity for you?" section lists key foundational characteristics: a year or more of BDR or Inside Sales experience selling B2B SaaS or Enterprise software solutions, with a track record of consistent top performance against target; experience in complex enterprise sales cycles, engaging senior stakeholders through tailored, intent-based outreach rather than a volume approach; a genuine sense of ownership over your numbers, and the resilience to keep pipeline moving through rejection and quiet periods; a natural mentor who enjoys helping peers improve, and is ready to take informal ownership of team activity without formal line management responsibility; sound judgment on where to spend your time, and the credibility to influence peers and cross-functional partners without authority; naturally curious and proactive about adopting new tools, techniques, and strategies, with a strong problem-solving instinct and a passion for building new processes; clear, confident communication, in writing and on the phone, that adapts to different audiences; comfortable operating in a remote and global environment. These could be Requirements or Qualifications. We can put them under Requirements (or Qualifications). The posting also has "How You'll Show Us" which is about evidence; could be considered Skills? Might be better to treat as "Skills" or "Qualifications". But we need to avoid duplication. Perhaps we can have Requirements (experience etc) and Skills (communication, mentorship, etc). However the list includes both experience and skills. Could combine into Requirements. We also have "What We Do", "Who We Are" maybe not needed as separate sections; could be part of About the role or omitted if not fitting headings. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We can include About the role, Responsibilities, Requirements, Benefits. Possibly also Skills if distinct. Pay and Schedule: The posting mentions "Hybrid working (3 days per week in our Irving, TX office)" and "Global Flexibility (work abroad up to 1 month per year)". That's schedule info. Also "Competitive salary package and bonus" under Benefits. So we have Pay info? It says competitive salary package and bonus but not specific numbers. That's vague; but it's still mention of compensation. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive salary package and bonus (though not specific). That's still stating something about pay. Should we include Pay section? It says "competitive salary package and bonus" - that's a statement about pay, albeit not specific. It's not filler like "commensurate with experience". It's a concrete statement: they offer competitive salary and bonus. So we can include Pay section with that sentence. Benefits: they list many benefits: Company 401(k) retirement plan, Generous paid time off, plus public holidays, Hybrid working (3 days per week in our Irving, TX office), Global Flexibility (work abroad up to 1 month per year), Enhanced Parental Leave, Paid Volunteer Day, Learning and Development Budget, STEM Ambassador Programme Partnership, Monthly Shared Knowledge Sessions, Mental Health First Aiders Programme. Also earlier they mentioned Learning and Development budget, Mental Health First Aiders. So we can put Benefits section. Schedule: The hybrid working and global flexibility could be considered schedule. But we already used hybrid working in Benefits. Might be better to put schedule info under Schedule section: Hybrid working (3 days per week in our Irving, TX office), Global Flexibility (work abroad up to 1 month per year). However those are also benefits. But we can still include Schedule if we want. The instruction: prefer a few substantive sections over many thin ones. So maybe combine schedule into Benefits or omit separate Schedule. Since we already have Benefits covering many items, we could include hybrid working and global flexibility there. Then we may not need Schedule section. Pay: we have competitive salary package and bonus. That's substantive enough for Pay section. Thus sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No markdown. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details precisely. About the role paragraph: We'll copy the paragraph(s) before responsibilities. From text: "The Opportunity Reporting directly to our BDR Team Lead and based in our Irving, TX office, we are seeking a proactive senior individual contributor and player-coach who will help build and scale our BDR function across AMS, whilst delivering against their own KPIs. This is a first among equals role. You will set the standard on the floor as a high-performing BDR, and act as the eyes and ears on the ground for the wider AMS team, supporting day-to-day execution, KPI delivery, and the onboarding and development of new BDRs. You will support the BDRs around you, but you will not carry direct line management responsibility for their reporting or outcomes. That accountability sits with the BDR Team Lead. Our ideal candidate brings a strong foundation in Enterprise B2B sales development, a solutions-focused and innovative mindset, and the ability to adapt as the sales landscape evolves." That's one paragraph. We'll put that in

  . Responsibilities: list after "In this two-pronged role of individual contributor and team support, you can expect to:" then bullet points: - Own and consistently deliver your own pipeline target, taking full responsibility for the qualified opportunities you generate and setting the performance benchmark for the AMS team - Design and run multi-step, multi-channel outbound sequences across email, phone, and LinkedIn, tailoring messaging and cadence to account and persona rather than relying on volume - Identify and act on early buying signals, trigger events, and organisational changes to create opportunities before they are formally defined - Lead structured discovery using SPICED, uncover the business impact behind a prospect's challenges, and secure well-qualified meetings with the context Account Executives need to convert - Act as a player-coach and first point of contact on the floor, providing hands-on guidance, peer feedback and day-to-day coaching support to fellow BDRs - Support the BDR Team Lead with the day-to-day running of team activity, monitoring execution against KPIs and surfacing what is and is not working on the ground - Support the onboarding, training and ramp of new BDRs, helping them reach productivity faster - Test and refine outreach approaches, messaging, and targeting, and share what works so the wider team improves - Communicate value in commercial terms, framing the conversation around business outcomes, efficiency, and risk rather than product features - Partner with Sales and Marketing to align outbound strategy, account targeting and lead handoff - Use Salesforce, Apollo, and LinkedIn to manage outreach, maintain clean and reliable data, and track results - Stay informed on SAP ecosystem developments, market trends, and competitive dynamics to sharpen the relevance of outreach and positioning - Foster a culture of experimentation, learning, and continuous improvement We'll put each as

• . Requirements: The "Is this opportunity for you?" section bullet list: - A year or more of BDR or Inside Sales experience selling B2B SaaS or Enterprise software solutions, with a track record of consistent top performance against target - Experience in complex enterprise sales cycles, engaging senior stakeholders through tailored, intent-based outreach rather than a volume approach - A genuine sense of ownership over your numbers, and the resilience to keep pipeline moving through rejection and quiet periods - A natural mentor who enjoys helping peers improve, and is ready to take informal ownership of team activity without formal line management responsibility - Sound judgment on where to spend your time, and the credibility to influence peers and cross-functional partners without authority - Naturally curious and proactive about adopting new tools, techniques, and strategies, with a strong problem-solving instinct and a passion for building new processes - Clear, confident communication, in writing and on the phone, that adapts to different audiences - Comfortable operating in a remote and global environment We'll put as
• under Requirements. We could also include "How You'll Show Us" as maybe Skills or Evidence but we can omit to avoid thin sections. However that is substantive: they ask for evidence of pipeline result, helping peer improve, testing outreach. Could be considered "Skills" or "Qualifications". But we already have Requirements covering experience and traits. The "How You'll Show Us" is about what they want to see in application; not a requirement per se but still substantive. Could be included under a section like "What We Look For in Your Application" but not in allowed headings. Allowed headings are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put that under Skills. But we already have Requirements; maybe we can treat "How You'll Show Us" as Skills. However the list is about evidence, not skills. Might be better to omit to keep sections few. The instruction: prefer a few substantive sections over many thin ones. So we can omit How You'll Show Us. What We Do and Who We Are: Could be included under About the role? Might be extra but not required headings. Could be omitted to keep sections few. However they are substantive about company. But we have no heading for company description; we could incorporate into About the role as extra paragraph. But the About the role currently is about the role; we could add a paragraph about what we do and who we are after that. That would still be under About the role heading, which is allowed. So we can add additional

  after the role description containing "What We Do..." and "Who We Are..." paragraphs. Thus About the role will have multiple paragraphs: role description, what we do, who we are.