Director, IT Business Partner - Neuromodulation

We need to output HTML fragment with sections: About the role? The posting includes intro about company, then description of role. We should not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We have responsibilities (Key Responsibilities etc). We have qualifications (Required Qualifications And Experience). We have maybe Skills? Not explicit separate. Could combine responsibilities and qualifications. We have maybe "Measures of Success" could be part of responsibilities? But we can create a section "Responsibilities" covering the detailed responsibilities. "Qualifications" covering required qualifications. Possibly "Skills" not explicit separate; we could omit. Benefits, Pay, Schedule not present, so omit. We need to preserve all substantive information, not invent. Remove boilerplate like EEO etc. There's none. We need to use

• for any list of duties/requirements/benefits. So we need to convert the responsibilities bullet points into list items. The responsibilities are given in paragraphs with headings like "Strategic Business Partnership and Domain Immersion", "Strategy, Roadmap and Portfolio Leadership", etc. Those could be subheadings? But we only allowed

  for section headings. Could we use

  for those subheadings? The instruction: 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

  for section headings. Likely we should only use

  for those top-level sections. For subheadings we could use

  or just

  . Safer to keep within

  and maybe . But we need to preserve content. Could format each responsibility area as

  inside the Responsibilities section. Not prohibited. The instruction only says use

  for section headings (list). It doesn't forbid other heading levels. So we can use

  for sub-sections. Similarly for qualifications we can list bullet points. We need to output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  ... intro paragraph about company and role summary ...

  Then

  Responsibilities

  • Strategic Business Partnership and Domain Immersion: ...
  ... etc. But we need to ensure each bullet corresponds to a duty. Could break each responsibility area into separate
  • . Provide the description. Similarly

    Qualifications

    • Bachelor’s degree in information technology, business, engineering, life sciences or a related field, or equivalent experience; advanced degree preferred.
    • Typically, 12 or more years of progressive technology, digital, data, product, consulting or business transformation experience, including significant leadership responsibility.
    ... etc. We need to preserve all details: include mention of Salesforce, SAP COE, BI, AI, etc. Those are in responsibilities. Let's extract responsibilities text: From posting: Role Mandate (list): - Build a dedicated, credible and visible IT partnership with the Epilepsy and OSA leadership teams. - Develop deep subject matter expertise and translate business strategy into a multi-year digital, data and technology roadmap. - Provide strong business-facing leadership for Salesforce as the key commercial platform for Epilepsy and OSA, while coordinating relevant SAP priorities with the SAP COE. - Create clear accountability for business outcomes, adoption and realized value, not only project delivery. - Provide practical BI reporting and simple AI enablement so the partnership can demonstrate value quickly while using enterprise standards and guardrails. - Bring one integrated view of demand, priorities, investment, risk, dependencies and performance across both organizations. Key Responsibilities sections: Strategic Business Partnership and Domain Immersion - Serve as the primary IT relationship owner and trusted advisor to the Epilepsy and OSA presidents and their leadership teams. - Maintain a regular presence in business operating reviews, strategy discussions, portfolio reviews and field or customer-facing forums where appropriate. - Build working knowledge of commercial, clinical, medical, market access, patient support, finance, supply chain, quality, regulatory and operational processes relevant to each organization. - Proactively identify growth, productivity, experience, compliance and decision-support opportunities where technology, data or AI can create value. - Communicate enterprise IT strategy, capabilities, constraints and tradeoffs in clear business language, while representing business context and priorities within IT. Strategy, Roadmap and Portfolio Leadership - Co-create and maintain business-aligned technology, data and AI roadmaps for Epilepsy and OSA, with explicit outcomes, investment assumptions, dependencies and measures of success. - Partner with the Salesforce COE to develop and maintain platform roadmaps that support the commercial vision and strategy of Epilepsy and OSA, including the OSA business roadmap, and translate business needs into clear Salesforce capability priorities. - Serve as the senior business-facing partner for Salesforce demand, adoption and value realization, ensuring alignment with enterprise architecture, data, security, release and lifecycle standards. - Partner with the SAP COE to identify, prioritize and align relevant SAP capabilities, integrations and roadmap dependencies with Epilepsy and OSA business priorities. - Translate strategic priorities into a transparent demand portfolio and facilitate fact-based prioritization across growth, operational, regulatory, risk and foundational needs. - Develop investment cases that define the business problem, expected benefits, total cost, organizational impact, adoption requirements and value-realization plan. - Ensure local or business-specific needs are addressed through enterprise platforms and standards wherever practical, minimizing fragmentation and avoidable technical debt. - Provide executive-level portfolio reporting and escalate decisions, risks or resource conflicts early. Outcome Ownership and Value Realization - Jointly define outcome measures with business sponsors before work begins and maintain accountability from concept through adoption and benefit realization. - Establish baselines, targets and review cadences for approved initiatives; surface variance and agree corrective actions with business and IT owners. - Partner with business leaders on process ownership, change leadership, communications, training and adoption. - Conduct post-implementation value reviews and apply lessons to future investment and delivery decisions. - Use business outcomes, stakeholder trust, adoption and portfolio health as the primary indicators of BRM effectiveness. Business Intelligence and Practical AI Enablement - Lead or coordinate development of priority BI reports, dashboards and decision-support products that address clearly defined business questions. - Create a disciplined intake and prioritization approach for reporting needs, including ownership of definitions, data quality, adoption and report rationalization. - Facilitate rapid discovery, prototyping and delivery of simple AI use cases within approved enterprise tools and governance, such as knowledge assistance, summarization, workflow support and low-complexity productivity use cases. - Define success criteria and validate value before scaling AI use cases; transition solutions requiring material integration, sensitive data, advanced models or production support to the appropriate enterprise teams. - Promote data literacy, responsible AI practices and reuse of governed data products, common metrics and enterprise capabilities. Delivery Orchestration and Service Performance - Act as the accountable business-facing integrator across applications, data, infrastructure, cybersecurity, architecture, service management and delivery teams. - Maintain strong working relationships with the Salesforce and SAP Centers of Excellence, clarifying business priorities, shared accountabilities, decision rights, delivery dependencies and measures of value. - Match business needs to the right delivery path, including product teams, projects, enhancements, analytics, automation or service improvement. - Confirm clear executive sponsorship, product or process ownership, decision rights and acceptance criteria for material initiatives. - Monitor delivery commitments, business readiness, service experience and recurring pain points; coordinate recovery plans when outcomes are at risk. - Maintain a closed feedback loop so recurring incidents and service issues inform roadmap and investment decisions. Governance, Risk and Financial Stewardship - Embed cybersecurity, privacy, quality, regulatory, records, data and architecture requirements early in solution shaping and decision-making. - Balance speed, innovation and local business needs with enterprise risk appetite, standards and lifecycle sustainability. - Support annual planning, forecasting and financial transparency for the Epilepsy and OSA technology portfolios. - Provide visibility to spend, capacity, vendor commitments, benefits and tradeoffs; recommend actions to improve value and simplify the portfolio. - Participate in vendor evaluation and performance management in partnership with procurement, legal and relevant IT owners. Leadership and Capability Building - Lead, coach and develop business partnership, BI reporting and practical AI capabilities aligned to business priorities and enterprise standards. - Create clear role boundaries and ways of working across BRM, product, platform, project, architecture, data, security and service teams. - Build a culture of curiosity, accountability, collaboration, customer orientation and measurable value delivery. - Influence effectively across matrixed teams and mobilize resources without relying solely on direct authority. - Represent the Epilepsy and OSA perspectives within the IT Leadership Team and contribute to enterprise technology strategy and operating-model improvements. Decision Rights and Accountability - Owns the quality and cadence of the strategic IT relationship with Epilepsy and OSA leadership. - Owns business-facing technology, data and AI roadmaps and the consolidated demand view for the two organizations. - Recommends portfolio priorities and investment tradeoffs; agreed governance bodies retain final funding and architecture decisions. - Approves progression of small BI and AI use cases within delegated authority and enterprise guardrails; routes higher-risk or scaled solutions to enterprise review. - Is accountable for transparent outcome tracking and value-realization reviews, jointly with business sponsors and solution owners. Measures of Success - Strategic partnership: Stakeholder confidence; early engagement in business planning; depth of business knowledge; quality of executive dialogue. - Business value: Documented outcomes and realized benefits; adoption; measurable improvement in priority business processes or decisions. - Portfolio effectiveness: Roadmap alignment; prioritization quality; delivery predictability; timely resolution of risks and dependencies. - BI and AI impact: Use and usefulness of priority reports; cycle time from question to insight; validated value from simple AI use cases; responsible transition of scaled solutions. - Service experience: Reduction in recurring friction; improved transparency and responsiveness; effective connection between service issues and roadmap actions. - Enterprise alignment: Reuse of enterprise platforms and data; compliance with security, privacy, quality, architecture and AI guardrails; controlled technical debt. - Leadership: Engagement and development of talent; strong cross-functional collaboration; clear accountability across the operating model. We could include Measures of Success as a subsection under Responsibilities or separate section? Could be its own section but not in allowed list; but we could still include as

    Measures of Success

    though not in list; 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 suggests those are typical. Safer to keep only those headings. So we could incorporate Measures of Success into Responsibilities as a subsection. Similarly Decision Rights and Accountability could be part of Responsibilities. Thus Responsibilities section will be long but okay. Now Qualifications: Required Qualifications And Experience - Bachelor’s degree in information technology, business, engineering, life sciences or a related field, or equivalent experience; advanced degree preferred. - Typically, 12 or more years of progressive technology, digital, data, product, consulting or business transformation experience, including significant leadership responsibility. - Demonstrated success partnering with senior business executives to shape strategy, prioritize investments and deliver measurable outcomes. - Experience leading a complex portfolio across multiple functions in a global, matrixed organization. - Working knowledge of commercial, customer, finance, supply chain and regulated-product processes; medical device, life sciences or another regulated industry strongly preferred. - Experience with business intelligence, analytics, data products and practical AI or automation use cases, including the ability to distinguish prototypes from solutions requiring enterprise engineering and controls. - Strong working knowledge of and demo (cut off). The text ends abruptly: "Strong working knowledge of and demo". Likely missing continuation: maybe "Strong working knowledge of and demo...". We must preserve as is? The posting cut off; we should not invent. We'll