Software Engineer, Ads Pangle - USDS

We need to output only HTML fragment with sections: About the team? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes "About the team" (not exactly "About the role") but we can map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. The posting includes "About the team" describing Pangle, we could treat that as About the role? Might be okay. Also there is "Responsibilities" list. There's "Qualifications" with Minimum and Preferred. There's "Benefits" described. There's Pay: compensation range. There's Schedule: mention shift to fully in-person schedule up to 5 days a week. Also there is "About USDS" maybe not needed. We need to preserve all substantive info, remove boilerplate like EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions. The posting includes "Why Join Us", "Diversity & Inclusion", "USDS Reasonable Accommodation", "Job Information", etc. Some of that may be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Why Join Us" maybe not boilerplate but could be considered fluff; but we need to preserve substantive info. However we should only include sections when posting has real specific content. "Why Join Us" is generic motivational; maybe we can omit as not required headings. The allowed headings list does not include "Why Join Us". So we should not create a heading for it. Similarly "Diversity & Inclusion" maybe not needed. "USDS Reasonable Accommodation" maybe legal; remove. "Job Information" includes Pay Transparency etc; we already have Pay and Benefits sections. So we will extract: - About the role: content from "About the team" paragraph(s). Could also include "As Pangle expands into the U.S. market..." etc. We'll combine. - Responsibilities: list items. - Qualifications: maybe combine Minimum and Preferred under Qualifications heading. Could also separate Requirements? The instruction includes Requirements as possible heading. But we have Qualifications. We'll put Qualifications. - Benefits: list of benefits. - Pay: compensation range. - Schedule: mention shift to fully in-person schedule up to 5 days a week. We must not repeat job title as heading. No Job ID. We must not include placeholder text like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to include details from About the team: "Pangle is the ad network of TikTok for Business, helping mobile developers accelerate growth, deliver engaging ad experiences, and maximize revenue by accessing TikTok's global advertising demand. Operating in more than 36 countries and regions, Pangle has built a strong reputation for driving measurable results for app partners worldwide. As Pangle expands into the U.S. market, we're building our advertising platform from the ground up — tackling exciting new challenges in large-scale systems, optimization, and machine learning. Join us to shape the future of mobile monetization and grow your career in a fast-moving, global team." Also maybe include "About USDS" but that's separate entity; maybe not needed for role. Could be considered boilerplate? It's about USDS Joint Venture; might be relevant to role? The posting includes that as separate section; but we are not required to include a heading for it. Could we include it under About the role? Might be too much. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we omit the USDS section, we lose substantive info about the joint venture. However the allowed headings list does not have a slot for that; but we could still include a

  under About the role? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings if needed, but better to stick to those. However we need to preserve all substantive info; we could embed USDS info within About the role as a paragraph. That would preserve it. Similarly "Why Join Us" etc could be omitted? That would lose some substantive info about company values. But maybe considered fluff; but instruction says preserve ALL substantive information; "Why Join Us" is substantive? It's motivational but still part of posting. However we could incorporate into About the role as well. But we must not create sections with filler/placeholder text. "Why Join Us" is not filler; it's substantive. But we don't have a heading for it; we could incorporate as a paragraph under About the role. Similarly "Diversity & Inclusion" could be incorporated. But we need to avoid duplication. Let's extract all substantive paragraphs: - About the team (Pangle description) - About USDS TikTok USDS Joint Venture LLC description (safety, data privacy, etc.) - Why Join Us (inspiring creativity, mission, values) - Diversity & Inclusion (commitment to inclusive space) - USDS Reasonable Accommodation (maybe legal; could be considered boilerplate? It's about accommodation; could be kept but maybe considered legal. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. This is about reasonable accommodation, which is related to EEO; likely considered boilerplate. So we can remove. - Job Information: includes Pay Transparency (we will extract Pay and Benefits), also includes Los Angeles County Fair Chance Ordinance (legal). That's likely boilerplate; remove. Thus we keep: About the team, About USDS, Why Join Us, Diversity & Inclusion, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to map to allowed headings: About the role (we can put all descriptive paragraphs under that). Responsibilities, Qualifications, Benefits, Pay, Schedule. We should not create Requirements or Skills headings if no specific content; we have Qualifications covering both minimum and preferred; we could also split into Requirements (minimum) and Skills (preferred) but not needed. We'll output:

  About the role

  ... combined paragraphs ...

  Responsibilities

  • ... each bullet ...

  Qualifications

  We could split into Minimum and Preferred as subheadings? Not allowed headings but we could use

  with bold? Better to keep as

  with lists. Use

  • for list. We'll have two lists: Minimum Qualification(s) and Preferred Qualification(s). Could wrap each in

    with heading? Not allowed headings besides those; but we can still use

    to introduce then

    . That's fine. Thus:

    Qualifications

    Minimum Qualification(s):

    ...

    Preferred Qualification(s):

    ...
    But we need to avoid adding extra headings; using inside

    is okay. Benefits: list of benefits from paragraph: "Employees have day one access to medical, dental, and vision insurance, a 401(k) savings plan with company match, paid parental leave, short-term and long-term disability coverage, life insurance, wellbeing benefits, among others. Employees also receive 10 paid holidays per year, 10 paid sick days per year and 17 days of Paid Personal Time (prorated upon hire with increasing accruals by tenure)." We'll put as

    • each item. Pay: compensation range: "$129960 - $246240 annually." Also note that compensation may vary etc. We'll include that as prose. Schedule: "As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." We'll output as

      . Now ensure we don't include any boilerplate like "EEO", etc. Let's craft the About the role paragraph combining: Pangle is the ad network of TikTok for Business, helping mobile developers accelerate growth, deliver engaging ad experiences, and maximize revenue by accessing TikTok's global advertising demand. Operating in more than 36 countries and regions, Pangle has built a strong reputation for driving measurable results for app partners worldwide. As Pangle expands into the U.S. market, we're building our advertising platform from the ground up — tackling exciting new challenges in large-scale systems, optimization, and machine learning. Join us to shape the future of mobile monetization and grow your career in a fast-moving, global team. TikTok USDS Joint Venture LLC is dedicated to the safety and security of millions of Americans who create, discover, and connect with what they love on the apps we operate. The Joint Venture has been established in compliance with the Executive Order signed by President Trump on September 25, 2025. Our foundation is a comprehensive data privacy and cybersecurity program we operate under defined safeguards to protect national security and secure U.S. user data, apps and the algorithm. We safeguard the U.S. content ecosystem, holding decision-making authority for trust and safety policies and moderation. USDS Joint Venture helps ensure Americans can continue to express their creativity, discover new hobbies and interests, and build thriving communities and businesses on a global scale. On-site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real-time decision-making, team development, and integrated execution. As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week. Why Join Us: Inspiring creativity is at the core of TikTok's mission. Our innovative product is built to help people authentically express themselves, discover and connect – and our global, diverse teams make that possible. Together, we create value for our communities, inspire creativity and bring joy - a mission we work towards every day. We strive to do great things with great people. We lead with curiosity, humility, and a desire to make impact in a rapidly growing tech company. Every challenge is an opportunity to learn and innovate as one team. We're resilient and embrace challenges as they come. By constantly iterating and fostering an "Always Day 1" mindset, we achieve meaningful breakthroughs for ourselves, our company, and our users. When we create and grow together, the possibilities are limitless. Join us. Diversity & Inclusion: TikTok is committed to creating an inclusive space where employees are valued for their skills, experiences, and unique perspectives. Our platform connects people from across the globe and so does our workplace. At TikTok, our mission is to inspire creativity and bring joy. To achieve that goal, we are committed to celebrating our diverse voices and to creating an environment that reflects the many communities we reach. We are passionate about this and hope you are too. We could combine all into one big paragraph but that may be too long; but it's okay. Now Responsibilities list: - Design and implement highly available ad-serving systems capable of handling large-scale traffic with low latency. - Develop and optimize delivery strategies for various ad placements to maximize monetization efficiency. - Improve core algorithms and systems across ad recall, ranking, bidding, and traffic allocation. - Leverage large-scale advertising data to enhance user- and ad-level monitoring systems, and build analytical and optimization tools for campaign performance. - Communicate cross-functionally across various teams, organizations and internal and external stakeholders to drive engineering efforts. Lead innovation efforts, and bring in new ideas and technologies.