Jobs · Business Development · Oklahoma

Business Development Representative

General Parts Group · Oklahoma City, OK · 1 mo ago
On-siteBusiness Development$70k–$80k/yrFull-time
We need to output HTML fragment with sections: About the role? The description includes many parts. We need 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. Content: - General Parts Experienced Business Development Representative Food Service Industry Experience Strongly Preferred Denver, CO (Remote / Hybrid) | 2+ years outbound BDR / SDR experience required - About the role: maybe the first paragraph describing company and role. - Responsibilities: "What You'll Own" bullet list. - Requirements/Qualifications: "What Sets You Apart" and "❌ Not For You If" maybe. - Skills: maybe "Food Service Edge" etc. - Benefits: "What You'll Get" includes Structured coaching, focused market, room to sharpen skills, real path forward, Wellness Health Benefits, 401K with Company Match, Profit Sharing. - Pay: "Compensation — Denver, CO Market Base Salary: $70,000 – $80,000 (based on experience) Commission: Uncapped, tied to qualified meetings generated and pipeline sourced On-Target Earnings (OTE): $80,000 – $110,000+ for experienced performers Top performers consistently beat OTE." - Schedule: Not mentioned explicitly; maybe remote/hybrid location indicates schedule? Not given. So we should not create Schedule section if not present. We must not repeat job title as heading. Also not include Job ID etc. We must remove boilerplate: application instructions, cookie/navigation/legal/EEO etc. The posting includes "Interested? 👉 Apply with your résumé. Be ready to talk about how you've built pipeline — and if you've sold into food service, be ready to prove it fast. Go to www.generalparts.com/careers to apply". That's application instructions, should be removed. Also "We'll Ask You About ..." maybe also part of interview questions; could be considered part of requirements? Might be considered part of interview but not boilerplate. It's substantive: they will ask about background etc. Could be included under Requirements or maybe as a separate section? Probably we can include under Requirements or Qualifications. We must not invent or summarize away detail. Keep all substantive info. We need to use

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

    for prose. We need to decide which content goes where. Let's extract sections: About the role: maybe a paragraph describing the company and role: "General Parts has sold service, parts, and equipment to food service operators for 80+ years — CFESA-certified, built by people who already know this business. Food service buyers can spot a generic pitch in one sentence. This role isn't built for people who wing it." plus maybe the intro line: "Experienced Business Development Representative Food Service Industry Experience Strongly Preferred Denver, CO (Remote / Hybrid) | 2+ years outbound BDR / SDR experience required". That's more metadata but we can include in About the role. Responsibilities: "What You'll Own" bullet list: - Own outbound prospecting into food service accounts — restaurants, institutional operators, and distributors - Build pipeline through cold calls, email, and targeted outreach - Speak to real problems: downtime, cost, reliability - Book qualified meetings and hand off clean - Run a disciplined, organized process in Zoho Requirements/Qualifications: "What Sets You Apart" bullet list: - 2+ years as a BDR/SDR in an outbound environment — food service background strongly preferred - You understand food service buyer psychology: urgency, seasonality, margin pressure - You know the difference between a chain operator and an independent — and what a GPO relationship means - You treat CRM as a performance tool, not admin work - You own your pipeline and results. No excuses. Also "❌ Not For You If" bullet list (these are disqualifiers) could be part of Requirements as well. - You have no interest in learning how food service buyers think - You rely on scripts without personalizing them - You avoid the phone, or see CRM as busywork - You expect marketing or inbound leads to carry your pipeline - You want a quick steppingstone without mastering the role Skills: maybe "Food Service Edge" bullet: "You move to the front of the process. You don't need to have sold parts or services specifically — food service equipment, distribution, supplies, or technology all count." That's more like a qualification/skill. But we could combine Skills with Requirements. Benefits: "What You'll Get" bullet list: - Structured coaching from a manager who values discipline and development - A focused market — not a scattershot territory - Room to sharpen your skills fast, and a real path forward for top performers - Wellness Health Benefits, 401K with Company Match, Profit Sharing Pay: Compensation paragraph. Schedule: Not present, so omit. We must not create sections with filler like "commensurate with experience". We have actual numbers. We need to ensure we don't repeat job title as heading. So no heading like "Experienced Business Development Representative". We'll just have sections. Now produce HTML fragment. Structure:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
    • ...

    Requirements

    • ...
    • ...
    Maybe also separate "Skills" but we can incorporate into Requirements. But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have About the role, Responsibilities, Requirements (maybe combine Qualifications), Benefits, Pay. Could also have Skills separate if we have content. We have "Food Service Edge" which is a skill/knowledge. Could be under Skills. Let's create:

    About the role

    General Parts has sold service, parts, and equipment to food service operators for 80+ years — CFESA-certified, built by people who already know this business. Food service buyers can spot a generic pitch in one sentence. This role isn't built for people who wing it. Experienced Business Development Representative Food Service Industry Experience Strongly Preferred Denver, CO (Remote / Hybrid) | 2+ years outbound BDR / SDR experience required.

    Responsibilities

    • Own outbound prospecting into food service accounts — restaurants, institutional operators, and distributors
    • Build pipeline through cold calls, email, and targeted outreach
    • Speak to real problems: downtime, cost, reliability
    • Book qualified meetings and hand off clean
    • Run a disciplined, organized process in Zoho

    Requirements

    • 2+ years as a BDR/SDR in an outbound environment — food service background strongly preferred
    • Understand food service buyer psychology: urgency, seasonality, margin pressure
    • Know the difference between a chain operator and an independent — and what a GPO relationship means
    • Treat CRM as a performance tool, not admin work
    • Own your pipeline and results — no excuses

    Skills

    • Food service edge: experience selling into food service or working in the industry and moving into sales; familiarity with food service equipment, distribution, supplies, or technology

    Benefits

    • Structured coaching from a manager who values discipline and development
    • A focused market — not a scattershot territory
    • Room to sharpen your skills fast, and a real path forward for top performers
    • Wellness Health Benefits, 401K with Company Match, Profit Sharing

    Pay

    Compensation — Denver, CO Market Base Salary: $70,000 – $80,000 (based on experience). Commission: Uncapped, tied to qualified meetings generated and pipeline sourced. On-Target Earnings (OTE): $80,000 – $110,000+ for experienced performers. Top performers consistently beat OTE.

    We should not include Schedule. Check for any leftover boilerplate: removed application instructions, "Interested? 👉 Apply..." etc. Also removed "We'll Ask You About ..." maybe we could incorporate that into Requirements or Qualifications as a note but it's not a list; it's a set of interview questions. Could be considered part of Requirements but it's not a requirement; it's what they'll ask. Might be considered boilerplate? It's not exactly boilerplate; it's substantive about interview. But the instruction says to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "We'll Ask You About ..." is not application instructions; it's about interview. Could be kept. But we need to decide where to put it. Could be under Requirements as a note: maybe a paragraph. But we already have Requirements as a list; we could add a paragraph after the list:

    During the interview, you’ll be asked about your background in or around food service, how you build and manage pipeline, how you use a CRM day-to-day, how you handle rejection and stay consistent, and what feedback has actually made you better.

    That preserves info. Similarly, the "If you've sold into food service, you'll recognize the difference immediately. If you haven't, be ready to prove you can learn it fast." could be added as a paragraph under Requirements or Skills. Let's incorporate that. We'll add after Requirements list a paragraph. Now check for any other content: "Stop Scrolling If This Sounds Like You" and bullet points about "You've sold into food service — or worked in it and moved into salesYou know how to generate meetings, not just log activityYou stay consistent when prospects go quietYou take coaching and apply it fast". That's like a callout; could be part of About the role or Requirements. It's basically describing ideal candidate. Could be included in Requirements as bullet points. But we already have Requirements list; we could incorporate those points there. However we must not invent or summarize away detail; we need to preserve all substantive information. So we should include those points as well. Let's extract that block: "You've sold into food service — or worked in it and moved into sales You know how to generate meetings, not just log activity You stay consistent when prospects go quiet You take coaching and apply it fast" That's four bullet points. We can add them to Requirements or maybe a separate section like "Ideal Candidate". But we only have prescribed headings; we could add them under Requirements as additional bullets. Similarly "Food Service Edge: You move to the front of the process. You don't need to have sold parts or services specifically — food service equipment, distribution, supplies, or technology all count." That's a skill. We already have Skills bullet. Now also "What Sets You Apart" we already captured. Now "❌ Not For You If" we captured. Now "What You'll Get" we captured. Now "Compensation" we captured. Now "Interested? 👉 Apply..." removed. Now "We'll Ask You About ..." we added. Now "If you've sold into food service, you'll recognize the difference immediately. If you haven't, be ready to prove you can learn it fast." we can add as a paragraph under Requirements or Skills. Let's add under Requirements as a paragraph. Now ensure we didn't miss any substantive info: The line

Similar jobs