Senior Product Manager - unannounced IP

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "What We Need", "What You Will Do", "What Will Make You a Great Fit", "Bonus Points", pay range. Also maybe "Benefits" not specified. We must not include boilerplate like EEO, accommodation, scam warning, etc. Also we must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. We need to map content to these headings. We have: - About the role: could be "Who We Are" and "What We Need"? Actually "About the role" could be description of role: "We are looking for a Senior Product Manager to join the 2K Product team to work on a new IP. Your role will be to help strategically understand market trends, advocate and ground our decisions in our player, and prioritize what makes a winning title in a competitive gaming landscape. You will work closely with studios and product leadership to develop, guide, implement, and optimize the Live Services strategies supporting our new IPs' creative vision." That's a prose. - Responsibilities: "What You Will Do" list of duties. - Requirements/Qualifications/Skills: "What Will Make You a Great Fit" includes requirements. Also "Bonus Points" could be additional qualifications/skills. - Pay: we have pay range. - Benefits: not specified (only mention "full range of medical, financial, and/or other benefits" but not specific; we should not create Benefits section unless posting actually states them. It says "may also include other elements, including a bonus and/or equity awards, in addition to a full range of medical, financial, and/or other benefits." That's somewhat generic but it's stating benefits exist. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits exist (full range of medical, financial, and/or other benefits). That's somewhat vague but it's stating benefits. I'd include a Benefits section with that statement? Might be considered filler? It says "full range of medical, financial, and/or other benefits." That's not specific but it's a statement. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits exist, albeit generic. I'd include Benefits with that sentence. - Schedule: not mentioned, so omit. We also need to include metadata like Job ID? Not present. So ignore. We must not include boilerplate: equal opportunity, accommodation, scam warning, etc. Remove those paragraphs. We need to preserve all substantive information. So we need to keep the "Who We Are" paragraph? That's about company, not role. Should we include? It's substantive but not under any heading. Could be placed under "About the role"? Actually "About the role" heading is for role description, not company. But we could include a short paragraph under "About the role" that includes company overview? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can have those headings. We need to decide which sections to include based on content. We have content for: - About the role: could combine "Who We Are" and "What We Need"? But "Who We Are" is about company, not role. Might be better to put under "About the role" a brief description of the role and maybe company context. However we must not invent or summarize away detail. We can keep the "Who We Are" paragraph as a

under a heading? But there is no heading for company. Could we add a heading "About 2K"? Not in allowed list. The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should map content to those headings, maybe omitting company info if not fitting. But we must preserve ALL substantive information; we cannot drop company info. However we could include it under "About the role" as a paragraph describing the company as part of role context. That's not inventing; it's just placing it there. That should be okay. Thus:

About the role

2K is headquartered in Novato, California and is a wholly owned label of Take-Two Interactive Software, Inc. (NASDAQ: TTWO). Founded in 2005, 2K Games is a global video game company, publishing titles developed by some of the most influential game development studios in the world. Our studios responsible for developing 2K’s portfolio of world-class games across multiple platforms, include Visual Concepts, Firaxis, Hangar 13, CatDaddy, Cloud Chamber, 31st Union, and HB Studios. Our portfolio of titles is expanding due to our global strategic plan, building and acquiring exciting studios whose content continues to inspire all of us! 2K publishes titles in today’s most popular gaming genres, including sports, shooters, action, role-playing, strategy, casual, and family entertainment. Our team of engineers, marketers, artists, writers, data scientists, producers, thinkers and doers, are the professional publishing stewards of our growing library of critically-acclaimed franchises such as NBA 2K, 2K PGA, Battleborn, BioShock, Borderlands, The Quarry, The Darkness, Mafia, Sid Meier’s Civilization, Marvel’s Midnight Suns, WWE 2K, and XCOM. At 2K, we pride ourselves on creating an inclusive work environment, which means encouraging our teams to Come as You Are and do your best work! We encourage ALL applicants to explore our global positions, even if they don’t meet every requirement for the role. If you're interested in the job and think you have what it takes to work at 2K, we encourage you to apply!

Then responsibilities:

Responsibilities

