Technical Product Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We have content: description of role (About the role). Responsibilities: many bullet points. Requirements: maybe "Required Qualifications". Qualifications: maybe "Preferred Qualifications". Skills: maybe not explicit; but we could infer from required qualifications? But we should not invent. The posting includes "Required Qualifications" and "Preferred Qualifications". Also "Benefits" listed. Pay: they say salary will be determined based on factors; that's vague, not a specific number. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits is stated (list). Pay: they mention salary will be determined based on factors, but not a specific range. That's not specific content; it's generic. Likely we should not include Pay section because it's not a concrete statement. Schedule: they mention willingness to support live events outside standard business hours; that's schedule info? It's about willingness to work outside hours. Could be considered schedule. But rule: only include if posting actually states them. It does state willingness to support live events and critical releases outside standard business hours when required. That's schedule info. So we could include Schedule section with that statement. We need headings:

for each section. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal. Also remove "We are an equal-opportunity employer..." line. Also remove "Additional Responsibilities" maybe? That seems like responsibilities but could be merged. Also "About Us" maybe not needed? It's about company; could be considered About the role? Probably not needed; but we could keep as part of About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should keep About Us content? It's about company, not role. Might be considered boilerplate? It's not navigation/legal/EEO. It's substantive about company. Should we include? The sections we can output are limited to those headings; we could put About Us under About the role? But About the role heading is for role description. Could we add another heading like "About the company"? Not allowed per list; only those headings. So we must either drop About Us or incorporate into existing sections if relevant. The instruction: "Prefer a few substantive sections over many thin ones." So we could drop About Us if not fitting headings. But we must preserve ALL substantive information; dropping it would lose info. However maybe About Us is considered boilerplate? It's not navigation/legal/EEO but it's generic company description. Might be considered okay to drop? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not those. So we should keep it. But we have no heading for it. Could we treat it as part of "About the role"? That would be mixing role and company info, but still substantive. Might be acceptable. Alternatively we could add a heading like "About the company" but not allowed. So we must incorporate. Thus sections: About the role (includes role description + About Us). Responsibilities (includes core accountabilities bullet points plus Additional Responsibilities). Requirements (maybe Required Qualifications). Qualifications (Preferred Qualifications). Skills (maybe not explicit; we could skip). Benefits (list). Schedule (statement about willingness to work outside hours). Pay: skip. Now we need to format. Let's extract prose for About the role: first paragraph: "The Product Manager leads the definition, prioritization, delivery, launch, and continuous improvement of digital products that power the end-to-end fan and staff experience here. This role owns a complex portfolio spanning mobile and web applications, ticketing, identity, loyalty, payments, suites, parking, access control, frictionless commerce, venue operations, and related integrations. The ideal candidate will translate business and fan needs into clear product outcomes, aligns internal stakeholders and external delivery partners, and guides cross-functional teams through discovery, requirements, sequencing, quality assurance, release readiness, event support, and post-launch optimization. Success requires strong product judgment, disciplined program leadership, comfort with technical systems and vendor architectures, and the ability to make tradeoffs across value, risk, quality, cost, and delivery capacity." Then About Us paragraph: "At OP, we help you harness the power of technology for maximum impact. A technology consulting and solutions company, we offer advisory and managed services, innovative platforms, and staffing solutions across a wide range of fields including AI, cyber security, enterprise architecture, and beyond. For nearly two decades, we ve been challenging the status quo of the consulting industry, serving up fresh, ingenious thinking through a radically lean structure. Together, this strategy delivers unprecedented performance at an unparalleled pace for faster results that propel your business forward." We can combine into one

  or multiple

  . Use

  for prose. Responsibilities: list of core accountabilities bullet points. Also Additional Responsibilities bullet points. We need to convert each bullet into

