Digital Assets Product Manager, Associate Director

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. We need to parse the posting. Let's extract sections: - About the role: The initial paragraph about DTCC, mission, etc. Could be considered "About the role". The posting starts with "Are you ready to make an impact at DTCC? ..." then description of DTCC Digital Assets. That's about the role/company. We'll put that in

About the role

with

paragraphs. - Responsibilities: The "Your Primary Responsibilities" list. That's a list of duties. We'll use

Responsibilities

with

• items. - Requirements: There's a "Qualifications" section with bullet-like paragraphs. Also "Talents Needed For Success" maybe skills. The posting has "Qualifications" heading (actually bold). Then list of qualifications. Then "Talents Needed For Success" which could be Skills. We'll treat "Qualifications" as Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications and Skills separate if content exists. The posting has "Qualifications" (with bullet points) and "Talents Needed For Success" (skills). So we can map: - Requirements: maybe the qualifications bullet list? But they also have a separate "Qualifications" heading. Actually they have "Qualifications" heading then bullet list. Then "Talents Needed For Success" heading then bullet list. So we could treat "Qualifications" as Requirements? But they also have a separate "Qualifications" heading allowed. The instruction says we can use those headings. So we could have:

  Qualifications

  with the bullet list under Qualifications.

  Skills

  with the Talents Needed For Success list. We might also have a "Requirements" section if we want to capture something else like minimum years etc. But the qualifications list already includes minimum 7 years etc. So we can skip a separate Requirements heading to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we can combine qualifications and skills? But they are distinct. We could have Qualifications (education, experience) and Skills (talents). That seems fine. - Benefits: The posting has "Pay And Benefits" section with bullet points: Competitive compensation, health insurance, pension, PTO, flexible hybrid model. So we can have

  Benefits

  with list items. Also Pay: they mention salary range indicative etc. That's pay info. We could have

  Pay

  with that paragraph. However they said only create Pay/Schedule/Benefits sections if posting actually states them. Pay is stated: "The salary range is indicative for roles at the same level within DTCC across all US locations. Actual salary is determined based on the role, location, individual experience, skills, and other considerations." That's pay info. So we can include Pay section. - Schedule: They mention flexible hybrid model of three days onsite and two days remote, with onsite attendance on Tuesdays, Wednesdays, and a third day unique to each team or employee. That's schedule info. So we can include Schedule section. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not include empty sections. Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement and accommodation request. We must remove that. Also remove duplicated lines (maybe none). Also remove "NOTE: The Primary Responsibilities of this role are not limited to the details above." That's a note but it's substantive? It's a note that responsibilities not limited. Might be considered boilerplate? It's a note but it's part of responsibilities. We could keep it as a sentence after responsibilities list. It's not a list item but we can include as a

  after the list. Also we need to not repeat the job title as heading. The job title is "Associate Director of Product Management within DTCC Digital Assets". Not to be used as heading. Now craft HTML. We'll start with

  About the role

  then paragraphs. We need to preserve all substantive information from the about section: The initial paragraphs: "Are you ready to make an impact at DTCC? Do you want to work on innovative projects, collaborate with a dynamic and supportive team, and receive investment in your professional development? At DTCC, we are at the forefront of innovation in the financial markets. We are committed to helping our employees grow and succeed. We believe that you have the skills and drive to make a real impact. We foster a thriving internal community and are committed to creating a workplace that looks like the world that we serve. DTCC Digital Assets is at the forefront of driving institutional adoption of digital assets technology with a steadfast commitment to innovation anchored in security and stability. As the financial services industry’s trusted technology partner, we pride ourselves on empowering a globally interconnected and efficient ecosystem. Our mission is to provide secure and compliant infrastructure for digital assets, enabling financial institutions to unlock the full potential of blockchain technology." We'll put that in

  maybe split into multiple paragraphs but we can keep as one

  with sentences. Now Responsibilities: list items from "Your Primary Responsibilities". We'll capture each bullet line. Let's extract them: - Personally own and execute product deliverables across multiple digital-asset workstreams, including requirements, functional and technical documentation, user stories, and acceptance criteria - Serve as a key day-to-day contact for clients, internal partners, and cross-functional stakeholders, maintaining productive relationships and clear communication regarding progress, changes, timelines, and decisions - Coordinate activity across Product, Technology, Architecture, Operations, Risk, Legal, and Compliance to maintain alignment and momentum across connected workstreams - Manage the intake of incoming requests, questions, and escalations, ensuring that each has a clear owner, response path, priority, and target date - Monitor progress across workstreams and maintain disciplined follow-through on open items, dependencies, approvals, and commitments - Maintain a consolidated, current view of product status, risks, decisions, dependencies, and implementation readiness - Provide the Product Director with timely, decision-ready updates, highlighting matters that require leadership awareness, input, or escalation - Identify emerging risks, requirements gaps, and competing priorities early, and recommend practical options and next steps - Prepare stakeholder communications, status reports, meeting materials, and follow-up summaries, and coordinate action items through resolution - Partner with Engineering and Architecture to clarify requirements, validate feasibility, resolve open questions, and support timely delivery - Confirm that protocol-specific solutions remain aligned with the broader product architecture, operating model, and roadmap - Coordinate product validation, user acceptance testing, launch readiness, and post-launch enhancements - Create capacity across the product organization by taking ownership of cross-workstream coordination, stakeholder communication, monitoring, and follow-through - Maintain knowledge of blockchain infrastructure, smart contracts, wallets, tokenization, and institutional digital-asset trends After that there is a note: "**NOTE: The Primary Responsibilities of this role are not limited to the details above.**" We'll include as a

  after the list. Now Qualifications: bullet list under "Qualifications". Let's extract: - Minimum 7 years of experience in product management, product ownership, business analysis, or technology delivery within financial services, fintech, digital assets, or a related environment - Bachelor’s degree in Computer Science, Engineering, Information Systems, Finance (preferred), or a related field, or equivalent experience - Experience with tokenized securities, digital custody, cryptocurrency, blockchain-enabled financial products, or related institutional digital-asset capabilities - Proven experience driving complex, cross-functional products or workstreams from requirements through implementation and launch in a hands-on individual-contributor capacity - Experience serving as a key contact for clients and stakeholders, including relationship management, status reporting, and executive-level communication - Demonstrated ability to organize, prioritize, monitor, and advance a high volume of concurrent requests, dependencies, and action items - Strong understanding of blockchain technology, smart contracts, wallets, distributed systems, or digital-asset infrastructure - Experience translating strategic objectives and client needs into product plans, requirements, user stories, and acceptance criteria - Experience coordinating product validation, user acceptance testing, launch readiness, and production implementation - Knowledge of financial markets, including custody, clearing, collateral, margin, payments, investment management, broker-dealer, exchange, or post-trade operations Now Skills/Talents Needed For Success: bullet list: - A product mindset that connects client needs, technical capabilities, controls, and business outcomes - Exceptional organization and follow-through, with the discipline to advance open items and close loops proactively - Strong relationship-building skills and confidence engaging clients, executives, and cross-functional partners - Ability to influence outcomes, establish accountability, and align partners collaboratively without formal authority - Ability to translate complex blockchain concepts for technical, business, and executive audiences - Sound judgment when balancing product priorities, technical feasibility, delivery risk, and market needs - Comfort navigating ambiguity, resolving dependencies, and driving timely decisions - Clear, concise communication that provides stakeholders and leadership with the appropriate level of visibility - Strong ownership, collaboration, and execution discipline, combined with a willingness to contribute directly to the work Now Benefits: bullet list under "Pay And Benefits". Let's extract: - Competitive compensation, including base pay and annual incentive. - Comprehensive health and life insurance and well-being benefits, based on location. - Pension and retirement benefits. - Paid Time Off, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being. - DTCC offers a flexible hybrid model of three days onsite and two days remote, with onsite attendance on Tuesdays, Wednesdays, and a third day unique to each team or employee. But note that the hybrid model is schedule info; we might split schedule separate. However the benefits section includes that line. We'll keep it in Benefits? But we also have Schedule section. To avoid duplication, we could keep hybrid model under Schedule, and benefits list without that line. However the instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we remove that line from Benefits, we lose it unless we put it in Schedule. So we can put hybrid model in Schedule section, and keep other benefits in Benefits. Thus Benefits list: - Competitive compensation, including base pay and annual incentive. - Comprehensive health and life insurance and well-being benefits, based on location. - Pension and retirement benefits. - Paid Time Off, Personal/Family Care, and other leaves of absence when needed to support your physical, financial, and emotional well-being. Now Pay section: The paragraph about salary range indicative etc. Also maybe mention "Competitive compensation" already in benefits but pay section is separate. We'll include the paragraph: "The salary range is indicative for roles at the same level within DTCC across all US locations. Actual salary is determined based on the role, location, individual experience, skills, and other considerations." Now Schedule section: The hybrid model description: "DTCC offers a flexible hybrid model of three days onsite and two days remote, with onsite attendance on Tuesdays, Wednesdays, and a third day unique to each team or employee." We'll put that as a

  under Schedule. Now ensure we don't include any boilerplate like EEO statement. Remove that. Now produce HTML fragment. We'll need to wrap each section in <