Director of Event Technology II, Venues- Sanibel Harbor Marriott

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, Key Job Responsibilities (with subcategories), Job Qualifications, Competencies, Physical Requirements, Work Environment, Salary Pay Range, Benefits mention. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. Do not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Click here to view the benefits options..." and "Click here to view details on our commitment..." as they are application instructions? They are links to benefits and inclusivity; they might be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Click here to view the benefits options..." is likely an application instruction (link to benefits). Should we remove? Probably yes, as it's an instruction to click. Similarly the inclusivity link. Also "For more information on our Competency Group, refer to the Competency Based Talent Management page..." is also a link; maybe remove as it's a reference. Also "Note: The physical requirements marked with an asterisk () indicate activities performed without assistance.*" Keep? It's part of physical requirements description; it's not boilerplate. Keep. We need to preserve all substantive information. So we need to include sections: About the role (Position Overview), Responsibilities (maybe break into sub-sections? But we can have a single Responsibilities section with lists). Requirements (Job Qualifications). Skills? Could include Competencies as Skills? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have Pay (Salary Pay Range). Benefits: there is a mention of benefits but no specifics; they say "Encore is committed to providing the best benefits options..." but no detail. Since we should not create Benefits section unless posting actually states them. It mentions benefits but no detail; maybe we can include a short paragraph about benefits? It says "Encore is committed to providing the best benefits options for our employees and families. Click here to view the benefits options..." That's not specific detail; it's a generic statement. According to rule: 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. The posting does state benefits exist but not detail; is that considered stating them? It says "Encore is committed to providing the best benefits options..." which is a statement that benefits exist but not specifics. Might be considered filler. Safer to omit Benefits section. Schedule: not mentioned explicitly; working times include irregular hours and on-call status including days, evenings, weekends, and holidays. That is schedule info. Could we create a Schedule section? The posting mentions working times will include irregular hours and on-call status including days, evenings, weekends, and holidays. That's schedule info. So we can include Schedule section with that detail. Pay: we have Salary Pay Range: $56,100.00 - $72,920.00. So include Pay section. Now structure:

  About the role

  Position Overview ...

  Then Responsibilities: we have multiple subcategories: Financial Management and Reporting, Operations Management, Sales Management, Customer Service, Technical Ability, People Development. Could combine into one Responsibilities section with lists for each subcategory. Use
  • for any list of duties/requirements/benefits. So we can have

    Responsibilities

    then maybe
    with each duty as
    • . But we also have prose paragraphs within each subcategory. The rule: Use
      • for any list of duties/requirements/benefits, and

        for prose. So we need to decide what is a list vs prose. The responsibilities are described in paragraphs; we could convert each bullet-like sentence into list items. But we must preserve all substantive information; we can keep prose paragraphs for each subheading and then lists for specific items. However the instruction: "Use

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

          for prose." It doesn't forbid having headings inside Responsibilities? It only says use h3 for section headings. So we could have

          Responsibilities

          then maybe

          Financial Management and Reporting

          but that's not allowed because only h3 for section headings? The instruction: "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests only those specific headings; but we could still use other headings? Probably safer to stick to only those headings and not add extra headings like Financial Management. So we need to embed all responsibilities under a single Responsibilities section, using prose and lists. We can break responsibilities into paragraphs (

          ) and within each paragraph we can have lists if needed. For example, Financial Management and Responsibilities includes multiple sentences; we could make a

          summarizing, then a

          for bullet points. But we need to preserve all details; we can convert each sentence into list items. Simplify: For each responsibility category, create a

          with a bold lead? Not allowed to use bold? Not prohibited. But we can just write prose. Given the volume, maybe better to create separate sections for each responsibility category using

          but that would deviate from allowed headings list. However the instruction says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but it says use h3 for section headings (e.g., those). Likely they expect only those headings. So we should not create extra headings like Financial Management. We'll just have one Responsibilities section with paragraphs and lists. Similarly for Requirements: we have Job Qualifications (Bachelor's degree preferred, etc.) and Competencies (list). Could combine into Requirements section? Or separate Requirements and Qualifications? The list includes Requirements, Qualifications, Skills as possible headings. We have Job Qualifications and Competencies. Could treat Qualifications as a heading and Skills as another? But we have both. Let's map: Job Qualifications (education, experience) -> Requirements heading. Competencies -> Skills heading. That seems appropriate. Physical Requirements and Work Environment could be separate sections? Not in the list but we could include them under Requirements? But they are substantive. The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Physical Requirements and Work Environment into a single section maybe "Working Conditions". But not in the allowed headings list. However we could still include them as

          if we consider them as section headings; but the list of examples is not exhaustive? It says "e.g." meaning examples. So we can use other headings as needed, but they gave examples. Probably okay to add other headings like Physical Requirements, Work Environment. But to be safe, we could incorporate them into Requirements or a new section like "Working Conditions". However the instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, just gives examples. So we can use other headings as needed. Thus we can have sections: About the role, Responsibilities, Requirements (Job Qualifications), Skills (Competencies), Physical Requirements, Work Environment, Pay, Schedule. We must not include Benefits section as no specific details. Now we need to remove boilerplate: The "For more information on our Competency Group..." link, the "Click here to view the benefits options..." and "Click here to view details on our commitment..." lines. Also the "Note: The physical requirements marked with an asterisk () indicate activities performed without assistance.*" we keep. Also remove duplicated lines: I see some duplicated like "See the Big Picture" appears multiple times; we keep as part of text. Now craft HTML. We'll need to escape any special characters? Not needed. Let's draft:

          About the role

          The Director, Event Technology II (DET II) is responsible for achieving the revenue and profitability goals of an assigned location(s). This position ensures the team delivers World-Class service while cultivating and maintaining relationships with key venue personnel to enhance the overall business relationship with the venue. The DET promotes high performance, accountability and continuous improvement in the team and fosters a collaborative environment that values learning and a commitment to quality. The DET II will manage venue revenues between $900k - $3.75M and will report to the Area Director, Venues or RVP, Venues.

          Responsibilities

          Financial Management and Reporting

          • Drive results by managing an efficient and profitable operation with a focused approach on revenue maximization and profitability using cost control measures in accordance with the company’s standard operating procedures.
          • Achieve Encore’s financial goals for the location(s) by effectively managing labor, equipment sub-rentals and other costs.
          • Understand and utilize operational and financial reports and completes standard and ad hoc reports accurately and on time.
          • Utilize the Company billing system to coordinate invoicing activities and makes certain that billing is reviewed and approved by clients.
          • See the Big Picture by completing the sales forecast at home location, ensuring they are accurate and submitted timely.
          • Participate in business review presentations as needed, in collaboration with regional management.
          • Review and manage location P & L and develops action plans to address deficiencies/grow the business.
          • Confirms venue partners process all payments to Encore in a timely basis.

          Operations Management

          • Perform daily floor operations including scheduling and equipment setups, operation, and strikes.
          • Assist on the floor as needed.
          • Ensure that all equipment and services are delivered on time, in good working condition and as specified by clients and the venue, and in accordance with brand standards.
          • Anticipate equipment challenges and changes in a timely and professional manner.
          • Use inventory control procedures to maintain proper inventory levels while also maintaining safety, security, and quality assurance of equipment.
          • See the Big Picture by efficiently sharing labor and equipment within the local market.
          • Attend all operational venue meetings such as daily stand-up meetings with venue operations staff.

          Sales Management

          • Work with Regional Sales Director to create effective sales strategies to maximize revenue per-event for assigned customers including upsell and cross-sell opportunities.
          • Prepare and deliver compelling presentations that convey the value of Encore and effectively solve customer challenges.
          • Effectively prepare and present quotes and proposals in a timely manner to customers, including those submitted through www.encoreglobal.com, venue booking system, or other sources as assigned.
          • Attend site visits, pre-conference planning meetings, and appropriate venue meetings as necessary to support the customer event experience.
          • Collaborate with vendors and other departments/divisions of the company to capture and service events.
          • Understand event cost structure and incorporate into solution designs according to established profitability guidelines.
          • Attend customer meetings, understanding their goals and responding to their questions, concerns, and challenges.
          • Do