• . The core accountabilities have several bullet-like sentences separated by periods. Let's extract them: - Own and continuously refine product strategy and roadmaps across the customer's digital ecosystem, connecting initiatives to fan experience, operational, commercial, and platform outcomes. - Run structured prioritization across production support, maintenance, technical debt, platform upgrades, and net-new features using clear criteria such as reach, impact, confidence, effort, cost, risk, and time sensitivity. - Facilitate cross-workstream prioritization forums, confirm sequencing and dependencies, and communicate changes in a way that creates alignment across business leaders, product owners, engineering partners, operations, marketing, analytics, and executives. - Maintain clear portfolio hygiene in tools such as Jira, Jira Product Discovery, Confluence, and shared release trackers, including status, target dates, ownership, dependencies, decisions, and expected outcomes. - Translate ambiguous business needs and operational pain points into well-defined opportunities, features, user stories, acceptance criteria, test scenarios, and measurable outcomes. - Lead discovery and requirements definition with stakeholders across ticketing, marketing, sales, premium, suites, parking, security, finance, operations, game presentation, customer support, and technology. - Guide distributed delivery pods through planning, backlog refinement, sprint execution, demonstrations, UAT, release readiness, and closure while protecting scope clarity and product intent. - Identify cross-pod and cross-platform dependencies early, particularly across mobile, web, backend services, identity, payments, ticketing SDKs/APIs, Adobe, Microsoft Dynamics 365 Commerce, and NBA services. - Ensure product documentation is standardized, complete, current, and usable by technical and non-technical audiences; use AI-assisted tools responsibly to accelerate research and documentation without replacing critical review. - Own product acceptance and quality decisions, ensuring critical defects and operational risks are addressed before production releases. - Create transparent release plans and shared validation trackers that make readiness, testing status, blockers, target dates, and business sign-off visible across teams. - Partner with engineering, QA, analytics, and operations to define practical test coverage for high-risk fan journeys, integrations, edge cases, and event-day scenarios. - Coordinate app-store, SDK, API, platform, and vendor release dependencies, including clear go/no-go criteria and rollback or contingency plans. - Participate in scheduled event support, including evenings, late hours, weekends, and high-profile events, to observe product performance, triage issues, and convert operational learning into backlog improvements. - Lead product relationships with strategic partners and delivery vendors, including Ticketmaster, Globant and other engineering partners, Microsoft, Adobe, NBA technology teams, and specialized venue platforms. - Challenge estimates, architectures, staffing assumptions, and delivery approaches to ensure proposed solutions are proportionate, supportable, and economically sound. - Convert feature definitions into sufficiently clear scope for fixed-price or capacity-based delivery decisions; evaluate value against cost and opportunity cost before committing resources. - Monitor vendor commitments, risks, quality, velocity, resource constraints, and dependencies; escalate with evidence and drive decisions when delivery is blocked or inefficient. - Contribute to contract, renewal, budgeting, roadmap, and capacity discussions by connecting platform choices and feature scope to business impact and total delivery effort. - Use product analytics, user research, operational feedback, support trends, logs, and event observations to identify root causes and prioritize improvements. - Develop working fluency with observability and operational tools, including Datadog or comparable platforms, to trace user journeys, understand errors, and facilitate evidence-based triage. - Partner with analytics teams to define product metrics, reporting needs, data quality requirements, adoption signals, and post-launch measurement plans. - Build repeatable operating rhythms for backlog intake, prioritization, release communication, knowledge transfer, documentation, and post-event learning. - Balance short-term incident response with long-term platform health, making deliberate choices that reduce recurring operational burden and improve scalability. - Lead, coach, and develop product managers and analysts, setting clear expectations for product thinking, documentation, stakeholder management, testing, and follow-through. - Delegate product ownership while maintaining consistent standards across workstreams; create opportunities for team members to deepen domain and technical expertise. - Communicate complex technical and delivery topics at the appropriate altitude for executives, operators, marketers, engineers, and external partners. - Create alignment in high-ambiguity or high-pressure situations by presenting options, consequences, recommendations, decisions, and next steps clearly. - Foster a transparent, collaborative environment where risks are surfaced early, assumptions are challenged constructively, and commitments are tracked to completion. Additional Responsibilities: - Participate in OP monthly team meetings and participate in team-building efforts. - Contribute to OP technical discussions, peer reviews, etc. - Contribute content and collaborate via the OP-Wiki/Knowledge Base. - Provide status reports to OP Account Management as requested. We'll combine all into one
  maybe. Requirements (Required Qualifications): list each bullet. - 7+ years of progressive experience in digital product management, technical program management, platform delivery, or a related discipline, including responsibility for complex cross-functional programs. - Demonstrated experience leading mobile and web products through discovery, requirements, delivery, testing, launch, and iterative improvement. - Strong program management capability in multi-team, multi-vendor environments, including dependency management, roadmap sequencing, risk management, and executive communication. - Experience partnering with engineering teams on APIs, SDKs, identity, payments, integrations, release management, technical debt, observability, and production support. - Ability to create precise product documentation, including problem statements, requirements, user stories, acceptance criteria, process flows, release plans, and decision records. - Experience using product and delivery systems such as Jira, Jira Product Discovery, Confluence, or comparable tools. - Analytical judgment and financial acumen sufficient to evaluate prioritization, estimates, capacity, vendor proposals, and cost-versus-value tradeoffs. - Excellent written, verbal, facilitation, and stakeholder-management skills, with the ability to work effectively across technical, operational, creative, and executive groups. - Willingness and ability to support live events and critical releases outside standard business hours when required. Qualifications (Preferred Qualifications): list each bullet. - Experience in sports, live entertainment, hospitality, venues, retail, ticketing, e-commerce, or other high-volume customer experience environments. - Experience with Ticketmaster products or ticketing integrations; mobile ticketing, entitlements, transfers, access control, premium or suite experiences, and event-day troubleshooting. - Familiarity with Microsoft Dynamics 365 Commerce/POS, Adobe Experience Cloud, identity and authentication flows, loyalty and gamification, payment ecosystems, and frictionless commerce. - Working knowledge of native iOS and Android delivery, web platforms, content management, deep linking, app-store release processes, and cross-platform analytics. - Experience with operational telemetry and troubleshooting tools such as Datadog, including logs, dashboards, service traces, and user-flow analysis. - Understanding