Director, Technical Program Management

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. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. Use

for headings,

• for lists,

  for prose. We need to parse the posting. Let's extract sections: - About the role: description of role, why it exists, what you will own, etc. Could be a prose paragraph(s). We'll put in

  . - Responsibilities: list of duties: timely and predictable delivery, building trust, run programs, portfolio dependency, product operating rhythm, building TPM team, etc. Could be bullet list. - Requirements: "What we're looking for": 8+ years in technical program management, with 3+ leading TPM teams or functions, ideally including founding one. Delivery leadership in regulated financial environment, technically credible with platform engineering, demonstrated experience with at least one of: M&A integration, legal-entity restructuring, or large multi-party partner migrations. Operates through influence, writing-first operator, crypto/digital-asset domain experience a plus, regulated-fintech delivery scar tissue matters more. - Qualifications: maybe overlapping with requirements. Could treat as same? But we need separate sections only if content distinct. The posting has "What we're looking for" which is requirements. There's also "What will make you fail here" maybe not a section. Could treat as "Skills"? Might list skills: technical program management, influence, writing-first, etc. But we can combine. - Benefits: list: Competitive base salary, bonus and stock options; 100% company paid health insurance for employee, partner and dependents; Up to 4% 401k company match; Paid parental leave, Paid vacation; Free custom lunches, dinners and snacks; Computer equipment and workplace furniture to suit your needs; Great colleagues and inspiring startup environment. - Pay: "Pay Transparency Notice: Depending upon your leveling the compensation for this role averages between $200,000 - $230,000 USD base salary. Equity, an annual performance bonus and the benefits outlined above are also a part of this role's package." - Schedule: "This role will require being full-time onsite at our New York City (40 Wall St) office to support collaborative team dynamics and innovative problem-solving." So schedule: full-time onsite. We must not include filler like "commensurate with experience". Not present. We need to ensure we don't duplicate content. Also need to avoid repeating same bullet points. Let's craft HTML. Structure:

  About the role

  ... prose ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...
  Maybe also Skills? Could combine with Requirements. But we can have Skills separate if we have distinct list: technical program management, influence, writing-first, etc. However the posting already includes those in requirements. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. So we can combine Requirements and Skills into one section maybe "Requirements & Skills". But headings must be exactly from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit sections not needed. So we can have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Qualifications and Skills could be omitted if content covered elsewhere. But we need to ensure we don't lose any substantive info. The "What we're looking for" includes experience, leadership, technical credibility, etc. That's requirements. The "What will make you fail here" maybe not needed. The "Why Join BitGo?" is more about culture, could be part of About the role or maybe Benefits? But we already have Benefits separate. Could include some of that in About the role. We need to preserve all substantive info: The description of why role exists, what you will own, building trust, portfolio dependency, product operating rhythm, TPM team, success metrics, who you will partner with, etc. That's responsibilities. The "What we're looking for" is requirements. The "Why Join BitGo?" includes values, etc. Could be part of About the role or maybe a separate section like "About BitGo"? Not in allowed headings. Could incorporate into About the role. Benefits list we have. Pay: salary range. Schedule: full-time onsite. We must not include boilerplate like "For more information, visit www.bitgo.com." That's navigation? It's not boilerplate but maybe considered info; but it's not substantive to role? It's just company website. Could drop as it's not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The website link is not navigation but could be considered navigation? It's just a link. Might be safe to drop. Also "BitGo (NYSE: BTGO) is the digital asset infrastructure company..." That's company description; could be part of About the role? Might be considered boilerplate? It's substantive about company but not role. Might keep in About the role as context. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the company description? It's about BitGo, not the role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Does that include company overview? It's part of posting. Likely yes we should keep it. But we can incorporate into About the role section as a brief intro. We must not repeat job title as heading. No job title given explicitly; we can ignore. Let's craft. About the role: combine company description and role purpose. Paragraph: BitGo (NYSE: BTGO) is the digital asset infrastructure company delivering custody, wallets, staking, trading, financing, stablecoins, and settlement services from regulated cold storage. Since 2013, BitGo has focused on accelerating the transition of the financial system to a digital asset economy. BitGo maintains a global presence and multiple regulated entities, including BitGo Bank & Trust, National Association, the first federally chartered digital asset trust bank owned by a publicly traded company. Today, BitGo serves thousands of institutions, including many of the industry's top brands, financial institutions, exchanges, and platforms, and millions of investors worldwide. This role will require being full-time onsite at our New York City (40 Wall St) office to support collaborative team dynamics and innovative problem-solving. Why this role exists: BitGo's product is the foundation of the crypto industry globally... etc. We'll need to include the "Why this role exists" paragraph and what you will own etc. Might be long; we can put as prose. But we also have Responsibilities section separate; we could put the detailed duties there. So About the role could be a brief overview: company description and role purpose (why this role exists). Then Responsibilities list the specific duties. Let's extract "Why this role exists" paragraph: "Why this role exists BitGo's product is the foundation of the crypto industry globally. Our products and services are used by a breadth of client types worldwide: exchanges, banks, fintechs, asset managers, protocols, corporates, and governments. Much of the industry's infrastructure ultimately runs on or intersects with our platform. Delivery at that scale, across that many client types and jurisdictions, is executed by single-threaded PM owners. The individual workstreams are owned. What is not owned is the connective tissue between them: delivery operating rhythm, cross-team dependencies, regulatory submission pipelines, audit-driven remediation programs, etc that cut across product, engineering, compliance, legal, and finance. You will join as the first program manager for R&D and build the Technical Program Management function from scratch within your first year. This is not a process-improvement role. It is an execution-risk role at a public company where missed delivery on regulated commitments has audit, examiner, and investor consequences." We can include that as prose in About the role. Then Responsibilities: list of what you will own etc. From "What you will own": Timely and predictable delivery of product. This is the mandate everything else serves. You own delivery integrity across the product portfolio: dates that mean something, cross-team and cross-entity programs (acquisition integrations, legal-entity restructurings, partner and vendor migrations) executed end-to-end, and early escalation the moment a plan and a commitment diverge. When BitGo says something ships, it ships. Building trust between product and our regulatory, compliance, legal, finance, and audit partners. Run the programs where product delivery and control exposure intersect: new-product regulatory review pipelines with fixed examiner deadlines, remediation of audit findings where the fix is a product build, and delivery against commitments made to regulators. These partner teams need to trust that product's plans are real and product needs to trust that review clocks are predictable; you are the person who makes both true, and who forces conflicts between remediation timelines and exposure windows into explicit decisions rather than letting them ride. Portfolio dependency and capacity integrity. Maintain the single source of truth for where resources are allocated, which programs must land when, and what is at risk. Surface contradictions, such as committed goals with unstaffed critical-path dependencies, duplicate ownership, or cross-team dependencies that live in nobody's plan, before they surface as quarter-end misses. Build a credible picture of keep-the-lights-on load so real capacity is known, not guessed. The product operating rhythm. Run the execution-review cadence for the product org: initiative status that is current and honest, launch readiness that commercial can sell against, and a working blocker-escalation path with SLAs. You make status cheap to produce and impossible to fudge. The TPM team. You start as the first program manager for R&D, hands-on, running the highest-exposure programs yourself, and build out the function within a year, hiring 1–2 TPMs against proven need. Set the bar for what program management means here: outcome-accountable, technically fluent, and light-touch on teams that are already delivering. Then "What success looks like in the first two quarters": Every regulated-delivery program has a dated plan reconciled against its external deadline, with gaps escalated in writing. There should be no compliance commitment tracked in a spreadsheet nobody owns. Committed goals and staffing are reconciled: zero commitments with unstaffed critical-path dependencies that leadership hasn't explicitly accepted. One integration or entity program demonstrably run end-to-end through your operating model. Product leads report the coordination overhead went down, not up. If the org experiences TPM as a reporting tax, the function has failed regardless of the dashboards. Then "Who you will partner with": list of partners. We can incorporate those as responsibilities bullets. Now Requirements: "What we're looking for" bullet list. Let's extract: - 8+ years in technical program management, with 3+ leading TPM teams or functions, ideally including founding one. - Delivery leadership in a regulated financial environment: you have run programs with examiner deadlines, audit findings, SOX-adjacent controls, or material-weakness remediation, and you know how public-company audit exposure changes program management. - Technically credible with platform engineering: you can read an architecture discussion, pressure-test an estimate, and hold your own on sequencing conversations with senior engineers without pretending to be one. - Demonstrated experience with at least one of: M&A integration, legal-entity restructuring, or large multi-party partner migrations. - Operates through influence in organizations where authority is split across reporting lines. You get things done with people who don't report to you and don't want another meeting. - Writing-first operator: your default artifacts are documents and dependency maps, not status meetings. - Crypto/digital-asset domain experience is a plus, not a requirement. - Regulated-fintech delivery scar tissue matters more. We could also include "What will make you fail here" as maybe a note but not required. Now Benefits list: - Competitive base