Senior Research Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description, Responsibilities, Qualifications, Additional Information (maybe includes schedule, pay, benefits). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes "Additional Information" with application window close date, hybrid/remote, background check. Also includes "Health & Well-Being" with benefits details. Also "Perks & Professional Growth". Also "Life in the Office". Also pay range. We need to map content to appropriate sections. We have: - About the role: maybe from Job Description paragraph: "CD PROJEKT RED is looking for an experienced Senior Research Manager..." That's description of role. Could be "About the role". We'll put that as

About the role

with

. - Responsibilities: list bullet points under "Responsibilities". We'll output

Responsibilities

• ... each bullet. - Qualifications: list bullet points under "Qualifications". We'll output

  Qualifications

  . - Skills: maybe not separate; but we have some skill-like items: "Exceptional written and verbal communication", "High degree of emotional intelligence", etc. Those are already in Qualifications. Could treat as Skills section but we already have Qualifications. The instruction says use headings like Skills if there is content. We could combine Qualifications and Skills? Better to keep Qualifications as is, and maybe Skills not needed. - Benefits: we have Health & Well-Being details: medical healthcare, mental health support, paid leave, 401K, LSA, menstrual leave, RED Parents Network, flexible hours. Also Perks & Professional Growth: trainings, welcome pack, etc. Life in the Office: dog-friendly, international, no dress-code. These are benefits/perks. We'll create a Benefits section with
  listing these. - Pay: we have pay range: $101,000 - $185,100 USD annually. Also note about compensation determination. We'll include Pay section with

  stating range. - Schedule: we have hybrid/in-office or fully remote, flexible working hours. Also mention application window close date? That's not schedule. Schedule could be flexible working hours, hybrid/remote. We'll include Schedule section with

  stating hybrid/remote or fully remote, flexible hours. We must not include sections with placeholder text like "commensurate with experience". We have real content. We must not include duplicated lines. Ensure we preserve all substantive info. We need to remove boilerplate: "Company Description" paragraph about mission and social media etc. That's not needed? It's company description but maybe we can include as About the company? Not required headings. The instruction says use headings for sections like About the role, Responsibilities, etc. Company description could be omitted or maybe included as part of About the role? The company description is not about the role but about company. Could be omitted as not required. However we must preserve ALL substantive information; but we can omit company description if it's not under any heading? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. Could we include it as a paragraph before headings? The instruction says output only HTML fragment, no /. It didn't forbid extra paragraphs not under headings. But they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

  • for any list of duties/requirements/benefits, and

    for prose. It didn't say we cannot have other paragraphs outside headings. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have a leading

    for company description if we want. But maybe better to incorporate into About the role? The About the role heading could include both role description and company description? But that might mix. However we can add a

    before any headings for company description. That is permissible. But we need to ensure we don't include navigation/legal/EEO etc. The posting includes "If you've observed any irregularities (i.e. legal or ethical violations) in our recruitment process, please click here to report them anonymously." That's boilerplate/legal; we should remove. Also "As part of our pre-employment process, candidates selected for this position will be required to complete a background check in accordance with applicable laws and regulations." That's substantive? It's part of Additional Information; we could keep it maybe under Additional Information but we don't have a heading for that. Could we put it under Additional Information as a

    ? Not a standard heading. Might be okay to include as a paragraph under Additional Information but we don't have heading for that. Could we treat it as part of "Additional Information" but not a heading? The instruction says use headings for those specific categories; but we can still have other paragraphs not under those headings. However to be safe, we could include it under a heading like "Additional Information" but that's not in the list. The instruction didn't forbid other headings, but said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we cannot use other headings, but they gave examples. Safer to stick to those headings only. So we need to fit background check info somewhere else, maybe under Schedule? Not appropriate. Could be under Benefits? Not really. Could be under Qualifications? No. Maybe we can incorporate it into a paragraph under "About the role" or "Responsibilities"? Not ideal. Alternatively, we could create a heading "Additional Information" as

    Additional Information

    even though not in list; but instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't explicitly forbid other headings, but they say "Use

    for section headings (e.g. ...)". That implies we should use those headings for sections; but we could still use other headings if needed? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you should use those headings for those sections; but you could also have other headings if needed? The safer approach is to only use those headings and place any other info under appropriate existing headings or as prose paragraphs without headings. Thus we can put background check info as a

    after the Pay section maybe, without a heading. Similarly, the application window close date and hybrid/remote info could go under Schedule section. We also have "This job can be hybrid/in-office or fully remote." and "Flexible working hours." That fits Schedule. Now, we need to ensure we don't repeat the job title as heading. The job title is "Senior Research Manager". We'll not use that. Now, let's extract content. Company Description paragraph: "To create revolutionary, story-driven RPGs which go straight to the hearts of gamers — this is our mission. Want to dive deeper into our company’s culture? Explore our social media and check out our YouTube channel and Beyond the Game Blog where we share behind-the-scenes insights and stories direct from our team members!" We'll keep that as a

    at start. Job Description paragraph: "CD PROJEKT RED is looking for an experienced Senior Research Manager with strong problem-solving skills to join our AI R&D team and help lead the development and delivery of solutions that will shape the next generation of immersive gaming experiences and tools. In this role, you will manage cross-functional projects that enhance user experience, game development pipelines, and our teams' creative capabilities." We'll put that under About the role. Responsibilities bullet list: - Work closely with the AI Director in driving new major initiatives within the AI R&D Team. - Serve as a bridge between East Coast and Europe time zone across both the AI R&D teams and projects. - Align and motivate your team towards clearly defined goals. - Form and nurture cohesive, high-performing teams that are empowered to self-organize and achieve outstanding results. - Unblock others. - Identify and address bottlenecks and queues, foster incremental delivery. - Project manage AI initiatives, ensuring the resource, scope and time constraints are balanced. - Identify risks and establish mitigation plans. - Continuously look at improving production processes (project planning, scoping, scheduling, roadmaps, requirements gathering, etc…). - Foster and maintain relations with key external partners. - Advocate for actionable and beneficial improvements, challenging the status quo with bravery and innovation. - Gather, acknowledge, and respond to internal feedback, adjusting processes and approaches as necessary. Qualifications bullet list: - 5+ years of software project management experience, with 3+ years in a leadership role. - Full cycle of an AI product, AI research or Game development. Ideally all. - Demonstrated experience in leading cross-functional teams, preferably in an Agile environment, with a focus on team empowerment and self-organization. - Exceptional written and verbal communication. - A high degree of emotional intelligence that is demonstrable in every interaction. - Ability to maintain composure under pressure and rally multiple teams to achieve a common goal. - Highly motivated, self-driven and proactively resolves problems with minimal oversight. - Seeks guidance when appropriate. - Accountable to the outcome whatever they might be. - Intellectually curious. - Humble and curious, constantly seeking learning opportunities, not limiting oneself to the bounds of role or company. - Experience with industry project management tools (e.g. Hansoft, Jira, Confluence, Office suite). - Excellent analytical skills. - Comfortable modelling and analyzing data. - Nice to haves: Deep understanding of the AI and gaming industries. - Good mastery of the Atlassian suite (Jira & Confluence) - Bachelor’s degree in a related field or equivalent professional experience We could separate "Nice to haves" as separate bullet but it's okay. Benefits: from Health & Well-Being and Perks & Professional Growth and Life in the Office. List: - Company-paid medical healthcare (dental, vision, and mental). - Free mental health support, including access to counseling, psychiatric care, and a variety of well-being webinars. - Paid leave — 26 days of vacation, 10 sick days, & 12 calendar holidays per year. - 401K with employer matching. - Lifestyle Spending Account (LSA) – $100 per month to use towards fitness, wellness, internet, home office equipment, learning, streaming services, and more. - Menstrual leave — employees who menstruate can take one extra day off when experiencing period pain. - RED Parents Network — support for working parents. - Flexible working hours. - Trainings, lectures, and courses — internal workshops, knowledge-sharing initiatives, online tutorials, and e-learning classes are all available. - A welcome pack filled with goodies — to help you feel right at home once you join the team. - Life in the Office Dog-friendly office — bring your pooch with you and look after them while working! There’s always a furry friend or two to meet. - Truly international working environment — a chance to meet and work with a diverse selection of people from all around the world. - No dress-code — we like to keep it casual. We could combine some. Pay: "Estimated pay range for this position: $