Senior Manager, Real Estate & Workplace Programs

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 that have real specific content. We need to parse the posting: It starts with description: "Navan is seeking a Senior Manager, Real Estate and Workplace Programs to build the operating cadence..." That's about the role. Then "What You'll Do" list of responsibilities. Then "What We're Looking For:" list of requirements/qualifications. Then "Preferred Experience". Then "What Success Looks Like" maybe could be considered as outcomes but not a standard heading; maybe we can treat as part of Responsibilities? But we should only include sections with real content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit Benefits, Pay, Schedule mentioned. There's mention of ability to travel up to 20% - that could be under Schedule? Not exactly schedule. Could be under Requirements? Travel requirement. But we should not create Pay/Schedule/Benefits unless posting actually states them. It does not state pay, benefits, schedule specifics. So we omit those sections. We need to include About the role (maybe a brief paragraph summarizing the role). Then Responsibilities (What You'll Do). Then Requirements/Qualifications (What We're Looking For). Possibly Skills could be separate but we can combine into Requirements. The instruction: Use headings for those categories if content exists. We can have About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to avoid thin sections. Might combine Requirements and Qualifications into one? But they are separate headings allowed. However we need to ensure we have real content for each. We have "What We're Looking For:" includes experience, skills, etc. That could be split into Requirements (experience) and Qualifications (education? not present) and Skills (specific abilities). But we can treat the whole block as Requirements and maybe Skills. However we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if we have content. Let's extract content: About the role: first paragraph(s) before "What You'll Do". That includes: "Navan is seeking a Senior Manager, Real Estate and Workplace Programs to build the operating cadence for our global real estate and workplace portfolio. This is a real estate-first role with strong program discipline, focused on creating structure around our spaces, lease obligations, key dates, occupancy and utilization, space planning options, active workstreams, stakeholder inputs, standards, and portfolio decision processes. This role owns the internal portfolio strategy, business case development, broker coordination, and decision process. Reporting to the Senior Director, Real Estate & Workplace, this person will own end-to-end portfolio initiatives, turning fragmented information into clear decisions, owners, timelines, risks, and executive-ready updates. This is a hands-on, high-impact role for someone with corporate real estate judgment, global portfolio discipline, and the ability to drive complex cross-functional work. Consistent with Navan’s AI-first value, this person will use modern tools and AI-enabled workflows to make the real estate and workplace operating system faster, clearer, and more scalable." That's good. Responsibilities: bullet list under "What You'll Do". Each line starts with a verb. We'll put each as

. Requirements: maybe the "What We're Looking For:" bullet points (the first set before "Preferred Experience"). That includes: - 6+ years of experience in corporate real estate, workplace strategy, real estate portfolio management, or real estate program management. - Experience supporting a multi-site corporate real estate or workplace portfolio; international or global portfolio experience strongly preferred. - Strong understanding of lease events, renewals, notice dates, transaction timelines, landlord coordination, broker processes, and key commercial obligations. - Experience managing brokers and external real estate partners while owning internal stakeholder alignment, business case development, financial assumptions, and executive decision materials. - Ability to connect headcount, seats, utilization, cost, timing, and business needs into clear portfolio views, options, and decision support. - Strong partnership skills with Finance, People, Legal, Procurement, IT, Security, and regional workplace teams on occupancy planning, portfolio forecasting, and real estate decision governance. - Strong program management skills, with the ability to create clear cadences, decision tracking, escalation paths, and cross-functional accountability. - Excellent analytical and executive communication skills, with the ability to synthesize conflicting inputs into clear trackers, status updates, decision memos, risk summaries, and leadership updates. - Strong comfort with AI-enabled tools, automation, and data-driven workflows; curious and proactive about using technology to improve how teams operate. - Ability to travel up to 20% across domestic and international locations as portfolio initiatives require. We could split these into Requirements (experience) and Skills (abilities). But we can also put all under Requirements and maybe Skills separate for things like "Strong partnership skills", "Strong program management skills", "Excellent analytical and executive communication skills", "Strong comfort with AI-enabled tools". However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we need to follow heading usage: we can include both if we have content. However we risk thin sections if we split too much. We have also "Preferred Experience" bullet list: could be under Qualifications or Preferred Experience (not a standard heading). Could treat as Qualifications. We have "What Success Looks Like" which is more about outcomes; could be omitted or included under Responsibilities? Probably not needed. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to ensure each has substantive content. Let's allocate: - About the role: paragraph as above. - Responsibilities: list of duties from "What You'll Do". - Requirements: maybe the core experience requirements: 6+ years experience, multi-site experience, understanding of lease events, managing brokers, ability to connect headcount etc. That's a set. - Qualifications: maybe the preferred experience bullet list (high-growth tech, prior experience with firms, hands-on experience across regions, familiarity with data sources). That's substantive. - Skills: maybe the partnership skills, program management skills, analytical/communication skills, AI comfort, travel ability. That's also substantive. Thus we have five sections. We must not repeat job title as heading. We'll not. We must not include Job ID etc. We must remove boilerplate like EEO, AI-assisted tool notice, etc. At the end there is a paragraph about Navan uses AI-assisted Automated Employment Decision Tool (Metaview)... etc. That's boilerplate; we should remove it. Also remove "Your rights: If you prefer..." etc. Remove all that. Now produce HTML fragment: use

