Head of Brand Partnerships

We need to output HTML fragment with sections: headings using

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. No job title heading. No Job ID. No application instructions. No duplicated lines. We need to parse the posting. Content: - About Nitro Studios (intro). That's about the company, not necessarily a section heading? Could be "About the role"? Actually "About Nitro Studios" is company description. Could be placed under a heading like "About the role"? But instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - Role description: description of responsibilities (day to day). That's responsibilities. - What success looks like: includes first 90 days, first year, how you are paid (percentage of every deal). That could be under "Pay" maybe? Actually pay details: "How you are paid: a percentage of every deal you close". That's pay/compensation. Also success metrics maybe not needed. - What we’re looking for: requirements/qualifications/skills. - Nice to have: additional nice-to-have skills. - Location: Full-time, remote — work from anywhere. The studio is based in Tel Aviv, and you work with the founders and the game team remotely. That's location, maybe schedule? Not schedule. Could be under "Schedule"? Not exactly. There's no explicit schedule info besides full-time remote. Could include under "Schedule" maybe? But schedule is about hours/shift. Not given. Might omit schedule section if not specific. - Benefits: Not mentioned explicitly. No benefits listed. So we should not create Benefits section. - Pay: we have compensation detail: percentage of every deal. That's specific. So we can include Pay section. - About the role: maybe we can include a brief about the role (role description). But we already have Responsibilities. Could combine. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract: About Nitro Studios: details about company: builds and operates original games within Fortnite’s UGC ecosystem, focusing on fast-paced, highly replayable experiences. • First year: 12 games shipped, over 22 million plays, 9 million unique players and 450 million minutes played — one of the top Fortnite creators worldwide, without paid user acquisition.• Founded in 2026 in Tel Aviv: fully bootstrapped, already profitable and continuing to grow.• Founder-led audience insight: a background in gaming content and YouTube channels with large followings, treating player understanding as a core design constraint from thumbnail to first-session experience.• Short, iterative loops: games are continuously updated with new content, events and balance changes based on live data. That's substantive. Could be placed under a heading like "About the company" but not in allowed list. However we could put under "About the role"? Might be okay to have a section "About the role" containing that description? But "About the role" usually describes the role, not company. However instructions say use those headings as examples, not strict requirement to only those? It says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings; we can also possibly use other headings? It says use

