Director, Client Services – Life Sciences Practice Lead

We need to produce HTML fragment with sections: About the role? The posting includes Introduction, Your Role And Responsibilities, Preferred Education, Required Technical And Professional Expertise, Preferred Technical And Professional Experience etc. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those headings if content exists. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. So we need to extract content and map to appropriate sections. We have Introduction: description of IBM Consulting, culture, etc. That could be "About the role" or maybe "About the role" is appropriate. Could also be "About the role" includes overview. Then "Your Role And Responsibilities" -> Responsibilities section. Then "Preferred Education" -> Qualifications? Could be Qualifications. Then "Required Technical And Professional Expertise" -> Requirements? Or Skills? Might be Requirements. Then "Preferred Technical And Professional Experience" -> Skills? Or maybe also Requirements. We need to decide mapping. We have sections: About the role (intro), Responsibilities (role and responsibilities), Requirements (required technical and professional expertise), Qualifications (preferred education), Skills (preferred technical and professional experience). Benefits, Pay, Schedule not present, so omit. We must not create sections with filler. So only include those with content. We need to use

• for any list of duties/requirements/benefits. The posting includes bullet-like sentences but not explicit bullet list. We need to convert lists where appropriate. For responsibilities, we have many sentences describing duties; we could wrap each duty as
• . Similarly for requirements list. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details. We'll parse the text and produce HTML. Let's extract sections: Introduction paragraph(s): "A career in IBM Consulting is built on long-term client relationships and close collaboration worldwide. You’ll work with leading companies across industries, helping them shape their hybrid cloud and AI journeys. With support from our strategic partners, robust IBM technology, and Red Hat, you’ll have the tools to drive meaningful change and accelerate client impact. At IBM Consulting, curiosity fuels success. You’ll be encouraged to challenge the norm, explore new ideas, and create innovative solutions that deliver real results. Our culture of growth and empathy focuses on your long-term career development while valuing your unique skills and experiences." That's about the role. Your Role And Responsibilities: long paragraph describing two accountabilities, then details. We need to break into list items for duties. We'll produce

  About the role

  then

  intro paragraphs

  . Then

  Responsibilities

  then
  • ... each duty
  . Then

  Qualifications

  for Preferred Education: "Preferred Education Master's Degree". Also maybe Bachelor's degree requirement later under Required Technical And Professional Expertise? Actually Bachelor's degree appears under Required Technical And Professional Expertise at end: "Bachelor's degree in Business, Life Sciences, Computer Science, or an equivalent field." That's a requirement. So Qualifications could include both preferred and required education? But we have separate sections: Qualifications maybe for education; Requirements for experience/skills. We'll follow instruction: Use headings as given; we can decide. We have "Preferred Education Master's Degree". That's a qualification. We also have "Bachelor's degree in Business, Life Sciences, Computer Science, or an equivalent field." under Required Technical And Professional Expertise. That could be a requirement. We'll put education under Qualifications (preferred) and maybe also under Requirements? But to avoid duplication, we could include both in Qualifications: Preferred Education Master's Degree; also Bachelor's degree required. But the instruction says use headings only when posting has real specific content. We have both. We could create Qualifications section with both preferred and required education. Then Requirements section for Required Technical And Professional Expertise (excluding education bullet). Then Skills section for Preferred Technical And Professional Experience. Let's extract Required Technical And Professional Expertise list: - 10+ years in consulting or professional services with a track record of leading and growing client accounts, including 5+ years serving Life Sciences clients (pharma, biotech, medtech, diagnostics, or CRO). - Demonstrated P&L or portfolio ownership: you have owned revenue, margin, and utilization targets and hit them. - Executive presence and trusted relationships at the VP and C-level in Life Sciences organizations. - Working knowledge of the modern data stack and cloud data platforms, ideally Snowflake, and the ability to shape data, analytics, and AI programs even if you are not hands-on in the code. - Familiarity with regulated delivery in Life Sciences: GxP, 21 CFR Part 11, data integrity, and validation expectations. - Experience building and leading teams of consultants, engagement managers, and architects, including hiring and developing leaders. - Strong commercial skills: proposal and SOW development, pricing and margin management, negotiation, and escalation handling. - Proven ability to define a practice or segment strategy, including target sub-segments, priority accounts, and an offering portfolio, and to execute against a revenue and margin plan. - Track record of building and qualifying pipeline with sales leads and co-owning pursuit strategy, solutioning, and proposal quality on priority deals. - Experience serving as the escalation point for client and delivery issues across multiple accounts and workstreams. - Ability to assess team-to-client fit and distribute staffing and bandwidth across accounts and a shared bench. - Bachelor's degree in Business, Life Sciences, Computer Science, or an equivalent field. We'll treat the last as education but we already covered; maybe we keep it here as part of Requirements. Preferred Technical And Professional Experience list: - Partner Ecosystem Experience: Experience selling and delivering through partner ecosystems (Snowflake, IBM, or comparable hyperscaler and platform channels). - Life Sciences Domain Depth: Depth in one or more Life Sciences domains: clinical operations, drug safety and pharmacovigilance, commercial analytics, manufacturing and quality, or real-world data. - Offering Development: Experience packaging services into repeatable offerings or accelerators and taking them to market. - Practice Leadership: Prior practice, vertical, or industry leadership role at a consultancy or systems integrator. - Thought Leadership: Experience representing a practice through conference presence, partner events, and published content. - Regulated Delivery Methodology: Experience contributing to delivery methodology and sales playbooks for regulated industries. Now Responsibilities: need to extract duties from the long paragraph. Let's parse: "This role reports to the Global Head of Healthcare and Life Science, with travel to clients as needed. This Position Carries Two Accountabilities That Reinforce Each Other First, they lead the Life Sciences practice at Hakkoda, an IBM company, owning the segment’s strategy, offerings, pipeline health, talent, and reputation across pharma, biotech, medtech, diagnostics, CROs, and life sciences distribution. Second, they are a hands-on Client Services Director on our most strategic Life Sciences accounts: the primary representative of the delivery capabilities of Hakkoda, an IBM company to those clients and the executive accountable for growing them." Then description of ideal candidate (maybe part of responsibilities? but could be qualifications). However we already have qualifications separate. The paragraph after that: "The ideal candidate is an expert in their clients’ businesses, challenges, and goals, with established trusted relationships at the most senior client levels. They are fluent in how Life Sciences works: the R&D-to-commercial value chain, the regulatory environment (GxP, 21 CFR Part 11, data integrity, validation), the data domains that matter (clinical, safety, RWD/RWE, commercial, supply chain and manufacturing), and the business pressures behind them (pipeline productivity, launch performance, cost of quality, and the push to make AI usable in a regulated setting). They can sit across from a Head of Clinical Operations, a Chief Commercial Officer, a Head of Quality, or a CDO and be credible on their agenda, then translate that agenda into a data and AI program on Snowflake that Hakkoda, an IBM company can deliver." That seems more like qualifications/skills. But we already have those covered. Might be redundant. However we must preserve all substantive info; we could include that as part of Responsibilities or Qualifications. Since it's about ideal candidate, maybe better as Qualifications/Skills. But we already have qualifications (education) and skills (preferred experience). This paragraph is about expertise; could be part of Requirements (technical expertise). But we already have a list of required technical expertise. This paragraph adds more detail about fluency in Life Sciences works etc. Could be incorporated into Requirements as additional bullet points. But to avoid duplication, we could keep it as part of Requirements (maybe as bullet). However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include that info somewhere. We could add a subsection under Requirements for "Life Sciences expertise" etc. But we must not create filler sections. We can add bullet points under Requirements list. Thus we will expand Requirements list with items derived from that paragraph. Similarly, the later part about practice and accounts details are responsibilities. Let's extract responsibilities bullets: From "For the practice, the Director defines where Life Sciences plays and how it wins. They own the practice plan (target sub-segments, priority accounts, offerings, and the revenue and margin plan behind them), shape and package offerings around the questions Life Sciences leaders are actually funding, and build on existing accelerators such as Clinical Trial Operations, Pharmacovigilance Signal Management, Batch Release and Continued Process Verification, Commercial Launch Analytics, FDA AI Readiness and Continuous Compliance, and Trusted Research Environment. They turn delivered work into repeatable IP, set the practice’s stance on regulated delivery, and act as the Life Sciences face of Hakkoda, an IBM company to both go-to-market channels, IBM client partners and Snowflake account teams, so that sellers reach for us first. They build the Life Sciences bench, serve as the escalation point and quality bar for Life Sciences delivery across all accounts, and represent the practice externally through conferences, partner events, and published content." Then "On accounts, the Director personally leads a portfolio of strategic Life Sciences accounts. They consult on the best path forward to achieve the client’s strategic goals, build relationships from the primary point of contact through the C-suite, align with the client’s partner account teams (Snowflake, IBM, Sigma, Alation, Fivetran) on a shared account plan, and hold indirect responsibility for all delivery services on their portfolio. They pursue opportunities for additional services, review client margins against Finance targets, lead the pitch process on existing accounts, draft and negotiate SOWs and amendments, mentor Engagement Managers on account management, and serve as the point of escalation on client issues, from cross-workstream performance problems to SOW and SLA conversations. They handle difficult client and employee conversations directly, solve resourcing and personnel issues as they arise, keep client and employee retention high across every track, facilitate staffing across tracks and the broader HCLS bench, and make the business case for hires and promotions." Also earlier: "This role reports to the Global Head of Healthcare and Life Science, with travel to clients as needed." That's a responsibility. Thus we can create bullet list for responsibilities. Now we need to output HTML fragment only. We'll structure:

  About the role

  Intro paragraphs.

  Responsibilities

  • Reports to the Global Head of Healthcare and Life Science, with travel to clients as needed.
  • Lead the Life Sciences practice at Hakkoda, an IBM company, owning the segment’s strategy, offerings, pipeline health, talent, and reputation across pharma, biotech, medtech, diagnostics, CROs, and life sciences distribution.
  • Act as a hands‑on Client Services Director on the most strategic Life Sciences accounts, serving as the primary representative of Hakkoda’s delivery capabilities and the executive accountable for growing those accounts.
  • Define where Life Sciences plays and