Technical Support Engineer - Platform 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 that have real content. We need to parse the job posting. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Method of Application: Apply online." etc. Also remove "Application Window: ..." etc. Also remove "Benefits and perks listed above may vary based on the nature of your employment with Talkdesk." Also remove "All questions or concerns about this posting should be directed to the Talent team at Talent@talkdesk.com." Also remove the long paragraph about Talkdesk story, mission, etc? That might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The mission statement and culture description might be considered not boilerplate but could be considered part of "About the role"? It's more company description. Might be considered not essential but could be kept as part of "About the role"? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep substantive info about role, duties, responsibilities, qualifications, skills, benefits, pay, schedule. The company description may be considered substantive? It's not directly about the role but could be considered "About the role"? Usually "About the role" includes description of role and maybe company. But we can include it under "About the role" as prose. We need to extract sections: - About the role: The first sentence: "The Technical Support Engineer - Platform Support serves as the initial point of contact for Talkdesk’s platform related issues, accurately capturing incident details, classifying impact and severity, and attempting immediate resolution." That's about role. - Responsibilities: The "Team Specific Duties and Responsibilities:" then bullet-like list: Familiarity with Reporting Applications: Issue Triage & Support, Data Verification, User Management & Access Control, and Incident Escalation; Familiarity with Workforce Management (WFM) Applications: Schedule & Roster Support, Configuration & Maintenance, Data Sync & Integration Monitoring, and Ticketing & Troubleshooting; Familiarity with Quality Management (QM) Applications: Platform Administration, Recording & Media Troubleshooting, System Health Monitoring, and Access & Role Management; Rigorous Ticketing Hygiene; SLA Compliance & Tracking; Escalation & Ownership; Knowledge Base Maintenance; Incident Communication. We need to format as

