Director of Security

We need to output HTML fragment with sections: About the role? The posting includes sections: OUR PURPOSE AND CULTURE, THE TEAM, YOUR ROLE, HOW YOU'LL MAKE THE PLACE, COULD THIS BE YOU?, OUR COMMITMENT TO YOU, PAY TRANSPARENCY. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings if they match content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those standard headings when appropriate, but we can also use other headings if they reflect content? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to map content to those headings where applicable. However the posting has its own headings: OUR PURPOSE AND CULTURE, THE TEAM, YOUR ROLE, HOW YOU'LL MAKE THE PLACE, COULD THIS BE YOU?, OUR COMMITMENT TO YOU, PAY TRANSPARENCY. We need to decide which sections to include. We must include a section ONLY when posting has real, specific content for it. We should not create Pay/Schedule/Benefits unless posting actually states them. Pay is stated: salary range $95,000 - $106,000 annually, plus possible bonuses. So we can include a Pay section with that info. Schedule not mentioned, so omit. Benefits not explicitly mentioned; there is "OUR COMMITMENT TO YOU" which mentions DEI etc but not specific benefits like health insurance. So we should not create Benefits section unless specific benefits are listed. There's no explicit benefits list, so omit. We need to include sections like About the role, Responsibilities, Requirements, Qualifications, Skills. We can map content accordingly. Let's parse: - About the role: could be the "YOUR ROLE" paragraph summarizing role. Also "HOW YOU'LL MAKE THE PLACE" includes responsibilities. So we could have About the role (summary) and Responsibilities (list). Or combine. - Responsibilities: list of duties from "HOW YOU'LL MAKE THE PLACE" bullet-like sentences. - Requirements/Qualifications/Skills: from "COULD THIS BE YOU?" includes education, experience, strategic thinking, project management, business acumen, budget management, communication, stakeholder management, knowledge of fire & life safety, pre-opening luxury hotel experience, guest-centric mindset, analytical data-driven approach, hospitality/luxury experience. We can separate into Requirements (education, experience) and Qualifications/Skills (others). But we can also combine. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should make a list. For requirements/qualifications/skills we also list. We must not repeat the job title as a heading. The job title is "Director of Security: Rosewood Calistoga". We should not put that as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none obvious besides maybe "OUR COMMITMENT TO YOU" includes DEI but that's not boilerplate; it's specific. We need to preserve all substantive information. Thus output HTML fragment with sections: About the role (

  About the role

  ), Responsibilities (

  Responsibilities

  ), Requirements (

  Requirements

  ), Qualifications (

  Qualifications

  ), Skills (

  Skills

  ), Pay (

  Pay

  ). Possibly also "Our Commitment to You" could be a section like "Culture & Commitment" but not in 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. ...)" implying we should use those headings for sections. It might be okay to add other headings if they reflect content, but safer to map to allowed headings. However "OUR PURPOSE AND CULTURE", "THE TEAM", "OUR COMMITMENT TO YOU" are substantive; we could include them as sections with appropriate headings like "Purpose and Culture", "Team", "Commitment". But they are not in the example list. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are examples of section headings we may use, not an exclusive list. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as long as they are

  . But we should avoid making up sections with filler. So we can include sections for Purpose and Culture, Team, Commitment. But we also need to avoid duplication. Let's decide to include sections: About the role (summary), Responsibilities (list), Requirements (education/experience), Qualifications (strategic thinking etc), Skills (communication etc), Pay (salary), Purpose and Culture, Team, Commitment. But that may be many sections; instruction says "Prefer a few substantive sections over many thin ones." So we should consolidate. Maybe we can have: About the role (summary + purpose and culture?), Responsibilities (list), Requirements and Qualifications (combined list), Skills (list), Pay. That's fewer. But we need to preserve all substantive information. Let's extract: Purpose and Culture paragraph: "We are driven to create a future where people and place enrich one another. We are wholly committed to rooting ourselves more deeply in every place we are in while setting new benchmarks for positive impact.As a pioneering collective with a common purpose, we curate extraordinary moments and honor the soul of every place along our journey. At Rosewood Hotel Group, we answer The Calling. Together, we Make the Place." Team paragraph: "As part of the Engineering Division, which focuses on ensuring the safety, efficiency, and sustainability of all hotel assets, this role contributes to the strategic and operational excellence of the property. You will report directly to the Director of Engineering, collaborating closely with senior leadership, cross-functional departments, and external partners to uphold Rosewood's standards of luxury and innovation." These are substantive but could be folded into About the role or a general overview. Commitment paragraph: "At Rosewood Hotel Group, your voice is heard and valued. We're a community that encourages associates to be themselves, not fit into a fixed culture, and this philosophy shines through in our commitments to reflect and honor the history, culture and geography of our destinations. We're not only committed to building and nurturing genuine, long-lasting relationships but to transforming them and our Diversity, Equity and Inclusion (DEI) strategy helps put these principles into practice." That's also substantive. We could have sections: About the role (includes purpose, culture, team, commitment), Responsibilities, Requirements/Qualifications/Skills (combined), Pay. But we need to use

  • for any list of duties/requirements/benefits. So responsibilities list, requirements list, qualifications list, skills list. We could combine requirements, qualifications, skills into one list? But they are different types; better to separate. But instruction: "Prefer a few substantive sections over many thin ones." So maybe we can have three sections: About the role (summary), Responsibilities (list), Requirements & Qualifications (list), Skills (list), Pay (maybe as a short paragraph). That's still many. We could combine Requirements and Qualifications into one list labeled "Requirements & Qualifications". Skills separate. Thus sections: About the role, Responsibilities, Requirements & Qualifications, Skills, Pay. That's five sections. Let's craft content. About the role: combine purpose and culture, team, commitment, and brief role summary from "YOUR ROLE". We'll write a paragraph. Responsibilities: list each duty from "HOW YOU'LL MAKE THE PLACE". Let's extract bullet points: - Lead the day-to-day security operations across the entire resort. - Develop and implement security policies, procedures, and standard operating procedures. - Ensure 24-hour security coverage for all operational areas as needed. - Manage outsourced security providers and ensure contractual compliance and service excellence as required. - Conduct regular patrols and inspections of guest, associate, back-of-house, and perimeter areas. - Oversee access control systems, visitor management, and key control procedures. - Ensure effective CCTV surveillance and monitoring systems are maintained. - Develop and maintain the resort's comprehensive Risk Register. - Conduct regular security and operational risk assessments across all departments. - Identify vulnerabilities and implement mitigation plans. - Carry out routine safety inspections of guest and associate areas. - Ensure compliance with statutory regulations, fire codes, and internal safety policies. - Represent Security in management and associate meetings, fostering cross-departmental collaboration. - Support pre-opening strategy and execution, overseeing all activities within the Security Department, in close partnership with peers and the corporate team. - Maintain readiness for Operational Management Reviews (OMR) and ensure timely follow-up on corrective actions. - Develop and update departmental policies and manuals to ensure consistency across the group. - Build and lead a technically competent and motivated Security team through recruitment, training, and succession planning. - Promote associate engagement through regular communication, recognition programs, and performance feedback. - Uphold discipline and support grievance procedures in partnership with Talent & Culture. - Model Rosewood's culture, vision, and values in all interactions and leadership practices. That's a lot; we keep all. Requirements & Qualifications: from "COULD THIS BE YOU?" plus maybe some from earlier? Let's list: - Bachelor's degree or equivalent qualification in security management, or related field. - Proven experience in leading a Security department at a senior management level. - Strong strategic thinking and project management capabilities. - Solid business acumen and experience managing complex budgets, including capital expenditure. - Excellent written and verbal communication and presentation skills. - Ability to manage relationships effectively with both internal and external stakeholders. - Knowledge of the steps required to meet or exceed compliance with all Fire & Life Safety standards. - Previously contributed to the successful pre-opening of a luxury hotel. - Guest-centric mindset with a strong commitment to service excellence. - Analytical, data-driven approach to decision-making. - Experience in hospitality or luxury environments further strengthens your profile. We could separate Requirements (education, experience) and Qualifications (strategic thinking, business acumen, etc.) but we combined. Skills: maybe communication, relationship management, analytical, etc. But we already included communication etc. Could separate but we might duplicate. Better to keep Requirements & Qualifications as one list; Skills maybe not needed separately. However we need to follow instruction to use
    • for any list of duties/requirements/benefits. So we can have one list for responsibilities, one for requirements/qualifications. Skills not separate. Thus sections: About the role, Responsibilities, Requirements & Qualifications, Pay. Pay: include salary range and bonus eligibility. Let's craft HTML. We need to output only HTML fragment, no /, no markdown. We'll do:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements & Qualifications

      • ...