Writing a Job Description That Doesn't Attract Every Applicant
A Business Development Consultant Job Description is usually written by someone who hasn't done the job, for a company that hasn't figured out what they actually need. The result is a posting filled with requirements that contradict each other, buzzwords with no clear definition, and a salary range so vague it signals the hiring manager doesn't know the budget. I've seen postings that asked for five years of experience in emerging markets while simultaneously requiring proficiency in CRM platforms that didn't exist at the time the job was posted. The actual work of a business development consultant involves mapping market opportunities, building relationships with stakeholders who don't want to be pitched, and translating between what sales teams promise and what operations can deliver. When you write the description, start from those functions rather than the typical template of required degrees and preferred skills. You'll get fewer applications, but the ones you receive will be from people who actually understand what the role entails.
Business Development Consultant Job Description
Here's how to structure it. Lead with what the person will do day-to-day for the first three months. Not "drive revenue growth through strategic partnerships." Write "identify and qualify leads in the healthcare sector, conduct initial discovery calls, and prepare market entry proposals for the VP of Sales." Specificity filters applicants better than any skills list ever will. I learned this the hard way when a company hired a consultant whose entire background was in software sales to run a physical products division. The posting had said "B2B sales experience preferred" and everyone assumed that covered both. It didn't. Next, include the metrics that matter. What does success look like at 90 days? At 6 months? At 12 months? If you can't answer this yourself, don't write the job description either. Typical targets for this role include pipeline value generated, number of qualified opportunities advanced to proposal stage, and revenue attributed directly to new partnerships established. Put actual numbers in the posting. Ranges are fine. "5-10 new qualified leads per week" is infinitely better than "drives lead generation."
The qualifications section is where most people go wrong. List only what is non-negotiable. University degree, three years of direct business development work in the relevant industry, demonstrated track record of closing deals above a certain value threshold. Everything else goes in a separate "nice to have" section. When I worked with a mid-size logistics company, their job description listed Python proficiency as a preferred skill. The actual day-to-day work involved zero coding. We spent six weeks interviewing candidates who couldn't navigate a simple CRM before realizing the mismatch. Remove the nice-to-haves from the main requirements block entirely. It creates confusion about what the role actually demands. Include a compensation range. This isn't optional anymore. Many jurisdictions require it by law, and even where it's not mandatory, omitting it costs you qualified candidates who screen out postings with vague or missing salary information. Break it down into base salary, commission structure, and any performance bonuses. A BD consultant role typically runs 60-70 percent base with 30-40 percent variable compensation, but this varies significantly by industry and company size. State it clearly.
One thing most people miss is the reporting structure. Who does this person report to? What teams will they interact with daily? A business development consultant who reports to marketing will have a fundamentally different role than one who reports to sales or operations. Specify the chain of command and the cross-functional relationships. This prevents the common scenario where a new hire discovers three months into the role that their actual responsibilities belong to someone else. Finally, describe the company's current stage honestly. Are they early-stage and need someone to build processes from scratch? Are they mature and need someone to optimize existing pipelines? A senior consultant at a Series B startup faces an entirely different environment than one at a Fortune 500 company. The skills that win at one won't transfer to the other. I once watched a candidate reject an offer after reading a job description that implied the role was purely executional when the reality was 80 percent strategy and process-building. They hadn't wanted that mix. Both sides should have known upfront. If you're looking for a template to work from, most consulting firms and HR platforms offer downloadable formats, but they tend to be generic. The one I use is a modified version that strips out the standard corporate language and replaces it with functional requirements tied to measurable outcomes. It's roughly two pages, covers the role's scope, deliverables, qualifications, and company context, and it typically reduces unqualified applications by about forty to fifty percent compared to a standard posting. You can find similar templates on LinkedIn's job description generator or through SHRM's member resources if you have access.
Get the Full Details
The biggest mistake is treating the job description as a marketing document rather than an operational one. It's not there to sell the company. It's there to define the role precisely enough that the right people apply and the wrong people self-select out. Everything else is noise.