for section headings (e.g. ...). Likely they expect those headings. We should map content to those headings where appropriate. Thus: - About the role: could include role description (what you will own, day to day). That's responsibilities actually. But we could put role description under About the role, and responsibilities under Responsibilities. Might be duplication but okay. Better: About the role: brief summary of role (own business, relationships, offers, deals, pipeline). Responsibilities: bullet list of day-to-day tasks. Requirements: what we’re looking for (must have). Qualifications: maybe same as requirements? Could split: Requirements = mandatory, Qualifications = nice-to-have? But they said prefer few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section maybe "Requirements". But we have both mandatory and nice-to-have. Could have Requirements (mandatory) and Skills (nice-to-have). Or Qualifications for mandatory, Skills for nice-to-have. Let's decide. We have: What we’re looking for (mandatory): - Brand deals closed in gaming: at least three brand, sponsorship or media deals you personally created and closed in games, esports or gaming media. - A network in gaming and brands: brand and marketing decision-makers who buy gaming campaigns, and people at game studios, publishers, platforms and agencies, who take your call. - From the games industry: your commercial career is in gaming, for example in-game brand integrations, esports or gaming sponsorships, gaming media or creator campaigns, or partnerships at a studio, publisher or platform. Commercial experience from outside games is not enough. - You have built a pipeline before: a proposal, a price list and a forecast that carry your fingerprints, not a book of business you inherited. - Creative to commercial: you can turn a game mechanic and an audience into a brief a brand understands, and push back when a client’s idea does not work in the game. - Hands-on: you write the deck, run the CRM and make the calls yourself. - English at a commercial level: you pitch, write and negotiate in it. Nice to have: - Fortnite, Roblox or UGC platforms: you understand what can and cannot be built inside them. - Agency side: you have sat on the other side of the table. - Youth entertainment or licensing: you have turned characters, content or IP into commercial deals. - Large organizations: you have sold to banks, ministries or companies with a procurement process. - Hebrew: useful with the team and with Israeli brands and agencies. - No degree is required. We care about the deals you closed and the people who will still answer your call. Location: Full-time, remote — work from anywhere. The studio is based in Tel Aviv, and you work with the founders and the game team remotely. Pay: How you are paid: a percentage of every deal you close, so the upside is yours. The details are agreed with you in the process. Success metrics maybe not needed as separate section; could be included under About the role or Responsibilities? But we could include under "About the role" maybe as "What success looks like". However not a standard heading. Could omit if not needed? But we must preserve ALL substantive information. So we need to include that info somewhere. Could add a section "What success looks like" but not in allowed headings. However we could incorporate into "About the role" or "Responsibilities". Probably best to add a subsection under About the role as a paragraph. But instructions: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role, Responsibilities, Requirements, Pay, Location. That's five sections. Nice-to-have could be part of Requirements or Skills. Could make Skills section for nice-to-have. Thus sections: - About the role: includes company description? Actually About the role could include role description and success metrics. But company description maybe not needed under About the role; but we could include a brief "About Nitro Studios" as part of About the role? Might be okay. Alternatively we could have a section "About Nitro Studios" but not in allowed headings. Might be risky. Better to embed company info in About the role? The instructions say use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Safer to stick to those. Thus we need to map company info somewhere. Could put under About the role as a brief intro: "Nitro Studios builds and operates original games within Fortnite’s UGC ecosystem..." That is about the company, but we can still put there. Now Responsibilities: bullet list of day-to-day tasks. Requirements: mandatory qualifications. Skills: nice-to-have. Pay: compensation. Location: location and remote. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like EEO etc (none present). We must not include application instructions (none present). We must not include duplicated lines. Now produce HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive info. Let's extract each piece. About Nitro Studios (company description): - Nitro Studios builds and operates original games within Fortnite’s UGC ecosystem, focusing on fast-paced, highly replayable experiences. - First year: 12 games shipped, over 22 million plays, 9 million unique players and 450 million minutes played — one of the top Fortnite creators worldwide, without paid user acquisition. - Founded in 2026 in Tel Aviv: fully bootstrapped, already profitable and continuing to grow. - Founder-led audience insight: a background in gaming content and YouTube channels with large followings, treating player understanding as a core design constraint from thumbnail to first-session experience. - Short, iterative loops: games are continuously updated with new content, events and balance changes based on live data. Role description / What success looks like: - Nitro’s games reach millions of players every month, and brands want to be where those players are. You will own that business — the relationships, the offer, the deals and the pipeline — working directly with the founders. - Day to day, you will: (list) - What success looks like: * First 90 days: several deals already closed. The target list, the deck and the pricing exist to sign campaigns, not to present them. * First year: brand campaigns live inside our games, repeat clients, and a pipeline you can forecast deal by deal. * How you are paid: a percentage of every deal you close, so the upside is yours. The details are agreed with you in the process. But we already have Pay section; we could move pay details there. Responsibilities (day to day): - Open doors: reach marketing, brand, digital and innovation leads at brands and agencies, in Israel and abroad. - Turn our audience into an offer: package Nitro’s games, players and in-game formats into something a CMO can buy, with clear pricing and deliverables. - Build the pitch: shape campaign ideas with our game team, so every proposal is specific to the brand. - Run the deal end to end: discovery, proposal, negotiation, procurement, signature and handover to the team that builds it. - Run the machine: target lists, pipeline, CRM, forecast and case studies. - This is a closing role, not account management. You are measured on signed campaigns. Requirements (mandatory): - Brand deals closed in gaming: at least three brand, sponsorship or media deals you personally created and closed in games, esports or gaming media. We will ask who bought, what your part was, and whether we can speak to the buyer. - A network in gaming and brands: brand and marketing decision-makers who buy gaming campaigns, and people at game studios, publishers, platforms and agencies, who take your call. - From the games industry: your commercial career is in gaming, for example in-game brand integrations, esports or gaming sponsorships, gaming media or creator campaigns, or partnerships at a studio, publisher or platform. Commercial experience from outside games is not enough for this role. - You have built a pipeline before: a proposal, a price list and a forecast that carry your fingerprints, not a book of business you inherited. - Creative to commercial: you can turn a game mechanic and an audience into a brief a brand