Technical Supp Eng V

We need to output HTML fragment with sections: About the role? The posting includes a description at start: "IGT , where innovation meets entertainment..." That's about the company, not necessarily a section heading. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. The posting includes: - Intro paragraph about IGT (company description). Could be considered "About the role"? Actually "About the role" is typical heading for role description. But we have a description of the company and then "Responsibilities". The intro could be placed under an "About the role" heading? The instruction says we can use headings like About the role, Responsibilities, etc. We need to include a section only when posting has real, specific content for it. The intro paragraph is about the company, not the role specifically. However we could treat it as "About the role" content? Might be better to not create an "About the role" heading if it's just generic company description not specific to role. But the instruction says we can use About the role for section headings. The posting does not have an explicit "About the role" section; but we could combine the introductory paragraph under that heading if we consider it role-related. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The intro paragraph is specific content about the company and role context. It's not filler. So we could create an

  About the role

  and put that paragraph in

  . That seems acceptable. Then we have "Responsibilities" heading explicitly in the posting. So we create

  Responsibilities

  and then list responsibilities as
  • items. The responsibilities are many sentences, each starting with a verb. We need to preserve all substantive information. We should not invent or summarize away detail. So we need to list each responsibility as a separate
  • . The responsibilities block includes many sentences separated by periods. We need to split them appropriately. Let's extract responsibilities text: "Serve as the technical SME for one or more core product domains, including promotional tools, core platform functionality, game engines, integration layers, and customizations.Independently diagnose and resolve complex, multi-system issues across application, integration, platform, and data layers, including code-level investigation across Java back-end and JavaScript/HTML front-end applications and event flows.Act as a senior escalation point for incidents that exceed generalist L3 support capabilities by forming and testing hypotheses, analyzing technical evidence, and isolating root causes under production conditions.Partner directly with core platform engineering to reproduce complex issues, identify failing components, provide complete and reproducible technical context, and validate permanent fixes.Trace and analyze API and integration flows using application code, technical documentation, and flow diagrams. Build or enhance scripts, queries, and diagnostic tools as needed to improve investigation and resolution.Perform log-driven investigations using OpenSearch/DQL or similar technologies and leverage platform data to support incident analysis, decision-making, and technical solutions.Lead root-cause analysis and problem-management activities, partnering with engineering to define corrective actions and reduce issue recurrence, customer impact, and mean time to resolution (MTTR).Create and maintain specialist runbooks, debugging playbooks, troubleshooting guides, knowledge articles, and diagnostic tools to improve the consistency and efficiency of technical support.Mentor and support other technical support engineers through case reviews, technical documentation, knowledge sharing, and coaching on investigation methodologies.Support operational readiness for new features, functionality, integrations, markets, migrations, and platform changes by validating expected behavior, identifying operational risks, and supporting successful rollout and handover.Partner with Product Management, Engineering, and wider operational teams to support the delivery of new functionality across promotional tools, game engines, and core platform capabilities.Maintain a high level of technical ownership within assigned product domains and promote continuous improvement across the support organization." We need to split each sentence into separate
  • . Note there are some missing spaces after periods (like "...customizations.Independently"). We'll treat each sentence as separate. Now Qualifications: The posting has "Qualifications" heading then subheadings Education Required, Experience Required, Skills Required. According to instruction, we should use

    for section headings like Qualifications, Skills, etc. But we have Qualifications heading already. Should we create separate sections for Education, Experience, Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid subheadings, but we should output only HTML fragment; we could keep Qualifications as a heading and then inside have subheadings maybe as

    ? But instruction only mentions using

    for section headings. It doesn't forbid other headings, but to keep simple, we could treat Education Required, Experience Required, Skills Required as subsections under Qualifications using

    or

    . However the instruction says "Use
    • for any list of duties/requirements/benefits". For qualifications, we could list Education as

      maybe. But we need to preserve all substantive information. Better: Keep a

      Qualifications

      then inside have

      for Education Required,

      for Experience Required,

      • for Skills Required (since it's a list). However Skills Required is also a list; we could output as
        • . The instruction says use
          • for any list of duties/requirements/benefits. Skills are requirements, so list. Education Required: "Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related technical discipline, or equivalent relevant professional experience." Experience Required: "10 years of work related experience is required.Extensive hands-on experience in senior technical application support, software engineering, integration/delivery, or a related technical role supporting business-critical, customer-facing platforms.Demonstrated experience diagnosing complex issues across distributed, multi-system environments, including application, integration, platform, and data layers.Experience investigating application behavior at the code level and isolating and validating technical fixes in production environments.Experience with API and system integrations and the ability to determine system behavior using application code, technical documentation, and flow diagrams.Experience performing root-cause analysis and supporting incident and problem-management processes." We need to split sentences. Skills Required: list of bullet-like sentences: "Strong development-level proficiency with Java for back-end applications.Strong knowledge of JavaScript and HTML, including the ability to understand and debug front-end application and event flows.Strong understanding of APIs and integration flows. Experience designing, developing, or extending APIs is a plus.Strong Linux server knowledge and scripting skills, including the ability to develop or adapt diagnostic tools.Experience with log-driven troubleshooting and analysis; knowledge of OpenSearch, DQL, or equivalent query tools is preferred.Ability to use technical and operational data effectively when investigating incidents and determining solutions.Strong understanding of operational risk and the impact of changes within business-critical production environments.Excellent analytical, troubleshooting, and problem-solving skills with the ability to independently investigate highly complex technical issues.Excellent written and verbal communication skills, including the ability to create clear, evidence-based incident narratives and high-quality technical documentation.Ability to collaborate effectively with Engineering, Product Management, Operations, and globally distributed technical teams.Ability to mentor and provide technical guidance to less-experienced support engineers.Ability and willingness to provide occasional out-of-hours support for major incidents as required." We need to split each sentence. Preferred Qualifications: after Skills Required, there is "Preferred Qualifications" heading with bullet-like sentences. According to instruction, we could include a section for "Preferred Qualifications" maybe under Qualifications or as separate heading? The allowed headings list includes Qualifications, Skills, etc. Not Preferred Qualifications. But we could treat it as part of Qualifications section, maybe as a

            heading "Preferred Qualifications:" then list. However instruction says include a section ONLY when posting has real, specific content for it. It does have content. We could create a

            Preferred Qualifications

            but not in allowed list. But maybe we can still use

            for any heading; the examples are not exhaustive. The instruction: "Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. So we can use

            Preferred Qualifications

            . Good. Then "Keys to Success" heading with list of items: "Building collaborative relationships Decision making Drive results Foster innovation Personal energy Self-leadership". These are likely bullet points. We'll make
            • . Then there is EEO boilerplate etc which we must remove. Then there is "Base pay is one component..." paragraph about pay and benefits. This includes mention of base pay, bonus/commission, benefits package. According to instruction, we should include Pay and Benefits sections only if posting actually states them. It does state base pay and benefits. So we should create

              Pay

              and

              Benefits

              sections with the relevant content. However we need to avoid filler like "depending on the role, employees may be eligible for bonus or commission opportunities." That's substantive. Also "IGT also offers a comprehensive benefits package, which may include a 401(k) savings plan with company contributions, medical, dental, and vision insurance, life and disability coverage, paid time off, tuition reimbursement, and other wellness programs, subject to eligibility requirements." That's substantive. We should not include the sentence "Base pay is one component of IGT’s total rewards program." That's part of Pay section. We also have "IGT is the global leader in gaming. For more information, please visit www.igt.com ." That's boilerplate/footer; we should remove. Also earlier there is "IGT , where innovation meets entertainment on a global scale! ... your next big move starts here - www.igt.com ." That's intro; we already used as About the role. Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "We thank all applicants for their for applying; however, only those selected to interview will be contacted." That's application instruction; remove. Now we need to output only HTML fragment. Let's structure:

              About the role

              IGT, where innovation meets entertainment on a global scale! From the casino floor to your mobile screen, we deliver thrilling, responsible, and unforgettable gaming experiences—powered by world‑class content, strong technical and commercial capabilities and nurtured by a culture of collaboration, accountability, and ownership. Whether it’s spinning reels, placing bets, or enabling secure payments, we turn innovation into impact through disciplined execution and long‑term value creation. With a team of over 6,000 employees across 30+ countries and products delivered in more than 100 jurisdictions worldwide, we operate at scale while staying closely connected to customers we serve. If you’re ready to bring your talent to a team shaping