Stop copying job descriptions from LinkedIn. Seriously.
You know the drill. You need to hire a BDR, so you open 15 tabs, find a template from a company 10x your size, and hit publish. Then you wonder why your inbox fills up with people who either want to “drive synergies” or have never made a cold call in their life.
Most business development job descriptions are bad. Not average. Bad.
They blur totally different jobs into one blob, bury the actual work under HR fluff, and leave candidates guessing whether they're applying for outbound prospecting, full-cycle sales, partnerships, or some cursed hybrid role invented in a budgeting meeting. That confusion is expensive. One guide on business development points out that role confusion between SDR/BDR work and strategic business development is common, and says 60% of BDR hires fail within 12 months when expectations are unclear.
That's not a hiring problem. That's a writing problem.
A strong JD tells the truth about the job. It names the scoreboard. It shows candidates where they'll spend their Tuesday, not just how “dynamic” your culture is. Done right, it filters out tourists and pulls in people who want the work.
Here are 8 field-tested business development job descriptions that do that job properly, from SDRs grinding top-of-funnel to partnerships leaders stitching together bigger bets.
This is the heavyweight role. If your business development job descriptions lump this person in with appointment setters, you're already off course.
A true AE or strategic Business Development Manager owns real revenue motion. They prospect when needed, run discovery, handle objections, coordinate stakeholders, negotiate terms, and close deals that justify everyone's salary. They are not glorified calendar managers.
In the U.S., the role carries weight in pay and expectations. Coursera's overview of the business development manager role puts median total pay at about $152,000 annually and notes that employers usually want a bachelor's degree plus three to five years of relevant experience. That should tell you something. This isn't an entry-level “hungry hustler” post with a vague promise of upside.
Spell out that this person owns the full sales cycle. Say whether they inherit pipeline, self-source part of it, or both. Name the deal environment too. Enterprise software, healthcare workflows, compliance-heavy finance tools, multi-department buying committees. Candidates need to know the terrain.
Also, be explicit about boundaries. Territory. Minimum deal size. Handoff rules. Procurement involvement. If your AE is expected to work closely with SDRs, write that. If they need to collaborate across time zones and sell asynchronously, write that too.
Practical rule: If a candidate can't tell whether the job is closing, qualifying, or account management after reading your post, your JD is the problem.
A few blunt recommendations:
If your team still confuses AE, BDM, SDR, and AM, fix that before you hire. Start with understanding sales team titles. It'll save you a month of interviewing the wrong people. Toot, toot.
Let's stop pretending this role is mysterious. It's outbound work. It's repetitive. It's rejection-heavy. And when written forthrightly, it attracts the right kind of person.
The biggest mistake in business development job descriptions is dressing SDR work up like strategic leadership. Candidates join expecting “growth strategy” and discover they're doing cold outreach all day. That mismatch burns people out fast and torches onboarding.
One industry roundup says 78% of SaaS companies now hire SDRs internationally to cut costs by 80% to 90%, yet many JDs still ignore remote-first collaboration, time zone execution, and cross-cultural communication. That's outdated thinking.
An SDR JD should say exactly how the rep creates pipeline. Cold email, calls, LinkedIn, inbound qualification, list building, CRM hygiene, follow-up discipline. If your team uses frameworks like MEDDIC or BANT, include them. If you expect heavy personalization, say that. If the rep is volume-driven, say that too.
Then tell the truth about daily rhythm. This role suits people who like a scoreboard. The best SDRs treat activity like training camp, not interpretive dance.
For anyone still mixing up these two roles, use this guide to SDR and BDR hiring. If your company wants smaller deals closed by the same person, that's not a pure SDR role anymore.
Here's the practical setup I'd use:
And yes, the outreach system matters. If you want reps to perform, give them a process, not motivational wallpaper. This guide for sales teams on email outreach is useful context for what the work looks like in practice.
You're not hiring “energy.” You're hiring someone who can hear “not interested” before lunch and still write a decent follow-up at 2 p.m.
This role is the Swiss Army knife. Handy. Flexible. Also dangerous if you write it lazily.
Inside sales specialists often cover inbound leads, warm outbound, early discovery, demos, follow-ups, and smaller closings. That's why founders love them. One salary report for Business Development Specialists in the U.S. puts the median average salary at $74,706 annually, with a range from $48,000 at the bottom 10% to $112,000 at the top 10%. So no, this is not your cheap catch-all hire.
Where companies go wrong is writing this role like a dumping ground. Prospect, demo, close, support customers, update CRM, write copy, maybe water the office plant. That's not versatility. That's management avoidance.
A useful inside sales JD defines where authority starts and stops. Can they run demos solo? Can they discount? Do they own renewals? Are they expected to source pipeline or mainly convert existing interest? Put it all in writing.
This role works especially well for SMB software, service firms, and startups that can't justify separate SDR and AE layers yet. Think of a team selling straightforward SaaS into small operations teams, or a support platform with steady inbound demand where buyers still need a human nudge before signing.
A few things worth putting directly in the JD:
Inside sales can be a fantastic role for someone who likes people and process. It is not a refuge for someone who couldn't hack pure outbound and doesn't want quota pressure. Write that part plainly and save yourself some awkward interviews.
This one is misunderstood because founders think “partnerships” means sending a few friendly emails and slapping logos on a slide. Cute idea. Doesn't work.
A channel partner manager gains advantage through resellers, agencies, implementation partners, consultants, and regional allies who can take your product into markets you can't cover directly. It's part relationship management, part enablement, part commercial diplomacy. If you hire a pure hunter for this role, they'll annoy every partner in your ecosystem by week two.
Good business development job descriptions for partner managers focus on ecosystem building. Recruiting the right partners. Onboarding them properly. Running joint go-to-market motion. Protecting deal registration. Solving friction before the partner drifts toward a competitor with a shinier portal and better enablement.
Don't describe this role as “owning a partner book” and call it a day. Write the mechanics. Partner sourcing, onboarding, training, co-marketing coordination, pipeline reviews, conflict resolution, and performance management. If your partnerships are vertical-specific, say so. A manager for fintech referral partners is not interchangeable with someone who's only worked agency ecosystems.
Use real examples in your own thinking. Salesforce built a massive ecosystem around implementation partners and integrators. HubSpot's agency partner model is another obvious one. Stripe and Slack also show how partnerships can extend reach and deepen product stickiness without adding a direct seller in every niche.
Partnerships fail when both sides expect magic and nobody owns enablement.
I'd also bake these expectations into the JD:
If your candidate sounds like a direct rep who got bored and wanted a nicer title, keep moving.
Some of the best pipeline I've ever seen didn't start with a cold call. It started with a smart operator who knew how to turn intent into qualified conversations.
This role sits at the messy but profitable edge between marketing and sales. Not brand fluff. Not “awareness.” Pipeline. If your Growth Marketing Manager can't explain how campaigns become sales conversations, you've hired a content tourist with dashboard access.
Use this role when your product benefits from education, repeatable funnels, and conversion discipline. Webinars, landing pages, nurture sequences, product-led handoffs, paid campaigns, gated assets. The channel matters less than whether the person can connect spend, messaging, and lead quality.
A sharp JD should tie this role to pipeline contribution, lead quality, and sales alignment. Make it clear they'll work with SDRs or AEs, not toss leads over the fence and disappear into attribution debates.
And yes, the role needs analytical rigor. The European guide to business development roles notes that success in these positions often requires hard skills like CRM proficiency and project management, alongside soft skills like active listening and planning, within a broad compensation range that varies by experience level in Europe according to emlyon's business development manager overview. Different title, same lesson. Growth work is commercial work.
If you're building this function, I'd write the JD around these realities:
If you're not sure how this role fits with the rest of your org, map it against essential marketing roles for 2026. Better to define overlap early than let sales and marketing spend six months politely blaming each other.
ABM is not “personalized marketing” because you changed the company name in an email opener. That's lazy outreach wearing a blazer.
A real ABM specialist works a defined list of target accounts with coordinated touches across marketing and sales. Specific accounts. Specific stakeholders. Specific value props. If your deal sizes justify custom attention, this role can be lethal in a good way.
The trick is discipline. ABM falls apart when teams get greedy and target too many accounts too early, or when sales wants meetings tomorrow while marketing is still building the campaign spine.
Start by saying this role partners tightly with sales. Weekly account reviews. Shared account plans. Joint messaging. If that sounds annoying, don't hire ABM. You need alignment, not vibes.
A good ABM job description also needs research muscle. Deep account mapping. Stakeholder context. Industry pain points. Offer customization. Multi-touch coordination. This isn't mass lead gen with better branding. It's selective pressure.
Use examples candidates will recognize. Salesforce and HubSpot have both used account-focused plays to land larger enterprise opportunities. Marketo built much of its category identity around this discipline. More recent SaaS teams like Notion, Figma, and Airtable have all benefited from focused enterprise motions where generic nurture tracks would be too blunt.
I'd keep the JD anchored around a few essential elements:
“ABM” without sales alignment is just expensive pretending.
If your company can't agree on what a qualified account looks like, fix that before posting the role. Otherwise you'll hire someone smart and set them up to lose.
Now we're in actual strategic business development. Not list building. Not appointment setting. Deals that change distribution, product reach, market access, or long-term strategic advantage.
Business development job descriptions usually become nonsense. Everything turns into “identify opportunities” and “build relationships,” which tells serious candidates exactly nothing. A strong JD for this role should read like a commercial mandate, not a motivational poster.
In the U.S., a salary snapshot from Maryville lists the median for Business Development Managers at about $73,000 in July 2020, with the bottom 10% around $45,000 and the top 10% reaching $122,000. The spread matters. This title gets used for wildly different jobs. Your JD has to narrow the field.
If the role handles integrations, white-label deals, referral agreements, market entry partnerships, or acquisition conversations, say so. Also say who they negotiate with. Product leaders, legal teams, executives, channel heads. The level of counterpart tells candidates a lot about how senior the role is.
This role also needs operational backbone. LinkedIn's hiring guide notes that a core responsibility for a Business Development Manager is performing high-level industry research and actively tracking business-related invoices. That second part gets skipped all the time. Big-picture dealmakers still need commercial discipline.
I'd write this role with these elements front and center:
For a live example of the level, this RemoteFast director role shows the kind of senior framing candidates expect when the job is strategic.
Here's the role too many companies underwrite like support and then act shocked when expansion doesn't happen.
An expansion-focused CSM is revenue talent. Different rhythm from new logo sales, yes. Softer touch, usually. But the job still requires commercial instinct, account judgment, and the ability to spot where a customer can grow into more product, more seats, more teams, or a broader rollout.
This role becomes especially important once you've sold enough logos that renewals and expansion can outgrow net-new contribution. If your business development job descriptions ignore post-sale revenue, you're leaving money on the table and pretending retention is someone else's department.
The JD should say this person owns commercial conversations inside existing accounts. Not just onboarding, issue escalation, and “customer happiness.” Spell out that they identify adoption gaps, monitor usage signals, map stakeholders, and coordinate upsell or cross-sell motions when the fit is real.
That last bit matters. Expansion CSMs should create value, not pressure accounts into awkward add-ons. Good ones understand the customer's business well enough to connect new use cases to actual outcomes.
A strong JD for this role should include:
The best examples are easy to picture. A design team starts on Figma, then product and QA adopt it too. A HubSpot customer expands from one hub into several. A Slack deployment begins in one department and spreads across the company. None of that happens by accident. Someone sees the signal, builds the case, and guides the expansion.
| Role | Implementation complexity | Resource requirements | Expected outcomes | Ideal use cases | Key advantages |
|---|---|---|---|---|---|
| Enterprise Account Executive (AE) / Business Development Manager | High, long sales cycles, multi-stakeholder coordination | Senior hire, robust sales ops, CRM, forecasting tools, ramp time | Large ACVs, predictable recurring revenue, strategic account growth | Complex enterprise deals, high-ACV SaaS, territories needing close relationships | High revenue per rep, builds case studies and deep customer relationships |
| Sales Development Representative (SDR) / Business Development Representative (BDR) | Low–Medium, repeatable playbooks and high activity volume | SDR manager, engagement platforms, outreach templates; can be offshore | Top-of-funnel pipeline, qualified meetings, scalable lead generation | Early-stage funnel building, outbound prospecting, high-volume outreach | Cost-effective, clear KPIs, scalable quickly |
| Inside Sales Specialist / Sales Associate | Medium, hybrid processes for prospecting and closing | Versatile rep, CRM, demo tools, modest support | Faster deal velocity for SMBs, reduced handoff delays | SMBs, mid-market, startups with limited headcount | Cost-efficient end-to-end ownership, faster decisions |
| Channel Partner Manager / Business Development Partner Manager | Medium–High, partner programs and ecosystem coordination | Enablement resources, co-marketing funds, partner portals, training | Scalable revenue via partners, lower CAC, market entry through partners | International expansion, reseller networks, agency partnerships | Leverage partners' reach, scalable distribution, lower acquisition costs |
| Growth Marketing Manager / Marketing-Sourced Pipeline Builder | Medium–High, experimentation and analytics driven | Analytics stack, ad spend, landing pages, marketing automation | Measurable pipeline, improved CAC and conversion rates | Scaling demand gen, paid acquisition, funnel optimization | Direct ROI attribution, scalable spend, conversion improvements |
| Account-Based Marketing (ABM) Specialist / Account Manager | High, intense sales-marketing alignment and customization | ABM tools, intent data, custom content, cross-functional coordination | Higher win rates, larger ACV, compressed sales cycles for target accounts | Mid-market and enterprise targeting high-value accounts | Precision targeting, higher close rates, better forecasting |
| Strategic Partnerships Manager / Business Development Director | High, complex negotiations, legal and product integration | Senior BD lead, legal/product resources, executive sponsorship | Multi-million revenue opportunities, strategic market access | Platform integrations, white-labels, joint ventures, ecosystem deals | Strategic leverage, long-term moats, accelerated market entry |
| Customer Success Manager (CSM) – Expansion Focus | Medium, requires data, playbooks, and stakeholder mapping | Product telemetry, customer analytics, renewal/expansion playbooks | Increased NRR, upsells/cross-sells, reduced churn | Retention and expansion motions, increasing customer LTV | Low CAC growth, predictable revenue, strong customer advocacy |
A great job description isn't paperwork. It's positioning.
Every candidate reads your JD and makes a snap judgment about whether your company knows what it's doing. If the post is vague, bloated, or stuffed with corporate confetti, strong operators assume the role is a mess. They move on. The people who stay are often the ones least bothered by ambiguity, which is a polite way of saying they may not know what good looks like either.
That's why strong business development job descriptions do three jobs at once. They define the work. They set the scoreboard. They sell the opportunity to the right person without overselling the role to the wrong one.
The practical framework is simple. Name the actual revenue motion. State who the role works with. Say what success looks like in behavior and outcomes. Clarify whether the job is outbound prospecting, full-cycle closing, partnership building, or expansion inside existing accounts. If there's travel, say it. If there's async work across time zones, say it. If the role requires industry research, CRM discipline, and comfort with invoices or contract details, put that in black and white.
And stop trying to cram three jobs into one because you're feeling “lean.” Lean is useful. Confused is expensive.
One more thing. A JD isn't just a filter for candidates. It's a mirror for your own leadership team. If your head of sales, founder, and hiring manager can't agree on what the person will do, posting faster won't save you. You need alignment before recruiting, not after the third mis-hire.
If you want a broader operating lens for that, this practical framework for business development is a useful companion to the hiring side.
And yes, if building the engine in-house feels like mortgaging your office ping-pong table, using a specialist option can make sense. hireSDR.io is one route for teams that need remote SDR and BDR hiring support with pre-vetted candidates and cross-border hiring infrastructure. That's not magic. It's just often faster than duct-taping a hiring process together at midnight.
Write the JD like it matters, because it does. It's your first sales pitch to the person who'll carry your number.
If you need SDRs or BDRs without turning your leadership team into a part-time recruiting committee, take a look at hireSDR.io. It gives you access to pre-vetted, English-fluent remote sales talent, so you can spend less time sorting resumes and more time building pipeline.
You know the scene. Your VP Sales is reviewing resumes between forecast calls. Your best AE is “helping” with interviews instead of closing deals. Your...
The worst advice in sales is “don't take it personally.” Of course you take it personally. You're a human being calling strangers, getting ignored, brushed...
Monday morning. A founder opens the campaign report, sees a miserable reply count, and blames the market, the list, or the rep. Usually the problem...
Tell us who you need. We'll have pre-vetted candidates in your inbox within 72 hours. No commitment until you hire.