Manager, Software Engineering - Data Platform

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the "Pay Transparency Disclosure" maybe part of Pay? Actually they gave salary range, so we can include Pay section with that range. Benefits: they list many benefits; we can include Benefits section. Schedule: they said full time role that can be held from US hubs or remotely in US. That's schedule info (full-time, location). So we can include Schedule section. Responsibilities: bullet list under "What you’ll do at Figma:" includes multiple items. We'll put those as

• . Requirements: bullet list under "We'd love to hear from you if you have:" includes required qualifications. We'll put those as Requirements. Qualifications/Skills: There's also "While it's not required, it's an added plus if you also have:" which could be Skills or Preferred Qualifications. We could treat as Skills section. Or maybe Qualifications includes both required and preferred? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have an introductory paragraph about Figma and mission; could be About the role. We'll put that as About the role. Responsibilities: the bullet list. Requirements: the required bullet list. Skills: the preferred bullet list (added plus). Could also be Qualifications but we already used Requirements for required; we can put Skills for preferred. Benefits: list of benefits. Pay: salary range. Schedule: full-time, location info. We must not include filler like "commensurate with experience". Not present. We must not include boilerplate like EEO etc. Remove those paragraphs. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can reformat. We need to ensure we don't lose any substantive info: The introductory paragraphs about Figma's mission, Data Platform, role description, etc. We'll capture them in About the role maybe as prose. Let's extract substantive content: - Intro: "Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all. Figma’s platform helps teams bring ideas to life—whether you're brainstorming, creating a prototype, translating designs into code, or iterating with AI. From idea to product, Figma empowers teams to streamline workflows, move faster, and work together in real time from anywhere in the world. If you're excited to shape the future of design and collaboration, join us! Figma is a data-driven organization, and Data Platform builds the foundation that makes that possible. The platform powers everything from core business metrics and product analytics to the applied AI and experimentation systems that teams across the company rely on to build and make decisions. In this role, you'll lead engineers across Data Platform through their next phase of scale, setting technical direction, growing the team, and partnering broadly across the company. This is a full time role that can be held from one of our US hubs or remotely in the United States." That's About the role. - Responsibilities bullet list (under "What you’ll do at Figma:"): * Lead and grow a team of engineers building and operating Figma's data platform, owning delivery, technical direction, and team health * Set the roadmap and technical strategy for your sub area, and provide hands on technical leadership where the team needs it * Drive the reliability, scalability, and forward strategy of the platform as adoption grows across the engineering and product organization * Hire, grow, and coach engineers and tech leads, raising the bar and building a healthy, inclusive, high-performing team * Partner with Data Science, Product, Finance, and Engineering to identify the highest-leverage priorities and drive alignment * Make sound build versus buy decisions, including evaluating and managing platform vendors where it makes sense * Keep delivery predictable while balancing near-term execution with long-term platform investment - Requirements bullet list (under "We'd love to hear from you if you have:"): * 3+ years managing engineers, including senior ICs or tech leads, with a track record of building and scaling high-performing teams * Demonstrated experience building and scaling data platform or data infrastructure systems in a production, online environment * A strong software engineering background with senior or staff-level technical depth before moving into management, and enough current depth to set direct technical direction * Strong partnership mentality and the ability to manage multiple cross-functional stakeholder groups such as Data Science, Product, Finance, and Engineering * Ability to set technical direction, drive alignment, and prioritize clearly under ambiguity, paired with strong written communication - Preferred/Skills bullet list (under "While it's not required, it's an added plus if you also have:"): * Expertise in large-scale data processing systems, including batch, streaming, or applied AI and ML workloads * Familiarity with experimentation or feature flagging platforms * A track record of evaluating and managing vendor relationships * A demonstrated ability to develop tech leads and scale hiring at pace - Benefits: list after "Figma offers equity to employees, as well as a competitive package of additional benefits, including health, dental, and vision coverage; retirement benefits with company contributions; parental leave and reproductive or family planning support; mental health and wellness benefits; and paid time off. Figma provides paid sick leave, holidays, and other leave benefits in compliance with applicable federal, state, and local laws, including the requirements of the Washington Minimum Wage Act and related regulations. Exempt employees are eligible for employer‑provided paid flexible PTO in addition to flexible paid sick leave. PTO is subject to manager approval. Additional benefits may include company recharge days, cell phone and home internet reimbursements, and a number of lifestyle spending accounts. Figma also offers sales incentive compensation for most sales roles and an annual bonus plan for eligible non-sales roles. All compensation and benefits are subject to applicable plan terms and may be modified by Figma at any time, consistent with applicable law." We need to capture all that as Benefits. - Pay: "Annual Base Salary Range: $258,000—$376,000 USD" - Schedule: "This is a full time role that can be held from one of our US hubs or remotely in the United States." Already included in About the role maybe but we can also put Schedule section with that detail. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put that sentence in both About the role and Schedule, we duplicate. Better to keep it only once. Since About the role already includes that sentence, we could omit Schedule section, or we could move that sentence to Schedule and remove from About the role. But About the role currently includes that sentence as part of description; we could keep it there and not have Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (full time, location). So we could create Schedule section with that info, and we could remove it from About the role to avoid duplication. But we must preserve all substantive information; we can move it. So About the role would not contain that sentence; we would put it in Schedule. Thus we need to adjust About the role to exclude the schedule sentence. Let's rewrite About the role without that sentence. About the role paragraph: "Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all. Figma’s platform helps teams bring ideas to life—whether you're brainstorming, creating a prototype, translating designs into code, or iterating with AI. From idea to product, Figma empowers teams to streamline workflows, move faster, and work together in real time from anywhere in the world. If you're excited to shape the future of design and collaboration, join us! Figma is a data-driven organization, and Data Platform builds the foundation that makes that possible. The platform powers everything from core business metrics and product analytics to the applied AI and experimentation systems that teams across the company rely on to build and make decisions. In this role, you'll lead engineers across Data Platform through their next phase of scale, setting technical direction, growing the team, and partnering broadly across the company." That covers all except schedule. Now Schedule section: "This is a full time role that can be held from one of our US hubs or remotely in the United States." Now Benefits section: we need to include all benefits details as prose or list? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. Benefits is a list; we can make a

    • for each benefit item. However the benefits paragraph includes many items separated by semicolons and sentences. We could split into list items: health, dental, and vision coverage; retirement benefits with company contributions; parental leave and reproductive or family planning support; mental health and wellness benefits; paid time off; paid sick leave, holidays, and other leave benefits; employer‑provided paid flexible PTO; company recharge days; cell phone and home internet reimbursements; lifestyle spending accounts; sales incentive compensation for most sales roles; annual bonus plan for eligible non-sales roles. Also note that Figma offers equity to employees. That's also a benefit. Also mention that all compensation and benefits are subject to applicable plan terms and may be modified. We should preserve all substantive information; we can keep as prose if we want, but instruction says use
      • for any list of benefits. So we should make a list. We need to ensure we don't lose any detail: equity, health/dental/vision, retirement benefits with company contributions, parental leave and reproductive or family planning support, mental health and wellness benefits, paid time off, paid sick leave, holidays, other leave benefits (compliance with laws), exempt employees eligible for employer‑provided paid flexible PTO in addition to flexible paid sick leave, PTO subject to manager approval, additional benefits may include company recharge days, cell phone and home internet reimbursements, lifestyle spending accounts, sales incentive compensation for most sales roles, annual bonus plan for eligible non-sales roles, all compensation and benefits subject to applicable plan terms and may be modified. We could make list items for each distinct benefit. Might be many but okay. Pay section: just the salary range as

        . Now we need to output only HTML fragment, no /, no markdown. Let's craft:

        About the role

        Figma is growing our team of passionate creatives and builders on a mission to make design accessible to all. Figma’s platform helps teams bring ideas to life—whether you're brainstorming, creating a prototype, translating designs into code, or iterating with AI. From idea to product, Figma empowers teams to streamline workflows, move faster, and work together in real time from anywhere in the world. If you're excited to shape the future of design and collaboration, join us! Figma is a data-driven organization, and Data Platform builds the foundation that makes that possible. The platform powers everything from core business metrics and product analytics to the applied AI and experimentation systems that teams across the company rely on to build and make decisions. In this role, you'll lead engineers across Data Platform through their next phase of scale, setting technical direction, growing the team, and partnering broadly across the company.

        Responsibilities

        • Lead and grow a team of engineers building and operating Figma's data platform, owning delivery, technical direction, and team health
        • Set the roadmap and technical strategy for your sub area, and provide hands on technical leadership where the team needs it