Senior Product Marketing Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting: It starts with description of Unity, product marketing, etc. Then "Scope of the engagement Duration: initial engagement of 1yr, with the possibility of extension based on business need. Location: fully remote or near one of our many hub locations: NYC, SF, MTV, MTL, etc. We ask for meaningful working-hour overlap with US time zones, since product and marketing reviews run on that clock. Commitment: full-time equivalent hours for the duration of the engagement." Then "What You'll Be Doing" list of responsibilities (positioning and narrative, go-to-market execution, audience definition, developer credibility, competitive and market intelligence, voice of the customer, enablement and content, partner and ecosystem marketing, measurement). That's responsibilities. Then "What We're Looking For" list of qualifications: 7-9 years in product marketing or go-to-market roles, with a clear track record of owning a product line or a major launch end to end. Game production fluency — a background in games, or a deep grasp of modern development pipelines and creator workflows. Strongly preferred. Proven experience marketing to technical audiences such as developers, engineers or technical artists, and the credibility to win over users whose default posture is skepticism. Exceptional writing... Independent operator... High comfort with ambiguity... Strong data literacy... Strong with AI tools such as Claude Code, Gemini or similar... Nice to have Platform and ecosystem go-to-market — experience marketing developer platforms, game engines, SDKs or plugin ecosystems. Direct experience with AI or ML products, and the technical judgment to tell a production-ready capability from a good demo. Hands-on creation experience — you have shipped something in Unity or a comparable real-time creation tool. Partner co-marketing — a track record running joint go-to-market motions with major technology partners. Category creation — experience taking a product through a market shift and educating users on a new way of working. Prior contract or consulting experience inside a large matrixed organisation, where you have had to be effective without formal authority. Then "Base Salary Range: We determine the base salary range for this role based on your primary work location: Zone A: $150,000 - $225,000 USD gross Zone B: $169,500 - $254,300 USD gross Zone C: $190,500 - $285,700 USD gross Cette fourchette correspond au salaire de base prévu pour ce poste. En plus du salaire de base, ce poste peut donner droit à des attributions d’actions et à une participation à nos programmes d’incitation de l’entreprise, comme des primes annuelles discrétionnaires ou des commissions de vente. Le montant final de l’offre dépendra de plusieurs facteurs, notamment l’emplacement géographique ainsi que l’expérience pertinente, le parcours professionnel et les compétences du/de la candidat(e). This range reflects the anticipated base salary for this position. Beyond base salary, this role may be eligible for equity awards and participation in our company incentive plans (such as annual discretionary bonuses or sales commissions). The final offer amount will depend on several factors, including geographic location and the candidate’s relevant experience, professional background, and skill set." Then "Avantages Chez Unity..." and later "Benefits At Unity, we want our team members to thrive..." So benefits section. We need to include sections: About the role? Could be a short paragraph summarizing the role. The posting includes introductory paragraphs about Unity and product marketing. That could be "About the role". Then responsibilities: "What You'll Be Doing". Then qualifications: "What We're Looking For". Then Pay: base salary range. Then Benefits: benefits description. Schedule? Not explicitly given; they mention commitment: full-time equivalent hours, location remote/hub, working-hour overlap with US time zones. That could be considered Schedule? But they said only include Schedule if posting actually states them. It does mention commitment: full-time equivalent hours for the duration of the engagement. That's schedule info. Could include Schedule section with that detail. However they said prefer few substantive sections over many thin ones. Might combine location and commitment under About the role? But we need to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. Likely include About the role, Responsibilities, Qualifications (or Requirements), Pay, Benefits. Maybe also Schedule (full-time equivalent hours). But we need to avoid filler. Let's decide: - About the role: introductory description of Unity and product marketing role, scope of engagement (duration, location, commitment). That's substantive. - Responsibilities: the bullet list under "What You'll Be Doing". Use

