Performance & Capacity Engineer - Capacity Planning Optimization(Technical Leadership)

We need to output HTML fragment with sections: About the role? Actually the posting includes description before responsibilities. 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 have content: description (intro) maybe "About the role". Then responsibilities list. Then Minimum Qualifications (Requirements). Then Preferred Qualifications (Qualifications? maybe Skills). There's also "About Meta" but that's boilerplate? It's about company, maybe we can include as "About the role"? Actually "About Meta" is generic company description; could be considered boilerplate but maybe we keep as part of role description? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Meta" is not exactly legal boilerplate; it's company overview. Might be okay to keep as part of description. But we need to avoid duplication. We have Pay: "$219,000/year to $301,000/year + bonus + equity + benefits". That's specific pay range, so we should include Pay section. Schedule: "This position is full-time." That's schedule info, so include Schedule section. Benefits: mention "benefits" but not detailed; they say "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's vague; not specific benefits listed. According to rule: never create Benefits section unless posting actually states them. It does mention benefits generically but not specific. Might be considered not specific enough; better to omit Benefits section. Skills: Not explicitly listed; we have qualifications and preferred qualifications. Could map to Skills section? But we have Requirements (minimum qualifications) and Qualifications (preferred). The instruction says use headings like Requirements, Qualifications, Skills. We can put Minimum Qualifications under

Requirements

. Preferred Qualifications under

Qualifications

. Skills maybe not needed. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the responsibilities bullet points, qualifications bullet points, etc. We must not repeat job title as heading. The page already shows it, so we don't add a heading for "Performance & Capacity Engineer". Good. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

Meta is seeking a Performance & Capacity Engineer to join the Capacity Planning Optimization Engineering team to lead software systems and process design. You will build and optimize infrastructure capacity planning covering all of Meta, in one of our largest transformations to date of how we plan and manage infrastructure capacity. This is a hands on leadership role, building some of complex parts of the system yourself while leading other engineers and non-technical contributors. You will be in one of the most cross-functional roles at the company, with the opportunity to work with a variety of engineering and business teams at the intersection of all Meta products and services (Facebook, Instagram, WhatsApp, etc), all physical infrastructure (Servers, Data Centers, Network), and product business goals (AI, Metaverse, etc). You will be uniquely positioned to optimize these capacity plans at strategic levels with company level impact, with your output used at the CxO level for key strategic decisions, as well as providing execution guidance for infrastructure and product teams.To do this, you will partner across technical and business orgs to design the right solutions and lead engineers to build effective technical and process solutions to transform Meta's capacity planning process to be software driven, highly flexible, agile, and ROI Driven. You will connect business strategy with software-driven modeling of detailed service, platform, and infrastructure considerations for executable plans.Contribute to building and scaling Meta's global infrastructure and internet services! This position is full-time.

Then

Responsibilities

with

