Senior Analyst, L2 Restaurant Tech Support

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job description. Content: - Intro paragraph about BrinkerHead, etc. Could be "About the role" or maybe "About the role" is generic. The intro includes description of company, culture, etc. Could be "About the role" or "About Brinker". The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have: - Job Summary: description of role. Could be "About the role" or "Job Summary". Use "About the role" heading. - Responsibilities: bullet list under "What You’ll Do". That's responsibilities. - Requirements/Qualifications: "What You Bring To The Team" includes experience, skills, etc. Could be split into Requirements and Qualifications and Skills. But we can combine maybe. We have technical skills list: experience with restaurant technology, Active Directory, JAMF, Meraki, etc. Also "Strong analytical thinking, troubleshooting, problem-solving skills." etc. Also "Strong verbal communication, customer service, technical writing, and incident documentation skills." etc. Also "Ability to work independently..." etc. We could put those under "Requirements" or "Qualifications". The instruction says prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits. Benefits: The "Why Brinker" section lists flexibility hybrid schedules, dining discounts, on-site gym, culture events. That's benefits. Pay: Not mentioned. Schedule: The posting mentions after-hours schedule during week and rotating on-call weekend schedule. That's schedule info. So we should include a Schedule section. We should not include Pay if not specified. We need to avoid boilerplate like EEO, equal opportunity, navigation, cookie, legal, application instructions. The posting includes "Brinker International is an equal opportunity employer." That's boilerplate; remove. Also "Check our Careers page and LinkedIn for more exciting opportunities!" is application instruction/boilerplate; remove. Also "BrinkerHead" intro maybe considered fluff but it's substantive about culture; we can keep as part of About the role. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  • . For requirements/qualifications/skills list, also
    • . For benefits list, also
      • . For schedule maybe just a paragraph. We need to use

        for prose. We must not repeat the job title as a heading. The job title is "Sr Analyst, L2 Restaurant Tech Support". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. Now construct HTML. Start with

        About the role

        then paragraph(s) containing the intro and job summary. Intro: "What does it mean to be a BrinkerHead? It means creating moments that make everyone feel special — whether you’re supporting our restaurants, celebrating wins with your team, or sparking ideas that keep Guests coming back. We play like a team, take pride in our culture, and know that life’s too short not to work happy. At Brinker’s Restaurant Support Center (RSC), every role fuels the success of our brands — Chili’s® Grill & Bar and Maggiano’s Little Italy® — and directly impacts Team Members and Guests. From bold ideas to everyday support, we help create a fun atmosphere, great food and drinks, and the kind of hospitality that keeps everyone coming back. Here, you’ll discover opportunities for career growth, belonging, wellbeing, and plenty of chances to work hard and have fun." Then Job Summary paragraph: "The Level 2 Restaurant Systems Support Analyst provides advanced technical support for restaurant systems and serves as an escalation point for issues that cannot be resolved by Level 1. The role focuses on restoring service, troubleshooting restaurant technology, reducing recurring incidents, and driving Left Shift initiatives that strengthen Level 1 capabilities and improve the overall restaurant support experience. This position works an after-hours schedule during the week and participates in a rotating on-call weekend schedule to provide critical support for restaurant operations." We could combine into one or two paragraphs. Now Responsibilities:

        Responsibilities

        then
        • items from "What You’ll Do". Let's extract each bullet: - Receive, troubleshoot, and resolve incidents escalated by Level 1 or assigned through automated workflows. - Provide advanced support for restaurant technology, including laptops, iPads, NCR BackOffice, Aloha Configuration Center, Ziosk, kitchen display and network printers. - Utilize Active Directory, JAMF, Meraki and other technical tools to investigate issues and restore service. - Identify and implement appropriate workarounds when immediate service restoration is not possible. - Create, review, and maintain Knowledge Base Articles (KBAs) and Known Error documentation. - Drive Left Shift through knowledge creation, training, improved documentation, and coaching of Level 1 Analysts. - Identify recurring incidents and trends and partner with appropriate technical teams to address - Maintain clear and accurate incident documentation and collaborate with technical teams, vendors, and business partners as needed. - Provide reliable weekday after-hours support and participate in the team's rotating on-call weekend schedule, ensuring critical incidents are appropriately addressed and escalated. Note: The bullet "Identify recurring incidents and trends and partner with appropriate technical teams to address" seems incomplete; but we keep as is. Now Requirements/Qualifications/Skills: We could have a single section "Requirements" that includes all. List items from "What You Bring To The Team": - Foremost is understanding what great service looks like and a heart for delivering high levels of support to our restaurants. - Technical support, Service Desk, desktop support, or related IT experience; Level 2 or restaurant technology experience is preferred. - Strong analytical thinking, troubleshooting, and problem-solving skills. - Experience with restaurant technology such as NCR BackOffice, Aloha Configuration Center, and Ziosk is preferred. - Working knowledge of Active Directory, with experience using JAMF, Cisco Meraki, and CMDB tools preferred. - Familiarity with Microsoft SQL Server Management Studio (SSMS) and basic SQL querying is a plus. - Strong verbal communication, customer service, technical writing, and incident documentation skills. - Ability to work independently, manage multiple priorities, make sound escalation decisions, and operate with a strong sense of urgency. - Ability to collaborate effectively, coach and share knowledge with Level 1 Analysts. We could split into Requirements and Skills but instruction says prefer few substantive sections. So one section "Requirements" covering all. Now Benefits:

          Benefits

          list from "Why Brinker": - Flexibility that fits your life: Hybrid schedules with weekly flex days to work from home. - Enjoy our brands: Generous dining discounts at Chili’s® Grill & Bar and Maggiano’s Little Italy®. - Wellbeing at work: On-site gym and fitness classes like yoga and boot camp. - A culture worth celebrating: From company-wide events to a casual, collaborative atmosphere, you’ll find plenty of ways to connect, work hard, and play hard. Now Schedule: The posting mentions after-hours schedule during week and rotating on-call weekend schedule. We could put that in Schedule section. But we already mentioned schedule in responsibilities and job summary. However we can still have a Schedule section with details: "This position works an after-hours schedule during the week and participates in a rotating on-call weekend schedule to provide critical support for restaurant operations." We should avoid duplication but it's okay to include as separate section if it's substantive. The instruction: prefer few substantive sections over many thin ones. But schedule is a distinct aspect; we could include it. Alternatively we could incorporate schedule into About the role or Responsibilities. But we already have schedule mentioned in responsibilities bullet. However we could still have a Schedule section to highlight. The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have specific schedule info. So we can include Schedule. Now we need to ensure we don't include filler like "commensurate with experience" etc. Not present. Now produce HTML fragment. We'll wrap sections in appropriate tags. Make sure no extra text outside HTML. Let's craft:

          About the role

          What does it mean to be a BrinkerHead? It means creating moments that make everyone feel special — whether you’re supporting our restaurants, celebrating wins with your team, or sparking ideas that keep Guests coming back. We play like a team, take pride in our culture, and know that life’s too short not to work happy. At Brinker’s Restaurant Support Center (RSC), every role fuels the success of our brands — Chili’s® Grill & Bar and Maggiano’s Little Italy® — and directly impacts Team Members and Guests. From bold ideas to everyday support, we help create a fun atmosphere, great food and drinks, and the kind of hospitality that keeps everyone coming back. Here, you’ll discover opportunities for career growth, belonging, wellbeing, and plenty of chances to work hard and have fun.

          The Level 2 Restaurant Systems Support Analyst provides advanced technical support for restaurant systems and serves as an escalation point for issues that cannot be resolved by Level 1. The role focuses on restoring service, troubleshooting restaurant technology, reducing recurring incidents, and driving Left Shift initiatives that strengthen Level 1 capabilities and improve the overall restaurant support experience. This position works an after-hours schedule during the week and participates in a rotating on-call weekend schedule to provide critical support for restaurant operations.

          Responsibilities

          • Receive, troubleshoot, and resolve incidents escalated by Level 1 or assigned through automated workflows.
          • Provide advanced support for restaurant technology, including laptops, iPads, NCR BackOffice, Aloha Configuration Center, Ziosk, kitchen display and network printers.
          • Utilize Active Directory, JAMF, Meraki and other technical tools to investigate issues and restore service.
          • Identify and implement appropriate workarounds when immediate service restoration is not possible.
          • Create, review, and maintain Knowledge Base Articles (KBAs) and Known Error documentation.
          • Drive Left Shift through knowledge creation, training, improved documentation, and coaching of Level 1 Analysts.
          • Identify recurring incidents and trends and partner with appropriate technical teams to address
          • Maintain clear and accurate incident documentation and collaborate with technical teams, vendors, and business partners as needed.
          • Provide reliable weekday after-hours support and participate in the team's rotating on-call weekend schedule, ensuring critical incidents are appropriately addressed and escalated.

          Requirements

          • Understanding what great service looks like and a heart for delivering high levels of support to our restaurants.
          • Technical support, Service Desk, desktop support, or related IT experience; Level 2 or restaurant technology experience is preferred.
          • Strong analytical thinking, troubleshooting, and problem-solving skills.
          • Experience with restaurant technology such as NCR BackOffice, Aloha Configuration Center, and Ziosk is preferred.
          • Working knowledge of Active Directory, with experience using JAMF, Cisco Meraki, and CMDB tools preferred.
          • Familiarity with Microsoft SQL Server Management Studio (SSMS) and basic SQL querying is a plus.
          • Strong verbal communication, customer service, technical writing, and incident documentation skills.
          • Ability to work independently, manage multiple priorities, make sound escalation decisions, and operate with a strong sense of urgency.
          • Ability to collaborate