Senior Machine Learning Engineer, Advertiser Growth

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We have: - "The opportunity At Unity, we are building ..." This is about the role description. Could be "About the role" section. - "What You'll Be Doing" list: bullet points (Next-Gen budget pacing, Creative GenAI infrastructure, Marketplace experimentation engine, High-Scale billing reliability, Scientific optimization). Those are responsibilities. - "What We're Looking For": list of qualifications/requirements: advanced degree, 6+ years, etc. Could be Requirements or Qualifications. - "You might also have Experience embracing AI...": could be Skills or Additional qualifications. - "Additional Information": salary ranges (Pay). Also mention equity awards etc. - "Benefits": list of benefits. - No explicit schedule info; not present, so omit Schedule. - No explicit "Skills" separate; but we could put technical skills under Requirements or Skills. The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have content for About the role (intro paragraph). Responsibilities (What You'll Be Doing). Requirements/Qualifications (What We're Looking For). Could combine Requirements and Qualifications? They are separate headings but we can include both if we have content. The "What We're Looking For" includes both requirements and qualifications; we could split: Requirements (experience, degree) and Qualifications (maybe advanced degree?). But better to follow typical: Requirements = mandatory, Qualifications = preferred? The posting lumps them. We could put all under Requirements and omit Qualifications, or we could duplicate? The instruction: Prefer a few substantive sections over many thin ones. So we should not create both if they'd be thin. We'll include Requirements (or Qualifications) but not both. Which one? The posting includes "Advanced degree...", "6+ years...", etc. Those are requirements. Also "You might also have Experience embracing AI..." could be Skills. So we can have Requirements (mandatory) and Skills (preferred/nice-to-have). Benefits and Pay sections. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We must not repeat job title as heading. No Job ID. We must use

for section headings. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We need to include salary ranges exactly as given: Zone A: $210,300 - $273,400 USD etc. Also mention equity awards and incentive plans. Benefits list: Comprehensive health, life, and disability insurance | Commute subsidy | Employee stock ownership | Competitive retirement/pension plans | Generous vacation and personal days | Support for new parents through leave and family-care programs | Office food snacks | Mental Health and Wellbeing programs and support | Employee Resource Groups | Global Employee Assistance Program | Training and development programs | Volunteering and donation matching program We need to turn that into a list. Also note: "Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status." That's substantive? It's a note; we should preserve. Could be a

  . Also "While specific benefits vary, here are some of the ways we strive to take care of our eligible team members globally:" That's intro. We'll include that as a

  before the list. Now "About the role": The first paragraph(s) up to "What You'll Be Doing". Let's capture: "The opportunity At Unity, we are building a world-class ad-tech ecosystem that connects billions of users with the creators and experiences they love. The Advertiser Growth team is the engine of this mission, ensuring that as our marketplace expands, advertisers have the intelligent tools, robust infrastructure, and rigorous experimentation frameworks needed to scale their impact. In 2026, our roadmap is defined by three transformative pillars: Foundation, Smart, and Intelligence. This role is unique in its technical breadth, sitting at the intersection of financial execution, creative innovation, and marketplace science. You will architect the GenAI systems that build high-performing creatives, design the pacing algorithms that manage multi-million dollar budgets, ensure our billing pipelines handle massive scale with zero-fault tolerance, and build the experimentation infrastructure that allows us to scientifically evolve the marketplace. This is a high-stakes role where your technical leadership directly governs Unity’s financial integrity and the long-term growth of our ecosystem." We'll put that in a

  . Now Responsibilities: list items from "What You'll Be Doing". Each bullet starts with a bold heading? Actually they are like: **Next-Gen budget pacing:** Design and optimize sophisticated pacing controllers (PID, probabilistic forecasting) to smooth advertiser spend across diverse time zones and traffic spikes, ensuring optimal delivery and marketplace stability. **Creative GenAI infrastructure:** Lead the backend integration of Generative AI models (Diffusion, LLMs) to automate the creation of high-performing image and video assets tailored to specific campaign goals and formats. **Marketplace experimentation engine:** Build and scale the infrastructure for high-velocity experimentation, including A/B testing, switchback tests, and long-term holdouts to measure the impact of marketplace changes on advertiser ROI and platform health. **High-Scale billing reliability:** Architect and maintain high-throughput billing pipelines that process billions of events with 100% accuracy, bridging the gap between real-time ad delivery and mission-critical financial reconciliation. **Scientific optimization:** Analyze complex financial and marketplace datasets to refine the trade-off between spend velocity and advertiser performance, using experimentation results to tune pacing and billing logic. We'll make each as