• ... each bullet. Responsibilities list from posting: - Own infrastructure capacity planning for all of Meta: all software products/services and plans for how to scale server and data center resources most efficiently - Partner across the engineering technical landscape to optimize at the intersection of hardware, infrastructure, and software. Work closely with software service owners, Production Engineering, Server Hardware Engineering, Server Supply Chain, Network Engineering, Data Center Design, Operations, and Planning teams to find optimal ways to scale our infrastructure and place our services - Design and help build software systems to build scalable, reliable planning systems to connect business strategy with detailed technical execution including regional and temporal bin-packing, optimal service placement, traffic shifts and service migrations, efficient hardware refresh, etc - Effectively lead large engineering efforts while implementing complex parts of the system and process design yourself - Partner with Finance and business teams to balance cost efficiency with technical and product considerations - Work cross-functionally to define problem statements, collect data, build software driven models and make recommendations to drive change and optimization at strategic levels We need to preserve all; ensure no duplication. Then

  Requirements

  with Minimum Qualifications list: - Bachelor's degree in Computer Science, Computer Engineering, relevant technical field, or equivalent practical experience - 10+ years of experience in Performance, Capacity, or software engineering - Proficient in Python, C++, or other coding languages and designing large scale software systems - Demonstrated success leading large engineering projects and initiatives. Defining goals, managing ambiguity, inspiring and leading other engineers and - Demonstrated success leading large engineering projects and initiatives, including defining goals, managing ambiguity, and inspiring and leading other engineers and non-technical contributors Note there is duplication: two similar lines about leading large engineering projects. We should keep both? The instruction says remove duplicated lines. So we need to deduplicate. The two lines are slightly different but essentially same. We'll keep one combined maybe? But we must preserve all substantive information; removing duplicate is allowed. So we can keep one line that captures both: "Demonstrated success leading large engineering projects and initiatives, including defining goals, managing ambiguity, inspiring and leading other engineers and non-technical contributors". That covers both. Thus Requirements list: - Bachelor's degree in Computer Science, Computer Engineering, relevant technical field, or equivalent practical experience - 10+ years of experience in Performance, Capacity, or software engineering - Proficient in Python, C++, or other coding languages and designing large scale software systems - Demonstrated success leading large engineering projects and initiatives, including defining goals, managing ambiguity, inspiring and leading other engineers and non-technical contributors Then

  Qualifications

  with Preferred Qualifications list (deduplicate duplicates). Preferred qualifications list from posting: - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies - Experience and interest in building "Zero to One" - building systems and processes from scratch with ambiguous requirements and goals - Experience with mathematical optimization and solvers - Experience with technical infrastructure planning or capacity planning Note there are duplicates: "Demonstrated ability to integrate AI tools..." appears twice; "Experience adhering to and implementing responsible, ethical AI practices..." appears twice; "Demonstrated ongoing AI skill development..." appears twice. We'll deduplicate. Thus Qualifications list: - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies - Experience and interest in building "Zero to One" - building systems and processes from scratch with ambiguous requirements and goals - Experience with mathematical optimization and solvers - Experience with technical infrastructure planning or capacity planning Then

  Pay

  with

  $219,000/year to $301,000/year + bonus + equity + benefits

  Then

  Schedule

  with

  Full-time

  We might also include a brief "About the role" paragraph at top; we already have intro paragraph. Could wrap that in

  without heading. The instruction: Use

  for section headings (e.g. About the role, Responsibilities...). So we could add

  About the role

  before the intro paragraph. But we already have intro paragraph describing role; we could either not add heading or add heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't mandate we must include About the role heading, but we can if we have content. We have content for role description; we could put that under

  About the role

  . However we already have a paragraph that includes "Meta is seeking a Performance & Capacity Engineer...". That is about the role. So we could wrap that in

  About the role

  then

  ...

  . That seems appropriate. But we must not repeat the job title as a heading; the heading "About the role" is fine. Thus final HTML:

  About the role

  Meta is seeking a Performance & Capacity Engineer to join the Capacity Planning Optimization Engineering team to lead software systems and process design. You will build and optimize infrastructure capacity planning covering all of Meta, in one of our largest transformations to date of how we plan and manage infrastructure capacity. This is a hands on leadership role, building some of complex parts of the system yourself while leading other engineers and non-technical contributors. You will be in one of the most cross-functional roles at the company, with the opportunity to work with a variety of engineering and business teams at the intersection of all Meta products and services (Facebook, Instagram, WhatsApp, etc), all physical infrastructure (Servers, Data Centers, Network), and product business goals (AI, Metaverse, etc). You will be uniquely positioned to optimize these capacity plans at strategic levels with company level impact, with your output used at the CxO level for key strategic decisions, as well as providing execution guidance for infrastructure and product teams.To do this, you will partner across technical and business orgs to design the right solutions and lead engineers to build effective technical and process solutions to transform Meta's capacity planning process to be software driven, highly flexible, agile, and ROI Driven. You will connect business strategy with software-driven modeling of detailed service, platform, and infrastructure considerations for executable plans.Contribute to building and scaling Meta's global infrastructure and internet services! This position is full-time.

  Responsibilities

  • Own infrastructure capacity planning for all of Meta: all software products/services and plans for how to scale server and data center resources most efficiently
  • Partner across the engineering technical landscape to optimize at the intersection of hardware, infrastructure, and software. Work closely with software service owners, Production Engineering, Server Hardware Engineering, Server Supply Chain, Network Engineering, Data Center Design, Operations, and Planning teams to find optimal ways to scale our infrastructure and place our services
  • Design and help build software systems to build scalable, reliable planning systems to connect business strategy with detailed technical execution including regional and temporal bin-packing, optimal service placement, traffic shifts and service migrations, efficient hardware refresh, etc
  • Effectively lead large engineering efforts while implementing complex parts of the system and process design yourself
  • Partner with Finance and business teams to balance cost efficiency with technical and product considerations
  • Work cross-functionally to define problem statements, collect data, build software driven models and make recommendations to drive change and optimization at strategic levels

  Requirements

  • Bachelor's degree