Global Real Estate Director

We need to output HTML fragment with sections:

for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. The posting includes: About the role (the paragraph after location). Then responsibilities: "What will you do?" with bullet-like sentences. Then qualifications: "What qualifications will make you successful?" with bullet-like sentences. Then rewards: "Rewards designed for you" describing total rewards, but not specific benefits/pay/schedule. No explicit pay or schedule details. There's mention of "€40 billion global revenue +9% organic growth 150 000+ employees in 100+ countries" but that's not pay/benefits. There's no specific benefits list. So we should not create Benefits, Pay, Schedule sections unless actual content. There's no explicit benefits list; the "Rewards designed for you" is generic, not specific benefits. According to rule: never create Pay/Schedule/Benefits sections unless posting actually states them. So we omit those 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. Remove boilerplate: cookie/navigation/legal/EEO etc. So we need to cut out the long paragraphs about inclusion, trust charter, equal opportunity, etc. Also remove "Location: Kallang Mission (About The Role)"? Actually location line: "Location: Kallang Mission (About The Role)" seems like a heading? The instruction: 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 location can be a short

  . We'll include location as a

  . We need to keep the "About the role" paragraph after location. Actually the text: "Location: Kallang Mission (About The Role) The Global Real Estate Director plays a critical global role..." So we can treat "Location: Kallang Mission" as a

  . Then the rest as About the role section with heading

  About the role

  and then

  containing the description. Then responsibilities: heading

  Responsibilities

  (or maybe "What will you do?" but we should use standard heading "Responsibilities". 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. So we will have

  Responsibilities

  and then a
  • list of each duty. We need to extract duties from "What will you do?" bullet-like sentences. They are separated by periods and start with capital letters. Let's list them: - Co define the global Real Estate strategy with Corporate RE, Industrialization, and GSC partners to support footprint optimization and business growth. - Drive harmonization and transparency of the end to end property portfolio (offices, plants, warehouses, labs), including data quality, contracts, KPIs, and governance. - Oversee and support Real Estate decisions across GSC property portfolio, ensuring alignment with strategic, financial, and operational priorities. - Deliver analytics and insights (scenario planning, location strategy, make vs lease, consolidations, climate and nature scenario) to enable informed decisions on productivity and footprint evolution. - Strengthen governance frameworks to ensure alignment between Corporate, Regional, and SERE teams. - Build global IFM/FM capability through benchmarking, cost transparency, and data driven identification of outliers and productivity opportunities. - Standardize and elevate FM practices globally, such as promoting convergence/sharing of regional best practices in operating model and innovation - Embed sustainability FM practices and sustainable vendor selection criteria into the global FM model. - Partner with Corporate Security, Regional FM, and Indirect Procurement on governance of guarding, access control, CCTV, visitor management, and incident response - Global governance processes: KPIs, SLAs, vendor reviews, risk assessments, and escalation protocols. - Integration of physical security standards within IFM execution models. - Alignment with global resilience requirements and internal/external audit expectations. - Integrate climate risk assessment and adaptation planning into site strategy, footprint decisions and CapEx planning. - Support Scope 1 and 2 emissions reduction by strengthening governance of Real Estate and Facility Management data, spending, and performance monitoring. - Ensure sustainability standards (LEED, BREEAM, WELL) are applied in new tertiary buildings, major refurbishments, and acquisitions.[VM1.1][SD1.2] - Own the RE/FM contribution to the Sustainability Cockpit and to external disclosure frameworks (CSRD, TCFD, TNFD).[VM2.1][SD2.2] - Lead or participate in transversal topics and initiatives across Real Estate, FM, SERE, Digital, Sustainability, and GSC strategy. - Drive SERE Technical Debt Reduction initiatives (assets, systems, digitization). - Support Schneider Electric’s Digital transformation, AI use cases, Sustainability Cockpit, and data driven decision tools. - Support Winning Plan reporting, and coordination of steering committees. - Act as the key global interface between GSC and Corporate Functions on Real Estate, FM, and Physical Security topics. - Drive organizational alignment by bridging strategic, policy, and operational layers across Corporate, Regional, and Site teams. - Influence senior stakeholders, navigate matrix structures, and resolve cross functional misalignments. We need to keep all substantive info; we can keep the bracketed references like [VM1.1][SD1.2] as part of text. Now qualifications: heading

    Qualifications

    (or Requirements? The instruction list includes Requirements and Qualifications both. We have qualifications section. We'll use

    Qualifications

    . Then list items: - Experience in global Real Estate, Facility Management, or related fields across a multi site, international environment. - Knowledge of integrated facility management (IFM), service delivery models, and vendor governance. - Strong understanding of real estate transactions (acquisitions, renewals, disposals) and portfolio optimization. - Experience in climate and nature capital risk frameworks (TCFD, TNFD, scenario analysis), corporate decarbonization pathways, and sustainability disclosure (CSRD, GHG Protocol, SBTi). - Proficiency in FM/RE systems, workplace management tools, financial modeling, and CapEx/Opex planning. - Professional certifications such as IFMA (CFM), LEED AP, and GARP SCR preferred. - Degree in Real Estate, Facility Management, Engineering, Architecture, Business or related discipline preferred. We could also include "Rewards designed for you" as maybe a

    Benefits

    but it's not specific benefits; it's generic. According to rule, we should not create Benefits unless posting actually states them. It does not list specific benefits like health insurance, retirement, etc. So we omit. We also have a short paragraph about Total Rewards being more than pay and benefits, but again not specific. So we omit Benefits/Pay/Schedule. We also have location line: we can put

    Location: Kallang Mission

    . We also have the introductory paragraph about Schneider Electric mission etc. That is boilerplate? It's about company mission; could be considered substantive? It's not about the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement at start might be considered boilerplate? It's generic corporate description. Might be considered not specific to the role. However it's not EEO etc. But it's still generic fluff. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The mission statement is not about the role; but it's still part of posting. However typical job postings include a company overview; we might keep it as a

    under maybe no heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

    • for any list of duties/requirements/benefits, and

      for prose. It doesn't forbid having a

      without heading. So we can include the opening mission paragraph as a

      before the About the role heading. But we need to remove duplicated lines, application instructions, EEO etc. So we will cut out the later paragraphs about IMPACT values, Trust Charter, Equal Opportunity, etc. Also remove the line about "You must submit an online application..." etc. Also remove the revenue/employee stats? That's maybe substantive? It's company info; could be kept as a

      . But it's not about the role. Might be considered boilerplate but it's factual. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say to remove company overview. So we can keep the mission paragraph and maybe the revenue/employee stats as a

      . However the revenue/employee stats appear near the end before application instructions. Might be considered company info; we can keep. But we need to be careful not to include boilerplate like "We are looking for IMPACT Makers..." etc. That's more fluff; could be considered not specific to role. Might be removed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "IMPACT Makers" paragraph is generic fluff; but it's still part of posting. However it's not about the role specifics. I'd lean to remove it as it's more marketing fluff. The instruction says remove duplicated lines, but not necessarily all fluff. However to be safe, we could keep it as a

      under no heading? But it's not a list. Might be considered substantive? It's describing culture; could be considered relevant to role. However the instruction about sections: we could include a section "About the company" but not in allowed headings list. Since only allowed headings are those listed, we should not create other headings. So we could just put it as a

      without heading. But we need to decide what to keep. The mission paragraph at start: "In Schneider Electric, everything we do is geared towards advancing progress and sustainability for all—our colleagues, customers, partners, and the communities and societies we serve. Whether it's through our products, software, and services that propel the digital transformation of energy management and automation, or through our corporate citizenship and volunteer activities, we make a meaningful impact by empowering people and organizations to become more resilient, electric, and digital. Which is where you come in. Working at Schneider Electric means working toward a cleaner, better world. You are part of a global team built on inclusion, mastery, purpose, action, curiosity, and teamwork, turning sustainability ambitions into actions." That's substantive about company values and mission; could be kept. Then location line. Then About the role heading and paragraph. Then Responsibilities heading and list. Then Qualifications heading and list. Then maybe a

      for the rewards paragraph? It's generic but maybe we can keep as

      without heading. However the instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. The rewards paragraph is not a list of benefits; it's a description. It's not a section heading. So we could keep it as a

      after Qualifications. But the rewards paragraph includes: "Rewards designed for you Our Total Rewards is our way of saying: We see you and we value you. It’s more than just pay and benefits—it’s a meaningful investment in you. It is designed to help you perform, grow, feel safe, and elevate your potential. The package helps you care for yourself and your family, plan your future, grow your skills and career, collaborate in an inclusive workplace, and contribute to your community. At