• with the bold text maybe keep as strong? But we can just output plain text; the instruction didn't require preserving formatting like bold. We'll keep the substance. Now Requirements: list from "What We're Looking For". Items: - Advanced degree in computer science or relevant engineering-related field or equivalent experience. - 6+ years of software engineering experience, including 3+ years working on ads delivery systems. - Extensive experience building and operating large-scale, low-latency backend systems using languages like Java, Go, or Scala. - Deep familiarity with building or maintaining budget control systems, feedback loops, or spend-prediction algorithms. - Proven experience building or scaling experimentation platforms, with a deep understanding of variance reduction, interference/network effects, and metric design in a marketplace context. - A track record of working on "mission-critical" pipelines (like billing, payments, or clearinghouses) where data precision, idempotency, and fault tolerance are paramount. - Experience or strong technical interest in building the backend workflows required to serve, scale, and store Generative AI models for creative asset generation. - Proficiency with real-time stream processing (Kafka, Flink, or Spark) specifically applied to event-based charging and real-time performance feedback. - A proven ability to lead complex, multi-quarter technical roadmaps and mentor senior engineers in a high-growth environment. We'll put each as
• . Now Skills: from "You might also have Experience embracing AI as a strategic advantage in engineering, following established best practices for code quality and security." That's one item; could be a
• or

  . Since it's a list, we can make a

  • . Now Benefits: include note and list. Pay: include salary ranges and note about equity awards etc. We must not include duplicated lines. The posting repeats the salary paragraph twice; we need to include only once. Now ensure we don't include boilerplate like EEO, legal, etc. We removed those. Now output HTML fragment only. Let's craft:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • Experience embracing AI as a strategic advantage in engineering, following established best practices for code quality and security.

    Benefits

    Please note: Benefits eligibility, specific offerings, and coverage vary based on the country and employment status. While specific benefits vary, here are some of the ways we strive to take care of our eligible team members globally:

    • Comprehensive health, life, and disability insurance
    • Commute subsidy
    • Employee stock ownership
    • Competitive retirement/pension plans
    • Generous vacation and personal days
    • Support for new parents through leave and family-care programs
    • Office food snacks
    • Mental Health and Wellbeing programs and support
    • Employee Resource Groups
    • Global Employee Assistance Program
    • Training and development programs
    • Volunteering and donation matching program

    Pay

    Zone A: $210,300 - $273,400 USD
    Zone B: $187,200 - $243,300 USD
    Zone C: $165,600 - $215,200 USD

    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.

    Check for any missing substantive info: The "Additional Information" also had duplicate sentence about salary range repeated; we included once. Also note about equity awards etc we included. We omitted "Life at Unity" paragraph about Unity being leading game engine etc. That's substantive? It's about company description; could be considered part of About the role? But it's more general company info, not specific to role. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Should we include that? It's under "Life at Unity". It's not boilerplate; it's describing Unity. Might be considered substantive. However, we already have About the role describing the team and mission. The Life at Unity paragraph is generic company overview; could be considered filler but it's substantive info about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. So we should keep it. Where to put? Could be another section like "About Unity" but not in prescribed headings. We could incorporate into About the role as additional paragraph. The About the role currently only includes the opportunity paragraph. We could add another

    after that with the Life at Unity content. Let's capture Life at Unity paragraph: "Life at Unity Unity [NYSE: U] is the world’s leading game engine, powering play for more than 3 billion consumers each month. The top mobile games in the world, the most played PC indie titles, the most innovative console games, and virtually all of the top XR and Web Games are developed, deployed, and grown in Unity. Unity also enables teams across industries like automotive, manufacturing, and healthcare to design, simulate, and collaborate in 3D — closing the gap between ideas and reality. For more information, please visit www.unity.com." We'll add as a

    under About the role after the first paragraph. Now also there is a line about "Unity is a proud equal opportunity employer..." that's EEO boilerplate; we should remove. Also lines about disability accommodation, headhunters, privacy, etc. Remove. Now check for any other substantive info: The "Additional Information" also had "This range reflects the anticipated