Data Center Development Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. First, we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "About Meta:"? Might be considered boilerplate? It's about company description; maybe we can keep as part of About the role? The instruction: "Prefer a few substantive sections over many thin ones." We need to include sections only when posting has real specific content. We have content: description of role, responsibilities, minimum qualifications, preferred qualifications, travel requirement, compensation (Pay), benefits mention, schedule? Not explicit schedule besides travel 25-50% travel. No explicit schedule like full-time, part-time. So we may not include Schedule unless we have explicit schedule info. Travel is not schedule; it's travel requirement. Could be part of Responsibilities? Not exactly. Might be part of Requirements? Not sure. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." We have Pay: "$154,000/year to $200,000/year + bonus + equity + benefits". So we can include Pay section. Benefits: "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's vague but mentions benefits. It says benefits exist but not details. Is that enough? It says "Meta offers benefits." That's real content, albeit generic. Should we include Benefits section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, albeit not detailed. I'd include Benefits section with that sentence. Schedule: Not explicit. Travel 25-50% travel could be considered schedule? Not exactly schedule of work hours. Probably we should not include Schedule. Now sections: - About the role: we have introductory paragraph describing role. Could be used as About the role. - Responsibilities: list of responsibilities bullet points. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe we can extract skills from qualifications? But we have no explicit skills list besides project management tools. Could combine into Skills section? The instruction: "Prefer a few substantive sections over many thin ones." Might combine Skills into Requirements or Qualifications. But we have separate headings allowed. We could include Skills if we have content: experience with project management tools, etc. That's in Minimum Qualifications: "Experience with a range of project management tools and software, (eg. Google Suite, Excel, project management software, PowerPoint, etc)". That's a skill. Also maybe "Experience in managing multiple projects and coordinating with internal staff and external consultants, vendors and other stakeholders". That's also skill. Could put those under Skills. But we also have Minimum Qualifications includes degree, experience, etc. Those are qualifications not skills. So we could have Requirements (minimum qualifications) and Qualifications (preferred qualifications). Skills could be derived from the experience with tools etc. However we might avoid thin sections. Perhaps we can omit Skills and put those details under Requirements or Qualifications. Let's decide: We'll include About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Pay, Benefits. That's six sections. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO statements, etc. Also remove "About Meta:" paragraph? That's company description; maybe we can keep as part of About the role? But it's not about the role; it's about Meta. Could be considered boilerplate? It's not EEO but it's generic company description. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove company description. However "About Meta:" might be considered boilerplate but it's not legal/EEO. Might be okay to keep. But we already have About the role section; we could incorporate that description there. However the "About Meta:" paragraph is separate from role description. It might be considered part of About the role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role is a heading we can use for role description. The company description could be placed under About the role as prose, but it's not about the role. Might be better to omit it to avoid thin sections? But we need to preserve ALL substantive information; does company description count as substantive? It's about Meta, not the role. Might be considered boilerplate but not excluded. I'd keep it maybe as a separate

  before sections? But we cannot add extra headings not listed. Could just include it as a

  before the first heading? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs outside sections. But they said use headings for sections; we can have prose outside sections. However they said "Prefer a few substantive sections over many thin ones." Might be okay to include a brief intro paragraph before sections. But the role description already includes a paragraph: "Meta designs, builds, and operates some of the most advanced and efficient data center infrastructure in the world.... We are seeking an experienced Data Center Development Manager..." That's substantive about the role. So we can use that as About the role content. Thus we can ignore the "About Meta:" paragraph. Now let's extract content. About the role: The first paragraph up to "Data Center Development Manager Responsibilities:"? Actually the posting: "Meta designs, builds, and operates some of the most advanced and efficient data center infrastructure in the world. Ensuring that this infrastructure is available at the right place, at the right time, and at the right scale is critical to Meta's ability to serve billions of users across its family of apps and services.We are seeking an experienced Data Center Development Manager to join the Global Site Development organization, where you will play a central role in enabling the data center buildout of the future. This is a high-impact, highly collaborative position where you'll work alongside partners in site selection, infrastructure planning, and construction – bringing together diverse perspectives and balancing speed-to-market, project flexibility, and capital efficiency to deliver projects that keep Meta's data center portfolio ahead of demand. If you're a results-driven project manager who thrives at the intersection of strategy and execution, loves solving complex development problems with great people, and want your work to have tangible, world-scale impact, we'd love to hear from you." That's the role description. We'll put that in

  under

  About the role

  . Responsibilities: After "Data Center Development Manager Responsibilities:" there is a list of responsibilities separated by line breaks? Let's extract: - Drive the entitlements process (e.g., zoning, land use permitting) to ensure accurate and timely submission and execution of the necessary site entitlements and permits to meet project timelines - Lead the diligence and development process to vet prospective sites and assess site risks and opportunities by analyzing regional and site - specific information pertaining to (i) permitting and land use data (ii) information regarding federal, state and local taxes and incentives (iii) data on energy (including renewable energy), water and wastewater availability and cost (iv) network connectivity (v) natural hazard, floodplain and climatological data (vi) legal, physical risk and financial implications - Take the lead role in organizing communications by creating scalable processes with and tracking progress towards on-time delivery of projects by key internal and external stakeholders in support of the site selection effort, including capacity planning, data center design and construction, external consulting partners, network engineering, legal, tax, policy and finance - Work with Site Selection Manager and other key project team members to ensure alignment among all internal stakeholders and to find smart ways to overcome obstacles in the site development process - Support the preparation of project recommendations for presentation to management for approval - Support the development of Meta's near and long-term data center location and leased portfolio strategy - Support a portfolio of existing sites under construction or in operations to facilitate on time and quality delivery and development of the site that meets permit requirements and local expectations - Track and monitor ongoing site development including agreement management - Develop scalable, efficient tools and processes to improve delivery and communication for data center site development Also "This role requires 25-50% travel" appears after responsibilities? Actually after responsibilities list, before Minimum Qualifications: "This role requires 25-50% travel". That's not a responsibility but a requirement. Could be placed under Requirements or maybe a separate note. We'll treat as part of Requirements (maybe under Minimum Qualifications). We'll include it as a bullet under Requirements. Now Minimum Qualifications: bullet list: - Bachelor's degree in a directly related field, or equivalent practical experience - Bachelor's degree in Business, Planning, Engineering, Science or Environmental management - 5+ years of site development experience, or equivalent experience managing large scale, complex infrastructure projects - Experience in managing multiple projects and coordinating with internal staff and external consultants, vendors and other stakeholders - Experience with a range of project management tools and software, (eg. Google Suite, Excel, project management software, PowerPoint, etc) Note there is some redundancy: first two bullet both about Bachelor's degree; could combine but we must preserve all info. We'll keep both as separate bullets. Preferred Qualifications: - Experience in large and complex infrastructure projects - 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 - Advanced technical degree, law degree, or MBA - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Experience with planning, land use diligence and engineering, and entitlements processes Now Pay: "$154,000/year to $200,000/year + bonus + equity + benefits Individual compensation is determined by skills, qualifications, experience, and location. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, equity or sales incentives, if applicable." We need to preserve all substantive info. We'll put that as

  under Pay. Benefits: "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." We'll put that as

  under Benefits. Now we need to ensure we don't include any boilerplate like EEO statements etc. We'll remove the paragraph starting "About Meta:" and all the EEO stuff after that. Also remove "Please note that Meta may leverage artificial intelligence..." etc. That's also boilerplate about AI in hiring. Remove. Also remove "Meta is committed to providing reasonable accommodations..." etc. Remove. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Pay

  ...

  Benefits

  ...

  Make sure no extra whitespace issues. Now craft the content precisely. About the role paragraph: combine the sentences exactly as in posting, preserving punctuation. Let's copy: "Meta designs, builds, and operates some of the most advanced and efficient data center infrastructure in