Manager, Workplace

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes description of role (what you'll do) and what you bring (requirements). Also includes compensation (Pay) and benefits. No schedule info. So we can have sections: About the role (maybe summary), Responsibilities (what you'll do), Requirements (what you bring includes experience etc), Skills (maybe combine with requirements? But we need to follow headings list; we can include Skills if there is specific skill content. The posting mentions many skills: organization, communication, etc. Could put under Skills. Benefits: they list benefits. Pay: salary range. Schedule: not present, so omit. We must not repeat job title as heading. No Job ID. Must preserve all substantive info. Remove boilerplate like EEO, accommodation statement, etc. Also remove "About MongoDB" maybe? It's not required as a heading; but we could include under About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (summary), Responsibilities, Requirements, Skills, Benefits, Pay. Possibly Qualifications if distinct from Requirements; but we can combine. The posting has "What you bring" which includes experience and skills. Could treat as Requirements and Skills. We'll separate: Requirements (experience, years, etc.) Skills (specific abilities). We'll need to parse. Let's extract: About the role: The first paragraph(s) describing role: "MongoDB is seeking a proactive, hands-on Workplace Manager to lead the day-to-day operations of our San Francisco office while overseeing the employee experience and operational performance of our North America portfolio of satellite (a.k.a. “spoke”) offices. This is an operations-first role for someone who takes pride in making workplaces safe, welcoming, functional, and consistently well run. You will be the visible, service-minded point of contact for employees, visitors, vendors, and local leaders; responding to requests, coordinating workplace services, maintaining accurate records, and following issues through to resolution. Alongside daily operations, you will help cultivate a connected hybrid workplace in our San Francisco office and our Spoke Offices through thoughtful events, local communications, and culture-building initiatives." That's good. Responsibilities: The bullet list under "What you’ll do". We'll convert each line to

. Need to preserve all details. Let's list responsibilities from the text: - Own day-to-day workplace operations in San Francisco Hub Office - Serve as the primary point of contact and escalation path for workplace matters across assigned spoke offices and/or the designated hub office - Maintain a safe, clean, professional, organized, and welcoming workplace environment for employees and visitors - Conduct regular office walkthroughs to identify maintenance, facilities, hospitality, safety, presentation, and space issues; coordinate corrective actions and confirm completion - Respond to, track, and resolve employee and stakeholder requests through workplace support channels and systems with urgency, clear communication, and strong follow-through - Coordinate front-of-house and visitor experiences, greeting employees, guests, candidates, and vendors with a warm, hospitality-first mindset - Oversee Spoke office memberships, including activation, deactivation, changes, and ongoing third-party vendor coordination where applicable - Coordinate facilities workflows such as janitorial services, conference-room and event bookings, work orders, scopes of work, service requests, and office access needs - Monitor office supplies, amenities, equipment, and shared spaces; coordinate replenishment, repairs, and replacements - Maintain accurate workplace records and systems, including provider or membership databases, occupancy/utilization information, service logs, and operational documentation - Partner with Physical Security on access control, visitor procedures, incident follow-up, and other security requirements - Coordinate with IT/AV and other service partners to help ensure meeting rooms, workplace technology, and office equipment are working properly - Communicate workplace updates, service changes, expectations, and important office information clearly and consistently - Own Spoke Office operations and engagement across America - Oversee the day-to-day operations of our Spoke Offices across the Americas, serving as the primary Workplace point of contact for each location - Actively support the development of a positive, inclusive culture across Spoke Offices, ensuring local experiences align with MongoDB’s company values - Partner with Local Spoke Ambassadors to build strong office communities and deliver initiatives that foster connection and engagement - Manage office memberships, including activating, deactivating, and updating memberships, and maintain accurate provider records - Oversee ad hoc facilities operations, including janitorial services, conference-room coordination, event bookings, maintenance requests, and other office needs - Monitor and manage the budget allocated to each office location, partnering with Workplace leadership and Finance to support a consistent rhythm of events to ensure budgets are utilized effectively and completely - Audit and maintain the integrity of workplace databases and systems, including memberships, access, and utilization platforms - Support required utilization data entry and provide regular utilization and operational reports to keep Local Spoke Ambassadors and Workplace leadership informed - Proactively share workplace developments, service updates, risks, and recommendations with local stakeholders and employees We can combine into a single list; but some are subpoints. We'll just list each as separate

. Might be long but okay. Requirements: "What you bring" includes: - 5+ years of experience in workplace operations, office coordination, facilities, hospitality, events, employee experience, or a related field; 5+ years preferred for broader multi-location or specialist-level scope - Demonstrated experience managing day-to-day office or workplace operations, ideally across multiple locations or in a remote-management model - Strong event planning and execution experience, including vendor coordination, logistics, communications, and onsite delivery. - Experience managing vendors, service providers, budgets, purchase orders, invoices, or other administrative workflows - Project management experience and the ability to coordinate multiple stakeholders, deadlines, and competing priorities - Excellent organization, attention to detail, judgment, responsiveness, and follow-through - A proactive, flexible, hands-on approach and the ability to work effectively in a fast-moving environment where priorities can change - Strong written and verbal communication skills, with confidence working with employees, vendors, local leaders, and cross-functional partners - A warm, customer-obsessed, service-oriented mindset and strong emotional intelligence - Experience using workplace technology, support systems, utilization or membership platforms, and productivity tools such as Google Workspace, Slack, Coupa, Zoom, Zendesk, Concur, and Success Factors - Ability to work onsite at the designated office on a consistent basis We could split into Requirements (experience) and Skills (specific abilities). But the instruction says we can use those headings; we need to decide what goes where. Perhaps Requirements: years of experience, demonstrated experience managing day-to-day office operations, strong event planning, experience managing vendors/service providers/budgets, project management experience. Skills: organization, attention to detail, judgment, responsiveness, follow-through; proactive flexible hands-on; strong written/verbal communication; warm customer-obsessed mindset; experience using workplace technology; ability to work onsite. Qualifications: maybe not needed; we can omit if no distinct content. We'll omit Qualifications heading. Benefits: list from paragraph: equity, participation in the employee stock purchase program, flexible paid time off, 20 weeks fully-paid gender-neutral parental leave, fertility and adoption assistance, 401(k) plan, mental health counseling, access to transgender-inclusive health insurance coverage, and health benefits offerings. Pay: salary range $69,000—$135,000 USD. Schedule: none. We must not include boilerplate like EEO, accommodation statement, etc. Also remove "About MongoDB" paragraph? It's not required as a heading; but it's substantive about company. Could be part of About the role? The instruction says About the role heading for section headings (e.g. About the role...). So we could put company description under About the role? But About the role likely refers to role description, not company. However we already used About the role for role summary. The company description could be omitted? It's not required to preserve all substantive information? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the About MongoDB paragraph. Where to put it? Could be a separate section like "About MongoDB" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. Could we incorporate it into About the role? The About the role heading is for role description; but we could extend it to include company overview. Might be acceptable. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says use those for section headings. Likely they expect only those headings. So we should fit all content under those headings. The About MongoDB paragraph could go under About the role as a brief intro. Or we could put under Responsibilities? Not appropriate. Better to include under About the role as a brief description of the company and role. We'll combine. Thus About the role will contain both the role summary and company overview. Now we need to output HTML fragment only, no or . Use

for each section heading, then content:

for prose,

• for lists. We must not repeat job title as heading. No Job ID. Let's craft. Section About the role:

  About the role

  then a

  containing the role summary and company overview. We'll combine: "MongoDB is seeking a proactive, hands-on Workplace Manager to lead the day-to-day operations of our San Francisco office while overseeing the employee experience and operational performance of our North America portfolio of satellite (a.k.a. “spoke”) offices. This is an operations-first role for someone who takes pride in making workplaces safe, welcoming, functional, and consistently well run. You will be the visible, service-minded point of contact for employees, visitors, vendors, and local leaders; responding to requests, coordinating workplace services, maintaining accurate records, and following issues through to resolution. Alongside daily operations, you will help cultivate a connected hybrid workplace in our San Francisco office and our Spoke Offices through thoughtful events, local communications, and culture-building initiatives. MongoDB is built for change, empowering our customers and our people to innovate at the speed of the market. We have redefined the data platform for the AI era, enabling builders to create, transform, and disrupt industries with software. MongoDB’s unified data platform, the most widely available, globally distributed data platform on the market, helps organizations modernize legacy workloads, embrace innovation, and unleash AI. Our cloud-native platform, MongoDB Atlas, is the only globally distributed, multi-cloud data platform and is available across AWS, Google Cloud, and Microsoft Azure. With offices worldwide and over 67,000 customers, including AI-native startups and approximately 75% of the Fortune 100, relying on MongoDB for their most important applications, we’re powering the next era of software." That's fine. Responsibilities:

  Responsibilities

  then
  with each responsibility as
  • . We'll need to ensure we include all points. We'll list them as separate items; may be long but okay. We'll combine some to avoid excessive duplication but keep all info. Let's draft list items: - Own day-to-day workplace operations in San Francisco Hub Office - Serve as the primary point of contact and escalation path for workplace matters across assigned spoke offices and/or the designated hub office - Maintain a safe, clean, professional, organized, and welcoming workplace environment for employees and visitors - Conduct regular office walkthroughs