The Real Problem With Writing This Job Description
Most Business Development Executive Job Description templates you find online are copy-pasted garbage written by HR people who have never actually sold anything or opened a new account. They list responsibilities like "build and maintain client relationships" and "identify business opportunities" — which sounds impressive until you read it three dozen times in a row and realize it tells you absolutely nothing about what the person will actually do on a Tuesday afternoon. I spent years hiring BD executives across two different companies, and the ones who actually performed shared one thing: we'd given them a clearly scoped role. The ones who failed or left within a year almost always had a vague JD that made them spend three months figuring out whether they were supposed to be inside sales, account management, or operations.
Business Development Executive Job Description
Writing this document isn't about making the role sound appealing, though that matters for attracting candidates. The real purpose is defining the actual territory — who they hunt, what they sell, through which channels, with what support, and what success looks like at 90 days versus 12 months. Here's how to actually do it without producing another generic template nobody reads. Start with the day-to-day, not the headline responsibilities. A BD executive role that involves outbound prospecting through cold calls and LinkedIn outreach is fundamentally different from one built around partner referrals and inbound leads. I once posted a role that blended both into a single ambiguous posting and got applicants who were either aggressive closers uncomfortable with nurturing existing partnerships or softer relationship builders who froze when asked to cold prospect. We spent six weeks re-posting before realizing the JD itself was the problem.
The fix was separating the two tracks. We ended up writing two distinct JDs — one focused on new business development with quotas and cold outreach expectations, and another for business development focused on channel partnerships and referral generation. The first filled in three weeks with solid candidates. The second took longer but the quality was immediately better because the people who applied understood exactly what they were signing up for.
Get the Full Details
What to Include When You Write It
The core sections you need are pretty straightforward, though most postings skip the ones that actually help good candidates self-select in or out. Role overview. Two or three sentences max. State what the business does, what segment this role serves, and the primary objective. Avoid words like "dynamic," "fast-paced," and "highly motivated." Day-to-day responsibilities. Be specific about activity volume and methods. "Generate an average of 40 qualified outreach contacts per week" is more useful than "identify and pursue new business opportunities." If there's an expected conversion rate or quota, state the range. Candidates filter themselves out faster when they see the actual numbers.
Qualifications. Separate the must-haves from the nice-to-haves. I've seen JDs list seven "requirements" that were actually preferences, which inflated applicant quality scores on paper while producing zero actual competence in the interviews. Pick three non-negotiable skills and three things you'd prefer but can train. For a BD executive role, the non-negotiables are usually something like a track record in outbound pipeline building, comfort with CRM tools, and the ability to navigate multi-stakeholder sales cycles. Compensation structure. This is the section most companies skimp on, and it's the reason high-performing candidates ghost you before the first interview. Base salary, commission structure, OTE range, and how often payouts are reviewed — lay it out. You don't need to state exact figures, but giving a realistic band like "base $65,000–$75,000 with OTE $110,000–$135,000" saves everyone time. Career trajectory. Tell candidates where this role leads. The best BD executives treat every job as a stepping stone. If there's no clear path to senior BD or a general management role, say so. Lying about advancement prospects gets you someone who leaves after six months once they realize the ceiling is lower than advertised.
What Most People Get Wrong
The biggest mistake is conflating business development with sales. A BD executive isn't necessarily closing deals. In many organizations, the role is about opening doors, building pipelines, and handing qualified opportunities to account executives who close. In others, it's full-cycle selling from prospecting to signature. Your JD needs to make this clear, because candidates will walk into interviews expecting one thing and day one delivering the other. Another common error is writing the JD as if it's a job posting you're putting on a board. It's not. It's an internal alignment document first and a recruitment tool second. If your sales leadership, the hiring manager, and the candidate aren't aligned on what this role does, the JD will look fine on paper and still produce bad hires. I learned this the hard way when a VP of Sales asked me to post a BD executive role focused on enterprise accounts. The JD looked solid. We hired someone with a strong enterprise background. Three months in, it turned out the VP's definition of "enterprise" meant deals under $50K with five-month cycles, while the candidate came from a world of six-figure deals with eight-month cycles. The JD didn't capture the actual deal profile, so we wasted three months and had to redo the hire.
A Working Example
Here's a structure that actually works in practice. This is simplified, but it covers the ground most JDs miss. Role: Business Development Executive — Mid-Market Outbound We are a B2B SaaS company selling workflow automation software to companies with 200 to 2,000 employees. This role is responsible for building and managing a full outbound pipeline in the mid-market segment, with a secondary focus on nurturing inbound leads that come through our website and events.
You will generate 40 to 50 new contact conversations per week through cold calling, LinkedIn outreach, and targeted email campaigns. Approximately 30% of those conversations will advance to a discovery call. Discovery calls will be handed to a senior account executive for presentation and close, though you will remain involved through contract negotiation and onboarding handoff. Your quarterly quota is measured in qualified opportunities delivered to the AE team, not closed revenue. You should expect to deliver 12 to 18 qualified opportunities per quarter at a target conversion rate of 35% to discovery. Required experience:
At least two years of outbound business development or sales development in a B2B environment. Experience with Salesforce or HubSpot. A demonstrated ability to work through rejection and maintain activity volume over sustained periods. Familiarity with the SaaS or technology sector is preferred but not required. Compensation: Base salary $60,000 to $72,000. Commission structured at 8% of quarterly quota attainment with accelerators above 110%. Total OTE range $95,000 to $130,000. Quarterly reviews with performance-based adjustments. This format gives candidates enough detail to evaluate themselves honestly and gives your hiring team a baseline for scoring interviews.
Where This Approach Breaks Down
Writing a precise JD like this assumes you already understand your own sales motion well enough to describe it. That's not always the case, especially in smaller companies where the BD function hasn't been standardized yet. If you're hiring your first BD executive and you can't yet articulate the ideal daily activity or realistic quota, a detailed JD will just look like you're guessing. In that situation, it's better to post a shorter, more exploratory JD and use the interview process to calibrate. Tell candidates upfront that the role is still being refined and you're looking for someone who can help shape it. You'll attract a different type of candidate — more entrepreneurial, less rigid — but you'll also get honest feedback on whether your expectations are realistic. There's also a limitation worth noting: overly specific JDs can deter strong candidates who feel they don't meet every qualification. The 40-to-50 contacts-per-week expectation might scare off someone who's capable but used to a slower, more relationship-driven cadence. I've seen this happen more than once, where a candidate with excellent industry connections passed because they assumed the role was pure grind. The workaround is stating the expected activity range while explicitly noting that flexibility exists based on territory and season.
One final thing that most people forget: the JD should mention what you provide, not just what you expect. A BD executive without marketing collateral, a working product demo, and a responsive internal team is just a person making cold calls with no ammunition. List the tools, the training period, and the internal support they'll have. It makes the role more attractive and it filters out candidates who would quit in the first month because they felt abandoned.