for each heading, then content:

for prose,

• for lists. We need to ensure we preserve all substantive information; do not invent or summarize away detail. So we must keep all bullet points exactly as given (maybe slight rephrase? Must preserve meaning; we can keep same wording). We'll copy them. Let's extract bullet points exactly: From "What You'll Do": - Build and maintain a trusted global portfolio view of our spaces, lease obligations, commercial terms, capacity, business purpose, key documents, owners, and upcoming decisions. - Own the portfolio calendar, ensuring key lease, renewal, expansion, project, payment, and approval deadlines are visible, actionable, and translated into clear business implications. - Manage broker relationships and transaction workstreams, ensuring market activity, proposals, deal timelines, stakeholder inputs, and decision points are coordinated and aligned to Navan’s business needs. - Own the internal business case for real estate decisions, including options, assumptions, risks, financial impact, operational implications, stakeholder alignment, and recommended path forward. - Partner closely with Finance to maintain visibility into occupancy costs, rent commitments, capex and opex assumptions, budget exposure, forecast changes, and scenario models. - Coordinate occupancy, utilization, and capacity planning inputs across key locations, and use them to frame space planning options such as expansion, consolidation, sublease, exit, relocation, or seating changes. - Partner with business stakeholders to align requirements, constraints, timing, decision makers, and open questions. - Create visibility across real estate and workplace projects, including milestones, owners, dependencies, risks, budgets, escalations, and leadership updates. - Build repeatable standards for space requests, project handoffs, site readiness, and portfolio reviews. - Apply practical AI-enabled workflows and automation to improve portfolio visibility, documentation, reporting, decision preparation, and operating efficiency. Now "What We're Looking For:" bullet list (the first set). Let's copy each: - 6+ years of experience in corporate real estate, workplace strategy, real estate portfolio management, or real estate program management. - Experience supporting a multi-site corporate real estate or workplace portfolio; international or global portfolio experience strongly preferred. - Strong understanding of lease events, renewals, notice dates, transaction timelines, landlord coordination, broker processes, and key commercial obligations. - Experience managing brokers and external real estate partners while owning internal stakeholder alignment, business case development, financial assumptions, and executive decision materials. - Ability to connect headcount, seats, utilization, cost, timing, and business needs into clear portfolio views, options, and decision support. - Strong partnership skills with Finance, People, Legal, Procurement, IT, Security, and regional workplace teams on occupancy planning, portfolio forecasting, and real estate decision governance. - Strong program management skills, with the ability to create clear cadences, decision tracking, escalation paths, and cross-functional accountability. - Excellent analytical and executive communication skills, with the ability to synthesize conflicting inputs into clear trackers, status updates, decision memos, risk summaries, and leadership updates. - Strong comfort with AI-enabled tools, automation, and data-driven workflows; curious and proactive about using technology to improve how teams operate. - Ability to travel up to 20% across domestic and international locations as portfolio initiatives require. Now "Preferred Experience" bullet list: - Experience in a high-growth technology company or similarly fast-moving global environment. - Prior experience in corporate real estate, workplace strategy, portfolio strategy, either in-house or with firms such as JLL, CBRE, Cushman & Wakefield, or similar. - Hands-on experience coordinating across AMER, EMEA, and APAC time zones, vendors, lease structures, regional teams, and external project partners. - Familiarity with workplace data sources such as badge data, seat inventories, HRIS headcount, finance forecasts, and lease administration tools. Now "What Success Looks Like" bullet list (maybe we could omit, but it's substantive; but we don't have a standard heading for it. Could we include as a section? Not in the list of allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. ...)". It implies we should use those headings for sections; but we could also add other headings if needed? Safer to stick to those. So we may omit Success Looks Like or incorporate into Responsibilities? It's about outcomes, not duties. Could be omitted as not required? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. If we don't have a heading for it, we could put it under a generic

  after the sections, but that might be okay. However we need to decide where to place it. Perhaps we can add a section "Outcomes" but not in the list; risk of not following instruction. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills,