Director / Senior Director, Clinical Solutions (Business Development) - Enterprise, US
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we must map content to those headings. We have "About the company" not in list; maybe we can treat as "About the role"? Actually "About the company" is separate. The allowed headings list includes "About the role". There's no "About the company". Should we include it? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we have content about company, role, who we're looking for, responsibilities, requirements, nice-to-haves, what we offer, why join us. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit Pay or Schedule info. So we should not create those sections. Benefits we have: "What We Offer" includes competitive base salary and uncapped commission, opportunity to own relationships, shape strategy, grow into leadership, comprehensive private health coverage, hybrid work model, company events, MacBook, pet-friendly office. Those are benefits. So we can create a Benefits section.
Responsibilities: we have "Key Responsibilities" list.
Requirements: we have "Requirements" with must-haves and nice-to-haves. Could split into Requirements and Qualifications? The allowed headings include Requirements and Qualifications. We could put must-haves under Requirements, nice-to-haves under Qualifications. Or combine. We'll follow: Requirements for must-haves, Qualifications for nice-to-haves.
Skills: maybe we can extract skills from responsibilities? But we have no explicit skills list. Could omit Skills section if no specific content.
About the role: we have "About the role" paragraph.
We also have "About the company" paragraph. Not in allowed headings; maybe we can treat as part of About the role? But better to include as a section? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect only those headings. However, we have company info that is substantive; we could include it under a heading like "About the company" but that's not in list. Might be okay but risk. Safer to include as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. But we have content about company, role, who we're looking for, responsibilities, requirements, nice-to-haves, what we offer, why join us. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit Pay or Schedule info. So we should not create those sections. Benefits we have: "What We Offer" includes competitive base salary and uncapped commission, opportunity to own relationships, shape strategy, grow into leadership, comprehensive private health coverage, hybrid work model, company events, MacBook, pet-friendly office. Those are benefits. So we can create a Benefits section.
Responsibilities: we have "Key Responsibilities" list.
Requirements: we have "Requirements" with must-haves and nice-to-haves. Could split into Requirements and Qualifications? The allowed headings include Requirements and Qualifications. We could put must-haves under Requirements, nice-to-haves under Qualifications. Or combine. We'll follow: Requirements for must-haves, Qualifications for nice-to-haves.
Skills: maybe we can extract skills from responsibilities? But we have no explicit skills list. Could omit Skills section if no specific content.
About the role: we have "About the role" paragraph.
We also have "About the company" paragraph. Not in allowed headings; maybe we can treat as part of About the role? But better to include as a section? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect only those headings. However, we have company info that is substantive; we could include it under a heading like "About the company" but that's not in list. Might be okay but risk. Safer to include as a
without heading? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other headings, but they gave examples. I'd include About the company as a as well, but it's not in examples. Might be considered okay. However they said "Prefer a few substantive sections over many thin ones." Could combine company and role into About the role? But they said "do NOT repeat the job title as a heading (the page already shows it)". Not about company.
I'll include About the company as a About the company. It's substantive.
Now structure:
About the company
About the company. It's substantive.
Now structure:
About the company
... (the paragraph)
About the role
... (the paragraph)
Responsibilities
- ... each responsibility
Requirements
- ... must-haves
Qualifications
- ... nice-to-haves
Benefits
- ... what we offer
- for any list of duties/requirements/benefits, and
for prose. So we can have prose paragraphs then lists. Thus:
Requirements
Who We're Looking For: A commercially sharp enterprise seller with deep credibility across the U.S. pharmaceutical and clinical technology ecosystem. Someone who understands clinical development and enterprise buying processes inside out, has an established network within large pharma, and knows how to navigate complex, multi-stakeholder sales cycles from initial engagement through enterprise-wide adoption.This person should be comfortable operating with full autonomy — owning a defined portfolio of strategic accounts, generating and developing their own pipeline, building relationships across clinical, technology, procurement, and executive leadership teams, and representing Biorce at the highest levels of the industry.
- 7+ years of experience in business development, enterprise sales, strategic accounts, or strategic partnerships within clinical technology, life sciences technology, pharmaceutical services, or a closely related sector.
- Deep understanding of clinical development and clinical trial processes, with a strong network across the U.S. pharmaceutical ecosystem.
- Demonstrated experience selling directly into large pharmaceutical organizations and navigating complex enterprise buying environments.
- Proven track record of closing large, strategic enterprise deals with significant contract values and long, multi-stakeholder sales cycles.
- Established relationships with senior and C-level stakeholders across large pharma, particularly within Clinical Development, Clinical Operations, R&D, Digital, Technology, or related functions.
- Ability to independently originate pipeline, penetrate complex strategic accounts, and build relationships beyond a single buyer or department.
- Strong commercial judgment and the ability to develop account strategies that lead to long-term, enterprise-wide partnerships.
- Entrepreneurial mindset with the ability to operate independently in a fast-paced, high-growth environment.
- Strong executive communication, negotiation, and presentation skills.
- Ability to explain complex technology and AI-driven solutions in simple, value-driven terms tied directly to enterprise business outcomes.
- Willingness to travel up to 50% across the U.S. and internationally for client engagements, industry events, and company offsites.
Qualifications
- Familiarity with AI-driven platforms in a clinical or drug development context.
- Experience selling clinical technology platforms into Top 20 or Top 50 pharmaceutical organizations.
- Previous experience expanding a strategic account from an initial use case or pilot into a broader enterprise partnership.
- . Benefits: combine "What We Offer" and "Why Join Us?" paragraphs. What We Offer paragraph: "Competitive base salary and uncapped commission structure.Opportunity to own and develop relationships with some of the world's largest pharmaceutical organizations.Opportunity to shape the enterprise commercial strategy of a fast-growing AI healthtech company expanding rapidly across the U.S.Opportunity to grow into a broader strategic or commercial leadership role as Biorce expands." Why Join Us? paragraph: "A dynamic work environment with an international team, where collaboration and diversity thrive.Work alongside top talent, united by a shared purpose and committed to making a real impact.Comprehensive private health coverage to ensure your physical and mental well-being.Hybrid work model offering flexibility to balance your professional and personal life.Company events to celebrate achievements and enjoy time together.Get equipped with a MacBook to enhance your productivity and work experience.Our office is pet-friendly! You'll likely be greeted by a few wagging tails upon arrival." We'll split into list items. Benefits list: - Competitive base salary and uncapped commission structure. - Opportunity to own and develop relationships with some of the world's largest pharmaceutical organizations. - Opportunity to shape the enterprise commercial strategy of