• for any list of duties/requirements/benefits. So each bullet can be a list item. The headings inside each bullet (like "Familiarity with Reporting Applications:") could be part of the li text. - Requirements / Qualifications: There's "Preferred Qualifications:" then list: Fluent in English; Excellent written and verbal communication skills; Previous experience in a client-facing technical role for a product business; Strong problem-solving, decision-making, and critical-thinking skills; Ability to make sense of something complex and explain it in plain English; Professional, courteous and committed to providing amazing customer support; Open-minded, positive and keen to learn; Great attitude, team player; Willing to work flexible hours; Keen to mentor and help train junior team members; College degree. Also there is "Pay Range (OTE Pay): $45,073 - $79,497". That's Pay. Other Types of Pay: Based on level and role the employee may be eligible for long term incentives in the form of equity and short term incentives of either bonus or commission. Health Insurance: Medical, Dental, Vision, Life and Disability Insurance, Employee Assistance Program (EAP). Retirement Benefits: 401(k) plan Paid Time Off: Talkdesk offers an uncapped paid time off program for exempt employees and an accrual-based program for non-exempt employees; both are subject to manager approval and consistent with business needs. Paid Holidays: Talkdesk offers 14 paid holidays each year. Paid Sick Leave: Exempt employees have uncapped paid time off and non-exempt sick leave follows accrual standards; both are subject to manager approval and consistent with business needs. Thus Benefits section includes health insurance, retirement benefits, paid time off, paid holidays, paid sick leave, other types of pay? Actually other types of pay could be under Pay or Benefits. We'll treat Pay as separate section: Pay Range and other types of pay. Schedule: Not explicitly mentioned. There's "Willing to work flexible hours" under preferred qualifications. That's not a schedule spec. No explicit schedule like "Full-time", "Shift work". So we should not create a Schedule section unless posting actually states them. It does not state schedule, so omit. We also have "Work Environment and Physical Requirements:" but that's not a standard heading; could be part of About the role or Responsibilities? Might be considered "Work Environment". Not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put work environment under About the role or Responsibilities? Probably About the role includes description. We'll include it as part of About the role prose. We must not repeat the job title as a heading. So no

  Technical Support Engineer - Platform Support

  . We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown. We need to decide which sections to include: - About the role: include role description and maybe work environment and culture description? The culture description is lengthy but could be considered "About the role"? It's more about company. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture description is not those. It's substantive? It's about Talkdesk mission, values, recognition. Could be considered "About the role" or maybe we could omit as it's not directly about role. But preserving ALL substantive information suggests we should keep it if it's substantive. However, it's not about the role; it's about the company. The instruction didn't say to keep company description; but we should preserve all substantive information from the posting. The posting includes that paragraph after "Method of Application..." etc. It's definitely part of the posting. So we should include it somewhere. Perhaps under "About the role" as a paragraph. But we need to avoid duplication: there is also a later paragraph about "Talkdesk story hinges on empathy and acceptance..." That's also company description. We'll include that as part of About the role. Thus About the role will have multiple paragraphs: role description, work environment, company story/mission, recognition. Now Responsibilities: list items. Requirements vs Qualifications vs Skills: The posting has "Preferred Qualifications:" list. Could treat as Qualifications. Also there is "College degree" under that. Could also treat as Requirements. There's no separate "Skills" list, but many items are skills. We could create a Skills section for things like "Fluent in English", "Excellent written and verbal communication skills", "Strong problem-solving, decision-making, and critical-thinking skills", "Ability to make sense of something complex and explain it in plain English", "Professional, courteous and committed to providing amazing customer support", "Open-minded, positive and keen to learn", "Great attitude, team player", "Willing to work flexible hours", "Keen to mentor and help train junior team members". But many of those are also qualifications. To avoid thin sections, we could combine Qualifications and Skills into one section called "Qualifications" (or "Requirements") and include all. The instruction: Prefer a few substantive sections over many thin ones. So we can have Qualifications section that includes both required and preferred qualifications and skills. Thus we will have sections: - About the role (

  About the role

  ) with paragraphs. - Responsibilities (

  Responsibilities

  ) with
  • items. - Qualifications (

    Qualifications

    ) with
    • items (including preferred qualifications and skills). - Benefits (

      Benefits

      ) with
      • items (health insurance, retirement benefits, paid time off, paid holidays, paid sick leave). Also maybe other types of pay? But that is pay. - Pay (

        Pay

        ) with prose: Pay Range (OTE Pay): $45,073 - $79,497. Other Types of Pay: Based on level and role the employee may be eligible for long term incentives in the form of equity and short term incentives of either bonus or commission. We should not include Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to remove duplicated lines: There's some duplication? Not obvious. Now we need to ensure we don't include application instructions: "Method of Application: Apply online." "Application Window: ..." etc. Remove those. Also remove "All questions or concerns about this posting should be directed to the Talent team at Talent@talkdesk.com." Remove. Also remove "Benefits and perks listed above may vary based on the nature of your employment with Talkdesk." Remove. Now we need to preserve all substantive information: The role description, responsibilities, qualifications, benefits, pay, work environment, company story, recognition. Let's craft the HTML. We'll start with

        About the role

        then

        ...

        maybe multiple paragraphs. We need to avoid

        headings for sub-sections inside About the role; just prose. Now let's write the About the role paragraph(s): Paragraph 1: "The Technical Support Engineer - Platform Support serves as the initial point of contact for Talkdesk’s platform related issues, accurately capturing incident details, classifying impact and severity, and attempting immediate resolution." Paragraph 2: Work environment: "Primarily office-environment work, extended periods of sitting or standing, computer-based work. Limited lifting, and equipment usage limited to computer-related equipment (keyboards, mouse, etc.)." Paragraph 3: Company story/mission: "Talkdesk is pioneering a new era of Customer Experience Automation (CXA), redefining how the world’s most admired brands interact with their customers through AI. Our global team of courageous innovators is customer-obsessed, building AI-first solutions that put empathy, trust, and transparency at the center of every interaction. We foster an inclusive culture where diverse perspectives drive our success and every voice belongs. Combining the stability of a global leader with the agility of a disruptor, Talkdeskers are empowered with the autonomy to drive meaningful impact, while giving back to the communities and environment around us." Paragraph 4: Recognition: "Talkdesk has been recognized as a Leader in the Gartner® Magic Quadrant™ for Contact Center as a Service (CCaaS) and in the G2 Overall Grid® Reports for AI Agents and Contact Center. With seven consecutive years on the Forbes Cloud 100 and multiple AI Breakthrough awards, there has never been a more exciting time to join us as we shape the future of customer experience automation!" Paragraph 5: Inclusivity statement: "The Talkdesk story hinges on empathy and acceptance. It is the shared goal among all Talkdeskers to empower a new kind of customer hero through our innovative software solution, and we firmly believe that the best path to success for our mission is inclusivity, diversity, and genuine acceptance. To that end, we will hire, promote, work along, cheer for, bond with, and warmly welcome into the Talkdesk family all persons without regard to ethnic and racial identity, indigenous heritage, national origin, religion, gender, gender identity, gender expression, sexual orientation, age, disability, marital status, veteran status, genetic information, or any other legally protected status." We could combine some but it's fine. Now Responsibilities