Senior Director, Partner Strategy & Solutions for Commercialization/marketing

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Position Overview (could be About the role). Key Responsibilities (Responsibilities). Required Qualifications (Qualifications). Core Competencies (Skills). There's no explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title as heading. We need to include maybe a short paragraph for metadata? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a

with location etc. But we must preserve all substantive information. The location: Plano, Texas (US-TX), United States (US). Also maybe mention NTT DATA strives... but that's boilerplate? The first paragraph about inclusive etc might be considered boilerplate? It's not exactly boilerplate but could be considered generic. However we need to preserve all substantive information; but we can drop cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The first paragraph about inclusive etc is not boilerplate but maybe considered generic fluff. However it's part of the posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove generic fluff. But we should preserve all substantive information. The first paragraph is about wanting to be part of inclusive etc. Might be considered substantive? It's more like marketing. I'd keep it as a short paragraph under maybe an intro? But we have no heading for intro. Could just put a

after the metadata. We need to output only HTML fragment, no /. Use

for section headings. Use

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

  for prose. We need to decide what to list as

  • . For responsibilities, we have many bullet-like sentences but not explicitly bulleted. We could convert each sentence into
  • . However the instruction: "Use
    • for any list of duties/requirements/benefits". It doesn't say we must convert prose to list; but if it's a list, we should. The responsibilities section contains multiple distinct responsibilities each as a paragraph. Could treat each as list item. Similarly for qualifications: list of bullet-like statements. We'll convert to
      • . We need to preserve all substantive information; not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, core competencies, etc. Let's extract sections: - About the role: Could be Position Overview paragraph(s). We'll put that as

        under

        About the role

        . - Responsibilities: Key Responsibilities section includes multiple subheadings: Market and buyer definition, Offer commercialization and packaging, Go-to-market and launch planning, Seller and partner enablement, Cross-functional solution execution and governance, AI-enabled commercialization capability. Each has multiple sentences. We'll create a
        with
        • for each sentence? Might be too granular but okay. However we need to preserve all detail; splitting into sentences preserves detail. Could also keep each subheading as a
        • containing multiple sentences. But instruction: Use
          • for any list of duties/requirements/benefits. It doesn't forbid having paragraphs inside
          • . So we can make each responsibility area as a
          • with its prose. Thus:

            Responsibilities

            • Market and buyer definition: Work with business units, industry leaders, Partner Sales, Practices, partners, and client-facing teams to sharpen the target customer problem, buyer personas, buying triggers, use cases, target-account characteristics, and market context for assigned solutions. Validate that the offer is anchored in customer demand and a specific business outcome rather than in technology features alone. Translate solution capabilities into a differentiated market proposition that is relevant to executive buyers, business stakeholders, technical evaluators, and seller audiences. Identify competitive alternatives, substitute approaches, proof requirements, and messaging risks that affect positioning and launch readiness.
            • Offer commercialization and packaging: Lead development of complete partner-ready offer packages for assigned solutions, including offer narrative, customer problem, target buyer, use cases, business outcomes, NTT DATA value proposition, partner role, differentiation, delivery approach, proof points, qualification criteria, and target-account guidance. Convert complex technical and service components into a coherent offer architecture that sellers and clients can understand without losing accuracy or credibility. Coordinate development of seller-facing and client-facing assets such as solution briefs, pitch narratives, sales plays, discovery questions, qualification guides, talk tracks, executive messaging, use-case stories, objection handling, and supporting proof points. Work with Practice, delivery, finance, commercial, and partner stakeholders to incorporate appropriate commercial-model, pricing, investment, marketplace, or funding inputs without assuming ownership for functions that sit elsewhere. Ensure every asset communicates a consistent value proposition, partner story, differentiation, scope, maturity level, and call to action.
            • Go-to-market and launch planning: Develop the integrated launch plan for approved offers, including readiness criteria, target audiences, seller and partner activation, enablement, marketing dependencies, communications, target-account priorities, launch milestones, and feedback mechanisms. Coordinate across Marketing, Partner Sales, Partner Execution, business units, Practices, partner field organizations, and other contributors so launch activities are sequenced and mutually reinforcing. Establish launch-readiness gates and prevent premature activation when the offer, proof points, delivery model, enablement, partner alignment, or field support are insufficient. Define what must be true for an offer to move from pilot or initial launch to broader scale, including evidence thresholds, seller adoption, customer response, delivery confidence, and commercial traction. Support early launch execution and ensure lessons from sellers, partners, pursuits, and clients are converted quickly into revisions to the offer and activation approach.
            • Seller and partner enablement: Design enablement that equips Partner Sales Leaders and BU/Practice Sellers to recognize the opportunity, identify the right buyer, lead an effective first conversation, qualify fit, articulate business value, position NTT DATA and partner differentiation, and engage the correct specialists. Lead or coordinate seller-enablement sessions, launch briefings, office hours, playbook rollouts, and reinforcement mechanisms for assigned offers. Ensure sellers understand the AI and agentic components of approved solutions, including the customer value, practical use cases, qualification criteria, deployment considerations, and boundaries of what the offer can credibly promise. Create feedback loops with Partner Sales, business-unit sellers, partners, and early pursuits to identify where messaging, qualification, assets, solution scope, or enablement need improvement. Measure adoption of offer assets and enablement and recommend changes based on field usage and commercial outcomes.
            • Cross-functional solution execution and governance: Serve as the named Solution Development Lead for selected initiatives and contribute commercialization expertise from intake and ideation through development, ensuring marketability is considered before build decisions are locked. Work with technical solution leaders and Practices during development so requirements for proof points, buyer relevance, packaging, repeatability, and seller usability are addressed before launch. Convene and align contributors across business units, Practices, partners, Marketing, sales, delivery, Partner Sales, and Partner Execution around decisions, deliverables, owners, deadlines, and launch outcomes. Prepare or contribute to governance decisions concerning offer readiness, investment, launch timing, scale, correction, and retirement. Recommend holding, revising, or retiring solutions that cannot be converted into a differentiated, sellable, deliverable, and repeatable market offer.
            • AI-enabled commercialization capability: Maintain sufficient fluency in AI, generative AI, and agentic solutions to translate technical capabilities into accurate customer value propositions, seller narratives, use cases, and qualification guidance. Use large language models and generative-AI tools extensively to accelerate market research, competitive synthesis, offer development, messaging iteration, enablement content, launch planning, and feedback analysis while applying strong editorial and factual judgment. Partner with technical specialists to ensure external and seller-facing descriptions of AI and agentic capabilities accurately reflect architecture, maturity, governance, security, and deployment realities.
            - Requirements: The posting has "Required Qualifications". We'll treat that as Requirements? Actually they have separate sections: Required Qualifications and Core Competencies. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need both Requirements and Qualifications sections. The posting has "Required Qualifications" (list). That could go under Qualifications. And maybe "Core Competencies" under Skills. Requirements might be something else? There's no explicit "Requirements" separate; maybe we can treat "Required Qualifications" as Qualifications, and maybe we can put nothing under Requirements? But we should only include a section when posting has real specific content. If we don't have content for Requirements, we should omit it. However the instruction list includes Requirements as a possible heading; we can omit if no content. So we will have About the role, Responsibilities, Qualifications, Skills. Qualifications: list of bullet-like statements under "Required Qualifications". We'll convert each sentence to
          • . Let's extract: Required Qualifications: - Significant experience commercializing and launching technology, digital, AI-enabled, services, or industry solutions in enterprise markets. - Demonstrated success taking complex products, platforms, services, or solutions from development or validation through packaging, go-to-market preparation, seller enablement, launch, adoption, and scale. - Deep experience in product commercialization, offer management, product marketing, solution marketing, go-to-market strategy and execution, sales enablement, launch management, or a closely related field. - Strong understanding of enterprise buying motions, buyer personas, value propositions, competitive differentiation, sales plays, qualification, target-account strategy, partner co-sell motions, and field adoption. - Working knowledge of AI, generative AI, automation, and agentic technologies sufficient to explain business value accurately, collaborate with technical experts, and translate complex capabilities into market-facing propositions. - Hands-on proficiency using leading large language models and generative-AI tools for market research, synthesis, messaging development, content creation, prompt design, competitive analysis, enablement development, and quality validation. - Proven ability to lead complex cross-functional launches across product or solution teams, sales, marketing, delivery, partners, and executive stakeholders without direct authority over all contributors. - Strong commercial judgment and the ability to distinguish an interesting capability from a differentiated, repeatable, sellable, and deliverable offer. - Excellent executive communication, positioning, storytelling, facilitation, and written-content skills. - Experience in technology services and strategic technology-partner ecosystems strongly preferred. - Bachelor’s degree required; advanced degree or relevant product, marketing, business, or technology credentials preferred. We'll put each as
          • . Skills: Core Competencies list: - Product commercialization - Offer packaging and positioning - Go-to-market and launch leadership - Seller enablement - Commercial judgment - AI literacy and applied LLM fluency - Buyer and market orientation - Cross-functional influence - Executive communication and storytelling - Field-feedback synthesis We'll put each as
          • . Now we need to include location etc. We'll add a short

            after maybe before sections: "Location: Plano, Texas (US-TX), United States (US)." Also maybe include the introductory sentence about NTT DATA strives... but that's fluff; we could include as a

            but it's not substantive? Might be considered boilerplate? I'd keep it as a short paragraph: "NTT DATA strives to hire exceptional, innovative and passionate individuals who want to grow with us. If you want to be part of an inclusive, adaptable, and forward-thinking organization, apply now." However that's basically a call to apply; might be considered application instruction? It's not exactly instruction to apply but encourages. The instruction says remove application instructions. This is more of a marketing statement; but could be considered boilerplate. Safer to drop it. We'll keep only location. Thus output: