Construction Metro Director
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Input Text:**
- It's a Microsoft job posting for "Metro Construction Director" role
- Contains sections: Overview, Responsibilities, Qualifications, Preferred Qualifications, Pay/Compensation, Application period, EEO statement, accommodation info
- I need to extract only substantive content, remove boilerplate (EEO, equal opportunity, scam warning, application instructions, etc.)
- Determine which sections to include based on actual content, avoiding empty/placeholder sections
- Use specified HTML tags: `
` for headings, `- ` for lists, `
` for prose
- No job title heading (already on page)
- Pay section: there IS pay info: "The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year." So Pay section IS warranted.
- Schedule: I don't see specific schedule info, just "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." That's application period, not work schedule. I should probably not create a Schedule section unless there's actual schedule info. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated. Schedule? Not really. Benefits? There's a link: "Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay" but no actual benefits listed. So I should not create a Benefits section. The rule says "never emit a heading followed by filler/placeholder text". So I'll skip Benefits and Schedule.
- Qualifications: Has "Required/minimum qualifications" and "Background Check Requirements", and "Qualifications Preferred". I'll structure these carefully.
- Responsibilities: List of duties.
- About/Overview: Present.
Let's outline sections I'll include:
- About the role (from Overview)
- Responsibilities
- Qualifications (Required/minimum)
- Preferred qualifications (or I can merge into Qualifications section, but the posting has "Required/minimum qualifications" and "Additional Or Preferred Qualifications" - I'll treat as two subsections or keep under Qualifications with clear headings. The rules say use `
` for section headings, examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Requirements" and "Qualifications" are separate. I'll use "Requirements" for the minimum/background check, and "Qualifications" for the preferred? Actually the posting says "Required/minimum qualifications" and "Additional Or Preferred Qualifications". I'll map: "Requirements" section for minimum/background, "Qualifications" for the degree+experience part. But the rules list "Requirements, Qualifications" as possible headings. I'll use `Requirements
` for the minimum qualifications + background check, and maybe not create a separate "Qualifications" heading if it duplicates. Let's read carefully: The posting has "Qualifications Required/minimum qualifications..." and then "Additional Or Preferred Qualifications...". I'll create "Requirements" section covering the minimum quals and background check. I'll skip a separate "Qualifications" heading since the content is split between "Required/minimum" and "Preferred". Actually, the rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can pick and choose. I'll do: About the role, Responsibilities, Requirements, Pay. I won't do Qualifications separately if I can fold it into Requirements or vice versa, but the content under "Qualifications" is substantial. Let's see: "Required/minimum qualifications Bachelor's Degree... AND 12+ years... OR equivalent experience. Background Check Requirements..." Then "Additional Or Preferred Qualifications...". I'll create "Requirements" section with the min quals and background check, and maybe "Preferred qualifications" as a sub-list or under a separate heading. But the rules say only include sections with real content. I'll do "Requirements" covering both min and preferred, or split into "Requirements" and "Preferred qualifications". I think I'll use "Requirements" for the mandatory part, and list preferred as a bullet list under it or as a separate `Preferred qualifications
`. The rules don't forbid using headings not in the list, but they give examples. I'll stick to the spirit: use `` for major sections, only when there's content. I'll do: About the role, Responsibilities, Requirements, Pay. I'll fold preferred quals into Requirements or as a note. Actually, I'll read the exact text: "Qualifications Required/minimum qualifications... Background Check Requirements..." then "#COICareers | #EPCCareers | #DCDCareers Construction Project Management M6 - The typical base pay range..." then "This position will be open for a minimum of 5 days..." then EEO and accommodation. I'll ignore the hashtags, EEO, accommodation, application instructions.
Let's extract substantive blocks:
**About the role / Overview:**
"Microsoft Cloud Operations + Innovation (CO+I) builds and operates the infrastructure that supports Microsoft’s global cloud services. Our focus is smart growth, high efficiency, and delivering trusted experiences to customers and partners worldwide. The Metro Construction Director role offers the opportunity to lead complex, large-scale construction programs that enable reliable, secure, and scalable services for customers around the world. We are looking for an experienced construction leader to help build the infrastructure that powers some of the world’s largest online services. Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond. In alignment with our Microsoft values, we are committed to cultivating an inclusive work environment for all employees to positively impact our culture every day."
**Responsibilities:** (long list, I'll extract as bullet points)
- Oversees the team's deployment of large-scale, campus, and/or regionally-based delivery solutions while also aligning with regional and global leaders.
- Analyzes and recommends innovative delivery options utilizing best practices and trends, supports the development and implementation of all organizational procedures and standards, and ensures they are followed by all team members and vendors.
- Provides direction and coaching to internal and external partners to help resolve complex issues that may significantly impact global construction projects.
- Reviews and provides feedback to the team regarding resource procurement, allocation, and inventory.
- Leads the team's accountability for on-schedule delivery of multiple projects by ensuring project progress reports including scope, schedule, and budget are provided.
- Leads and drives coordination for meetings and activities with vendors, cost managers, and/or owner/architect/contractors.
- Engages, advises, and collaborates with other internal teams. Manages and advocates for safe worksites by adhering to organizational and industry procedures.
- Establishes, reviews, approves, and communicates risk mitigation goals and develops metrics, dashboards and/or scorecards to drive progress.
- Directs and oversees the management of vendors, ensuring compliance with contracts and prior audit results.
- In addition, this role has people management responsibilities, including coaching team members, supporting career development, setting priorities, creating an inclusive team environment, executing projects, and managing performance.
**Requirements:** (minimum qualifications + background check)
- Required/minimum qualifications: Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 12+ years related experience OR equivalent experience.
- Background Check Requirements: Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include, but are not limited to the following specialized security screenings: Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter.
**Preferred qualifications** (from "Additional Or Preferred Qualifications"):
- Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 15+ years related experience OR equivalent experience.
- 15+ years experience working on data center projects.
- 10+ years project management experience.
- 10+ years people management experience.
**Pay:**
- The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year.
**Application period:** "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." I could fold this into a short paragraph, but the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is minor metadata. I'll fold it into a
at the end or beginning, but not as a section heading. The rules also say "Remove... application instructions." So I'll probably drop the application period or fold it minimally. I'll maybe include it as a short
after Pay, but the rule says "fold minor metadata into a short
or drop it." I'll drop it to keep it clean, or fold it into a
without a heading. I'll see. The rule: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put a
with that info, but it's minor. I'll probably just drop it, or include it as a brief
at the very end. I'll decide during output.
**Removed:** EEO statement, equal opportunity text, scam warning, hashtags, "Microsoft is an equal opportunity employer.", accommodation info, "If you need assistance...", the link at the end "Find additional benefits and pay information here: ..." (I'll keep the
` for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Input Text:** - It's a Microsoft job posting for "Metro Construction Director" role - Contains sections: Overview, Responsibilities, Qualifications, Preferred Qualifications, Pay/Compensation, Application period, EEO statement, accommodation info - I need to extract only substantive content, remove boilerplate (EEO, equal opportunity, scam warning, application instructions, etc.) - Determine which sections to include based on actual content, avoiding empty/placeholder sections - Use specified HTML tags: `
` for headings, `- ` for lists, `
` for prose
- No job title heading (already on page)
- Pay section: there IS pay info: "The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year." So Pay section IS warranted.
- Schedule: I don't see specific schedule info, just "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." That's application period, not work schedule. I should probably not create a Schedule section unless there's actual schedule info. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated. Schedule? Not really. Benefits? There's a link: "Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay" but no actual benefits listed. So I should not create a Benefits section. The rule says "never emit a heading followed by filler/placeholder text". So I'll skip Benefits and Schedule.
- Qualifications: Has "Required/minimum qualifications" and "Background Check Requirements", and "Qualifications Preferred". I'll structure these carefully.
- Responsibilities: List of duties.
- About/Overview: Present.
Let's outline sections I'll include:
- About the role (from Overview)
- Responsibilities
- Qualifications (Required/minimum)
- Preferred qualifications (or I can merge into Qualifications section, but the posting has "Required/minimum qualifications" and "Additional Or Preferred Qualifications" - I'll treat as two subsections or keep under Qualifications with clear headings. The rules say use `
` for section headings, examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Requirements" and "Qualifications" are separate. I'll use "Requirements" for the minimum/background check, and "Qualifications" for the preferred? Actually the posting says "Required/minimum qualifications" and "Additional Or Preferred Qualifications". I'll map: "Requirements" section for minimum/background, "Qualifications" for the degree+experience part. But the rules list "Requirements, Qualifications" as possible headings. I'll use `Requirements
` for the minimum qualifications + background check, and maybe not create a separate "Qualifications" heading if it duplicates. Let's read carefully: The posting has "Qualifications Required/minimum qualifications..." and then "Additional Or Preferred Qualifications...". I'll create "Requirements" section covering the minimum quals and background check. I'll skip a separate "Qualifications" heading since the content is split between "Required/minimum" and "Preferred". Actually, the rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can pick and choose. I'll do: About the role, Responsibilities, Requirements, Pay. I won't do Qualifications separately if I can fold it into Requirements or vice versa, but the content under "Qualifications" is substantial. Let's see: "Required/minimum qualifications Bachelor's Degree... AND 12+ years... OR equivalent experience. Background Check Requirements..." Then "Additional Or Preferred Qualifications...". I'll create "Requirements" section with the min quals and background check, and maybe "Preferred qualifications" as a sub-list or under a separate heading. But the rules say only include sections with real content. I'll do "Requirements" covering both min and preferred, or split into "Requirements" and "Preferred qualifications". I think I'll use "Requirements" for the mandatory part, and list preferred as a bullet list under it or as a separate `Preferred qualifications
`. The rules don't forbid using headings not in the list, but they give examples. I'll stick to the spirit: use `` for major sections, only when there's content. I'll do: About the role, Responsibilities, Requirements, Pay. I'll fold preferred quals into Requirements or as a note. Actually, I'll read the exact text: "Qualifications Required/minimum qualifications... Background Check Requirements..." then "#COICareers | #EPCCareers | #DCDCareers Construction Project Management M6 - The typical base pay range..." then "This position will be open for a minimum of 5 days..." then EEO and accommodation. I'll ignore the hashtags, EEO, accommodation, application instructions.
Let's extract substantive blocks:
**About the role / Overview:**
"Microsoft Cloud Operations + Innovation (CO+I) builds and operates the infrastructure that supports Microsoft’s global cloud services. Our focus is smart growth, high efficiency, and delivering trusted experiences to customers and partners worldwide. The Metro Construction Director role offers the opportunity to lead complex, large-scale construction programs that enable reliable, secure, and scalable services for customers around the world. We are looking for an experienced construction leader to help build the infrastructure that powers some of the world’s largest online services. Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond. In alignment with our Microsoft values, we are committed to cultivating an inclusive work environment for all employees to positively impact our culture every day."
**Responsibilities:** (long list, I'll extract as bullet points)
- Oversees the team's deployment of large-scale, campus, and/or regionally-based delivery solutions while also aligning with regional and global leaders.
- Analyzes and recommends innovative delivery options utilizing best practices and trends, supports the development and implementation of all organizational procedures and standards, and ensures they are followed by all team members and vendors.
- Provides direction and coaching to internal and external partners to help resolve complex issues that may significantly impact global construction projects.
- Reviews and provides feedback to the team regarding resource procurement, allocation, and inventory.
- Leads the team's accountability for on-schedule delivery of multiple projects by ensuring project progress reports including scope, schedule, and budget are provided.
- Leads and drives coordination for meetings and activities with vendors, cost managers, and/or owner/architect/contractors.
- Engages, advises, and collaborates with other internal teams. Manages and advocates for safe worksites by adhering to organizational and industry procedures.
- Establishes, reviews, approves, and communicates risk mitigation goals and develops metrics, dashboards and/or scorecards to drive progress.
- Directs and oversees the management of vendors, ensuring compliance with contracts and prior audit results.
- In addition, this role has people management responsibilities, including coaching team members, supporting career development, setting priorities, creating an inclusive team environment, executing projects, and managing performance.
**Requirements:** (minimum qualifications + background check)
- Required/minimum qualifications: Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 12+ years related experience OR equivalent experience.
- Background Check Requirements: Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include, but are not limited to the following specialized security screenings: Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter.
**Preferred qualifications** (from "Additional Or Preferred Qualifications"):
- Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 15+ years related experience OR equivalent experience.
- 15+ years experience working on data center projects.
- 10+ years project management experience.
- 10+ years people management experience.
**Pay:**
- The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year.
**Application period:** "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." I could fold this into a short paragraph, but the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is minor metadata. I'll fold it into a
at the end or beginning, but not as a section heading. The rules also say "Remove... application instructions." So I'll probably drop the application period or fold it minimally. I'll maybe include it as a short
after Pay, but the rule says "fold minor metadata into a short
or drop it." I'll drop it to keep it clean, or fold it into a
without a heading. I'll see. The rule: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put a
with that info, but it's minor. I'll probably just drop it, or include it as a brief
at the very end. I'll decide during output.
**Removed:** EEO statement, equal opportunity text, scam warning, hashtags, "Microsoft is an equal opportunity employer.", accommodation info, "If you need assistance...", the link at the end "Find additional benefits and pay information here: ..." (I'll keep the
` for prose - No job title heading (already on page) - Pay section: there IS pay info: "The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year." So Pay section IS warranted. - Schedule: I don't see specific schedule info, just "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." That's application period, not work schedule. I should probably not create a Schedule section unless there's actual schedule info. The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated. Schedule? Not really. Benefits? There's a link: "Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay" but no actual benefits listed. So I should not create a Benefits section. The rule says "never emit a heading followed by filler/placeholder text". So I'll skip Benefits and Schedule. - Qualifications: Has "Required/minimum qualifications" and "Background Check Requirements", and "Qualifications Preferred". I'll structure these carefully. - Responsibilities: List of duties. - About/Overview: Present. Let's outline sections I'll include: - About the role (from Overview) - Responsibilities - Qualifications (Required/minimum) - Preferred qualifications (or I can merge into Qualifications section, but the posting has "Required/minimum qualifications" and "Additional Or Preferred Qualifications" - I'll treat as two subsections or keep under Qualifications with clear headings. The rules say use `
` for section headings, examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "Requirements" and "Qualifications" are separate. I'll use "Requirements" for the minimum/background check, and "Qualifications" for the preferred? Actually the posting says "Required/minimum qualifications" and "Additional Or Preferred Qualifications". I'll map: "Requirements" section for minimum/background, "Qualifications" for the degree+experience part. But the rules list "Requirements, Qualifications" as possible headings. I'll use `Requirements
` for the minimum qualifications + background check, and maybe not create a separate "Qualifications" heading if it duplicates. Let's read carefully: The posting has "Qualifications Required/minimum qualifications..." and then "Additional Or Preferred Qualifications...". I'll create "Requirements" section covering the minimum quals and background check. I'll skip a separate "Qualifications" heading since the content is split between "Required/minimum" and "Preferred". Actually, the rule says use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can pick and choose. I'll do: About the role, Responsibilities, Requirements, Pay. I won't do Qualifications separately if I can fold it into Requirements or vice versa, but the content under "Qualifications" is substantial. Let's see: "Required/minimum qualifications Bachelor's Degree... AND 12+ years... OR equivalent experience. Background Check Requirements..." Then "Additional Or Preferred Qualifications...". I'll create "Requirements" section with the min quals and background check, and maybe "Preferred qualifications" as a sub-list or under a separate heading. But the rules say only include sections with real content. I'll do "Requirements" covering both min and preferred, or split into "Requirements" and "Preferred qualifications". I think I'll use "Requirements" for the mandatory part, and list preferred as a bullet list under it or as a separate `Preferred qualifications
`. The rules don't forbid using headings not in the list, but they give examples. I'll stick to the spirit: use `` for major sections, only when there's content. I'll do: About the role, Responsibilities, Requirements, Pay. I'll fold preferred quals into Requirements or as a note. Actually, I'll read the exact text: "Qualifications Required/minimum qualifications... Background Check Requirements..." then "#COICareers | #EPCCareers | #DCDCareers Construction Project Management M6 - The typical base pay range..." then "This position will be open for a minimum of 5 days..." then EEO and accommodation. I'll ignore the hashtags, EEO, accommodation, application instructions.
Let's extract substantive blocks:
**About the role / Overview:**
"Microsoft Cloud Operations + Innovation (CO+I) builds and operates the infrastructure that supports Microsoft’s global cloud services. Our focus is smart growth, high efficiency, and delivering trusted experiences to customers and partners worldwide. The Metro Construction Director role offers the opportunity to lead complex, large-scale construction programs that enable reliable, secure, and scalable services for customers around the world. We are looking for an experienced construction leader to help build the infrastructure that powers some of the world’s largest online services. Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond. In alignment with our Microsoft values, we are committed to cultivating an inclusive work environment for all employees to positively impact our culture every day."
**Responsibilities:** (long list, I'll extract as bullet points)
- Oversees the team's deployment of large-scale, campus, and/or regionally-based delivery solutions while also aligning with regional and global leaders.
- Analyzes and recommends innovative delivery options utilizing best practices and trends, supports the development and implementation of all organizational procedures and standards, and ensures they are followed by all team members and vendors.
- Provides direction and coaching to internal and external partners to help resolve complex issues that may significantly impact global construction projects.
- Reviews and provides feedback to the team regarding resource procurement, allocation, and inventory.
- Leads the team's accountability for on-schedule delivery of multiple projects by ensuring project progress reports including scope, schedule, and budget are provided.
- Leads and drives coordination for meetings and activities with vendors, cost managers, and/or owner/architect/contractors.
- Engages, advises, and collaborates with other internal teams. Manages and advocates for safe worksites by adhering to organizational and industry procedures.
- Establishes, reviews, approves, and communicates risk mitigation goals and develops metrics, dashboards and/or scorecards to drive progress.
- Directs and oversees the management of vendors, ensuring compliance with contracts and prior audit results.
- In addition, this role has people management responsibilities, including coaching team members, supporting career development, setting priorities, creating an inclusive team environment, executing projects, and managing performance.
**Requirements:** (minimum qualifications + background check)
- Required/minimum qualifications: Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 12+ years related experience OR equivalent experience.
- Background Check Requirements: Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include, but are not limited to the following specialized security screenings: Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter.
**Preferred qualifications** (from "Additional Or Preferred Qualifications"):
- Bachelor's Degree in Construction Project Management, Architecture, Engineering, or related field AND 15+ years related experience OR equivalent experience.
- 15+ years experience working on data center projects.
- 10+ years project management experience.
- 10+ years people management experience.
**Pay:**
- The typical base pay range for this role across the U.S. is USD $130,900 - $277,200 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $165,600 - $303,600 per year.
**Application period:** "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." I could fold this into a short paragraph, but the rules say "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is minor metadata. I'll fold it into a
at the end or beginning, but not as a section heading. The rules also say "Remove... application instructions." So I'll probably drop the application period or fold it minimally. I'll maybe include it as a short
after Pay, but the rule says "fold minor metadata into a short
or drop it." I'll drop it to keep it clean, or fold it into a
without a heading. I'll see. The rule: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put a
with that info, but it's minor. I'll probably just drop it, or include it as a brief
at the very end. I'll decide during output. **Removed:** EEO statement, equal opportunity text, scam warning, hashtags, "Microsoft is an equal opportunity employer.", accommodation info, "If you need assistance...", the link at the end "Find additional benefits and pay information here: ..." (I'll keep the