Business Development Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate like EEO, legal, scam warning, duplicated lines, application instructions. Also remove navigation/cookie etc. We need to parse the posting. Key sections: - About the role: The first paragraph(s) describing role: "The Business Development Manager (BDM) is responsible for accelerating profitable growth across RWS's Linguistic Validation business..." etc. Also "About Regulated Industries" maybe part of About the role? Could be separate but we can include under About the role. - Responsibilities: The "Key Responsibilities" section with subheadings: Job Overview, Business Development & Revenue Growth, Customer Discovery & Consultative Selling, Executive Relationship Management, Market & Industry Leadership, Collaboration & Commercial Excellence. We need to list duties as

• . Should we keep subheadings? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. So we can have a

    Responsibilities

    then a
    with list items capturing each duty. We must preserve all substantive info, not lose detail. So we need to extract each bullet point from the responsibilities section. Let's extract responsibilities content: From posting: "Key Responsibilities Job Overview Business Development & Revenue Growth Identify, pursue, and secure new business opportunities aligned with RWS strategic priorities. Develop and execute strategic account plans to expand existing relationships and penetrate new business units within target accounts. Build and maintain strategic relationships across pharmaceutical companies, biotechnology organizations, CROs, eCOA technology providers, and related clinical research organizations. Develop and maintain a robust sales pipeline while consistently achieving revenue, profitability, and growth objectives. Apply a metrics-driven approach to pipeline management, forecasting accuracy, and sales performance. Identify opportunities to cross-sell and upsell the broader RWS portfolio, maximizing customer value and long-term account growth. Lead commercial negotiations, proposals, pricing discussions, and contract negotiations in partnership with Legal, Finance, and Commercial leadership. Consistently achieve or exceed assigned revenue, pipeline, and profitability targets." "Customer Discovery & Consultative Selling Lead meaningful discovery conversations to uncover both explicit and underlying customer needs. Translate customer challenges into tailored, value-driven solutions leveraging the full RWS Linguistic Validation and Digital Health portfolio. Position RWS as a strategic partner by articulating measurable business outcomes and return on investment. Demonstrate agility by adapting solutions in real time based on customer feedback, industry trends, and evolving priorities. Develop compelling business cases and presentations that differentiate RWS from competitors. Guide customers through complex buying journeys while aligning solutions with their strategic business objectives." "Executive Relationship Management Build trusted relationships with executive sponsors, procurement leaders, clinical operations teams, digital innovation leaders, and strategic decision-makers. Develop multi-level stakeholder engagement strategies that strengthen long-term partnerships. Influence decision-making through consultative leadership and industry expertise. Act as a trusted advisor by sharing market insights, best practices, and strategic recommendations throughout the customer lifecycle." "Market & Industry Leadership Maintain a strong understanding of the pharmaceutical, biotechnology, CRO, and eCOA technology landscape. Demonstrate expertise in Linguistic Validation, Clinical Outcome Assessments (COAs), eCOA, Digital Health, localization, and global clinical trial processes. Stay informed on regulatory requirements, industry trends, competitive intelligence, and customer challenges impacting clinical development. Maintain awareness of AI-enabled technologies, automation, and digital transformation trends relevant to Life Sciences. Use market intelligence to proactively identify opportunities and shape customer strategies." "Collaboration & Commercial Excellence Lead cross-functional deal teams comprising Solution Consultants, Delivery, Operations, Product, Marketing, Quality, and Subject Matter Experts. Collaborate closely with operational teams to ensure a seamless transition from sales through implementation and delivery. Contribute to the development of sales methodologies, messaging, playbooks, and commercial best practices. Share market intelligence, customer insights, and sales best practices across the broader commercial organization. Foster a collaborative culture that supports customer success and continuous improvement." We need to convert each sentence into list items? Probably each bullet point can be a sentence. We'll create
    • for each distinct duty. Now Requirements: The posting includes "Core Competencies" list: Consultative Selling, Strategic Account Planning, Executive Presence, Commercial Negotiation, Customer Discovery, Business Storytelling, Financial & Commercial Acumen, Strategic Thinking, Relationship Building, Active Listening, Problem Solving, Adaptability & Resilience, Cross-functional Leadership, Analytical & Data-driven Decision Making, Curiosity & Continuous Learning, Results Orientation. Also "Required Skills & Experience" list: Demonstrated success in Business Development, Enterprise Sales, Strategic Account Management, or similar customer-facing commercial roles. Proven track record of consultative, solution-based selling within complex B2B environments. Experience managing long, multi-stakeholder sales cycles involving executive-level decision-makers. Strong executive communication, presentation, and influencing skills. Experience negotiating commercial agreements and managing strategic customer relationships. Ability to navigate complex matrix organizations while influencing without direct authority. Strong commercial and financial acumen, including the ability to articulate customer value and return on investment. Experience using Salesforce (preferred) or similar CRM platforms to manage pipeline, forecasting, and customer engagement. Highly organized with excellent planning, prioritization, and time management skills. "Preferred Experience" list: Experience selling into pharmaceutical companies, biotechnology organizations, Contract Research Organizations (CROs), or eCOA technology providers. Experience selling Linguistic Validation, Clinical Outcome Assessments (COAs), eCOA, localization, Digital Health, clinical technologies, SaaS, or other technology-enabled services. Understanding of global clinical development, patient-facing technologies, and regulated research environments. Established relationships within the Life Sciences ecosystem. Familiarity with strategic sales methodologies such as MEDDICC, Challenger, Miller Heiman, SPIN Selling, or equivalent. Also "Key Performance Indicators (KPIs)" maybe could be considered Requirements? But KPI is more about performance metrics; could be placed under Requirements or maybe separate but we only have set headings. Could include under Requirements as part of performance expectations. However the instruction: include a section ONLY when posting has real specific content for it. KPIs are specific content; but we don't have a heading for KPIs in allowed list. Could we put them under Requirements? Probably yes, as they are expectations. But we must not invent headings. We'll include KPI items under Requirements as list items. Also "Success Profile" is prose; could be part of About the role or Requirements? It's more description of ideal candidate; could be under Requirements or maybe under About the role? I'd put under Requirements as it's about candidate profile. Now Qualifications: Not explicitly separate; maybe we can treat Required Skills & Experience as Qualifications. But we have both Requirements and Qualifications headings allowed. We need to decide what goes where. Typically Requirements = mandatory skills/experience; Qualifications = education, certifications etc. The posting does not mention education or certifications. So we might omit Qualifications section if no specific content. But we have Required Skills & Experience and Preferred Experience; those could be Requirements (mandatory) and maybe Qualifications (preferred). However the instruction: include a section ONLY when posting has real specific content for it. We have content for Required Skills & Experience (mandatory) and Preferred Experience (preferred). Could split: Requirements = Required Skills & Experience; Qualifications = Preferred Experience. Or we could combine under Requirements and omit Qualifications. But we have both headings allowed; we need to decide based on content. Since there is no explicit education/qualification, maybe we skip Qualifications. However we have "Preferred Experience" which could be considered Qualifications. I'd treat Required Skills & Experience as Requirements, and Preferred Experience as Qualifications. That seems logical. Skills: Could be separate section for skills like "Core Competencies". That could be Skills section. So we will have Skills heading with list of core competencies. Benefits: The posting includes "Benefits Amazing benefits! (Seriously!) Generous paid time off package, starting at 25 days per year (10 sick and 15 vacation), plus company holidays, birthday day off, paid volunteer time, and 100% paid parental leave. 401(k) Retirement plan with company match. Company-wide agile work policy with flexible work arrangements. Opportunities for training, professional development, and personal growth." We'll put that as
      • items. Pay: The posting includes "Base Pay $100,000 - $120,000 / year Actual rate of pay may vary based on factors including, but not limited to: position offered, location, education, training, and/or experience. Total compensation may also include variable incentives, bonuses, benefits, and/or other perks, as outlined in any formal offer made." We'll include that as

        maybe with details. Schedule: Not mentioned explicitly. There's "Company-wide agile work policy with flexible work arrangements." That could be considered schedule/flexibility. But we need specific schedule content; not given. Could treat as Schedule section with that info. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible work arrangements, which is schedule-related. So we can include Schedule section with that detail. Location: Not a heading we have; we could fold into a short

        under About the role or maybe under Responsibilities? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. Location is minor metadata; we can include a short

        maybe under About the role or at top. We'll include a

        after the role description maybe. We must not include boilerplate like EEO, legal, scam warning, recruitment agencies, Covid Vaccination, etc. Remove those. Now produce HTML fragment. Structure:

        About the role

        [description]

        Location: Candidates must reside in State advertised to be considered Arizona, California, Colorado, Connecticut, Florida, Georgia, Iowa, Illinois, Kansas, Massachusetts, Maryland, Maine, Michigan, Missouri, North Carolina New Jersey, Ohio, Oregon, Pennsylvania, Rhode Island, South Carolina, Tennessee, Texas, Virginia, Washington, Wisconsin.

        But location list is long; we can keep as is. Then

        Responsibilities

        • Identify, pursue, and secure new business opportunities aligned with RWS strategic priorities.
        • Develop and execute strategic account plans to expand existing relationships and penetrate new business units within target accounts.
        • Build and maintain strategic relationships across pharmaceutical companies, biotechnology organizations, CROs, eCOA technology providers, and related clinical research organizations.
        • Develop and maintain a robust sales pipeline while consistently achieving revenue, profitability, and growth objectives.
        • Apply a metrics-driven approach to pipeline management, forecasting accuracy, and sales performance.
        • Identify opportunities to cross-sell and upsell the broader RWS portfolio, maximizing customer value and long-term account growth.
        • Lead commercial negotiations, proposals, pricing discussions, and contract negotiations in partnership with Legal, Finance, and Commercial leadership.
        • Consistently achieve or exceed assigned revenue, pipeline, and profitability targets.
        • Lead meaningful discovery conversations to uncover both explicit and underlying customer needs.
        • Translate customer challenges into tailored, value-driven solutions leveraging the full RWS Linguistic Validation and Digital Health portfolio.
        • Position RWS as a strategic partner by articulating measurable business outcomes and return on investment.
        • Demonstrate agility by adapting solutions in real time based on customer feedback, industry trends, and evolving priorities.
        • Develop compelling business cases and presentations that differentiate RWS