• Closely partner with development and publishing teams to drive, define and deliver product & business strategy for unannounced projects, including:
... Actually the list includes multiple bullet points each starting with a verb. We need to break each duty into
• . The original "What You Will Do" includes a colon after "including:" then a list of items separated by line breaks. We'll extract each bullet. Let's list them: - Collaborate with studio and publishing teams to build Product Needs for in-game features and core gameplay, focused on player engagement, interest, satisfaction and how those relate to business outcomes. - Effectively partner with studio and publishing teams to guide and support prioritization, tradeoffs and value. - Use data, insights (research), and user testing to build a deep understanding of player behaviors, engagement patterns, content preferences, and player trust. - Partner with Monetization and Commercial to connect player satisfaction and business value to create win-win scenarios for both - Define Product imperatives and needs, market fit and testable hypothesis for a both successful game and Live Service updates. - Team up with marketing to connect our product offering to our marketing strategy so we reach the right players with the right promise - Market Intelligence – Deliver research and thought leadership on the industry landscape, trends, competitor products, and recommendations that help us grow and evolve our thinking. - Be the Product Champion – Share insights, processes, and lessons learned with other studio & publishing teams. - Be the Player Advocate – Deeply understand and advocate for the player’s perspective; be their advocate in the room who understands them and speaks up for them to make sure we’re authentically serving our players. We need to ensure each is a
• . Also the first bullet includes "including:" but we can keep as part of the li. Now Requirements/Qualifications/Skills: We have "What Will Make You a Great Fit" paragraph with multiple bullet-like sentences. Also "Bonus Points". We could combine into Requirements and Skills sections. But we have headings: Requirements, Qualifications, Skills. We need to decide which to use. Could put all under Requirements. Or split: Requirements (experience), Qualifications (education? none), Skills (specific skills). Since no explicit education, we could put all under Requirements and Skills. But we need to avoid thin sections. Perhaps combine into one section "Requirements" containing the list, and another "Skills" for bonus points? However the instruction: Prefer a few substantive sections over many thin ones. So maybe just one section "Requirements" that includes both the core requirements and bonus points. Or we could have "Requirements" and "Skills". Let's see. We have core requirements: - 5+ years of experience, including product management, production, live ops, game design, or other related fields within Live Service / Competitive games - Deep understanding of and passion for competitive games, player motivations, and market trends, with the ability to deconstruct what drives successful live games and the risks and opportunities within them - Strong shooter background professionally or recreationally, with the ability to deconstruct, analyze and synthesize market trends across data and personal experience lenses - A data-informed strategic thinker who is able to balance business priorities, customer perspective, resources, capacity, and partner needs to drive clear decisions. - Excellent interpersonal, written, and verbal communication skills, with a collaborative, alignment-building approach that emphasizes influence, clarity, and shared understanding - Strong understanding of service-based products and methodologies, including drivers of performance, player needs/sensitivities and content models. - Able to thrive in ambiguous environments and enjoy creating clarity - Comfortable operating in ambiguous environments, proactively identifying risks and opportunities early and working to mitigate issues before they become problems Bonus points: - Experience working on multiplayer competitive games in Product Management, Game Design, Production, Insights, or Strategy - Proficiency with business intelligence tools and comfortable building models to explore opportunities while working closely with analytics We could put all under Requirements as a list. Or split: Requirements (the first set) and Skills (bonus points). But the bonus points are also skills/experience. I'd make two sections: Requirements and Skills. Both substantive. Thus:

  Requirements

  • 5+ years of experience, including product management, production, live ops, game design, or other related fields within Live Service / Competitive games
  • Deep understanding of and passion for competitive games, player motivations, and market trends, with the ability to deconstruct what drives successful live games and the risks and opportunities within them
  • Strong shooter background professionally or recreationally, with the ability to deconstruct, analyze and synthesize market trends across data and personal experience lenses
  • A data-informed strategic thinker who is able to balance business priorities, customer perspective, resources, capacity, and partner needs to drive clear decisions.
  • Excellent interpersonal, written, and verbal communication skills, with a collaborative, alignment-building approach that emphasizes influence, clarity, and shared understanding
  • Strong understanding of service-based products and methodologies, including drivers of performance, player needs/sensitivities and content models.
  • Able to thrive in ambiguous environments and enjoy creating clarity
  • Comfortable operating in ambiguous environments, proactively identifying risks and opportunities early and working to mitigate issues before they become problems

  Skills

  • Experience working on multiplayer competitive games in Product Management, Game Design, Production, Insights, or Strategy
  • Proficiency with business intelligence tools and comfortable building models to explore opportunities while working closely with analytics
  Now Pay:

  Pay

  The pay range for this position in California at the start of employment