• . - Qualifications: the list under "What We're Looking For". Could split into Requirements and Nice-to-have? But we can just put all under Qualifications. - Pay: base salary range details. - Benefits: the benefits description. - Schedule: maybe not needed because we already covered commitment in About the role. But we could still include Schedule with "Full-time equivalent hours; remote or hub locations; overlap with US time zones." That's specific. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from the posting, not omit any. That's a lot. We need to ensure we don't leave out any substantive info. For example, the introductory paragraph about Unity powers majority of top mobile games etc. That's substantive. Also the description of product marketing at Unity spans engine developers build in, services, ecosystem, AI capabilities. That's substantive. Also the sentence: "We are looking for an experienced product marketer to take on a defined body of that work on a contract basis. You will pick up a product area or a set of launches, own the marketing for it end to end, and produce work that ships. This is a role for someone who can arrive with limited context, ask the right questions quickly, and start producing positioning, launch plans and enablement material without waiting to be told how." That's substantive. Also the scope of engagement details: Duration, Location, Commitment. Also the responsibilities list items each with description. Also qualifications list items each with description. Also Pay details: base salary range per zone, plus equity awards, etc. Also Benefits: list of benefits. Also Life at Unity description maybe considered About the role? It's more about Unity company. Could be included in About the role. We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to cut out the EEO statements, the privacy policy, the recruiter agency stuff, the disability accommodation form, the repeated English requirement, the repeated Life at Unity paragraph (maybe duplicate). Also the repeated Benefits section (English and French). We need to keep only one version, presumably English. We need to preserve all substantive information, but we can deduplicate duplicate lines. The posting includes both French and English versions of benefits and Life at Unity. We should keep one version (English) and drop the French duplicate. Also the repeated "Life at Unity" paragraph appears twice (once in French? Actually there is a French version then English). We'll keep one English version. Also the repeated "Avantages Chez Unity..." and "Benefits At Unity..." duplicates; keep one English. Also the repeated "Unity is a proud equal opportunity employer." etc. That's boilerplate; remove. Also the repeated "If you have a disability..." etc. Remove. Also the repeated "This position requires the incumbent to have a sufficient knowledge of English..." appears twice; keep one. Also the repeated "Unity [NYSE : U] is the world’s leading game engine..." appears twice; keep one. Also the repeated "Avantages Chez Unity..." and "Benefits At Unity..." duplicates; keep one. Also the repeated "Base Salary Range:" appears twice (once French then English). Keep one English version. Also the repeated "Cette fourchette correspond au salaire de base prévu pour ce poste..." French version; drop. Also the repeated "Avantages Chez Unity..." French; drop. Now we need to produce HTML fragment. We'll structure:

  About the role

  ... (introductory paragraphs about Unity, product marketing, scope of engagement)

  Responsibilities

  • Positioning and narrative — Own the positioning and messaging for the product areas assigned to you. Translate technical capability into obvious workflow value, and write the narrative that Sales, Community and Content all work from.
  • Go-to-market execution — Lead go-to-market for launches, betas and feature rollouts: tiering, audience targeting, channel plan, enablement and launch-day execution, followed by an honest read on what worked.
  • Audience definition — Define precisely who a product is for, from indie creators to technical directors, and document it clearly enough that other teams can act on it without reinterpreting it.
  • Developer credibility — Developers are inherently skeptical of marketing claims, and increasingly so of AI claims. Write messaging that earns credibility with practitioners rather than hyping past them, working with Community and DevRel to meet developers where the real discussions happen.
  • Competitive and market intelligence — Track the relevant landscape and turn market shifts into sharp positioning and usable sales material.
  • Voice of the customer — Turn forum threads, interviews and community feedback into signal that product and marketing teams can actually use.
  • Enablement and content — Equip Sales, Success and Support with pitch decks, battlecards and objection handling. Partner with Content marketing on launch assets and developer-facing material.
  • Partner and ecosystem marketing — Where an initiative involves third-party tools or platform partners, drive the joint go-to-market and co-marketing motion.
  • Measurement — Work with Product and Analytics to define what success looks like for each launch in advance, and report against it afterwards.

  Qualifications

  • 7-9 years in product marketing or go-to-market roles, with a clear track record of owning a product line or a major launch end to end.
  • Game production fluency — a background in games, or a deep grasp of modern development pipelines and creator workflows. Strongly preferred.
  • Proven experience marketing to technical audiences such as developers, engineers or technical artists, and the credibility to win over users whose default posture is skepticism.
  • Exceptional writing. You can turn complex technology into a crisp, obvious narrative across a launch page, a keynote section, a battlecard or a Slack thread with engineers.
  • Independent operator. Contract engagements come with less context and less standing than a permanent role. You need to be comfortable getting yourself oriented, driving work forward across teams you have just met, and producing finished artifacts rather than waiting for direction.
  • High comfort with ambiguity, including early-stage products where the strategy is still moving and the roadmap shifts underneath you.
  • Strong data literacy. You can set the right metrics, read performance signals honestly, and change course on evidence.
  • Strong with AI tools such as Claude Code, Gemini or similar, and a practical sense of how to use them to move faster without letting the output go out unchecked.
  • Nice to have: Platform and ecosystem go-to-market — experience marketing developer platforms, game engines, SDKs or plugin ecosystems.
  • Nice to have: Direct experience with AI or ML products, and the technical judgment to tell a production