Senior Solutions Engineer - Healthcare & Life Sciences (Central & East)

We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, duplicated lines, cookie/navigation, etc. We need to parse the posting. Key parts: Intro paragraph: "The Healthcare Senior Solutions Engineer is a strategic expert who understands the specific needs of healthcare organizations and provides business-driven consulting to both prospective and existing customers. SEs offer healthcare-centric expertise that helps our Sales team establish clear value, differentiation, and trust in our AI-powered Contact Center and CX solutions.This individual is a seasoned operator or practitioner with deep experience in healthcare environments—across providers, payers, or digital health—bringing knowledge of clinical workflows, regulatory compliance (HIPAA, HITECH), and patient engagement to every interaction. They engage throughout the entire sales lifecycle, from pre-sales engineering and technical qualification to solution architecture and post-sale expansion.The Healthcare Solutions Engineer is a recognized thought leader who confidently supports C-level discussions, accelerates deal cycles, and helps identify and expand revenue opportunities in healthcare." That's about the role. Then "Key Responsibilities" heading with bullet list. Then "Core Background" (maybe Requirements/Qualifications). Then "Desirable Heath & Life Sciences Experience" (maybe Skills). Then "Pay Range (OTE): $157,000 - $235,000". Then "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." Then "Health Insurance: Medical, Dental, Vision, Life and Disability Insurance, Employee Assistance Program (EAP)." Then "Retirement Benefits: 401(k) plan". Then "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." Then "Paid Holidays: Talkdesk offers 14 paid holidays each year." Then "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." Then "Method of Application: Apply online." etc. Remove. Then "Application Window: The application window is expected to close at least 10 days from the posting date. The application was posted on 11/25/2025." Remove. Then "Benefits and perks listed above may vary based on the nature of your employment with Talkdesk." Might be considered boilerplate but it's about benefits; but we can keep maybe? It's generic but still about benefits. Might be okay but we can drop as it's not specific. Then paragraphs about Talkdesk story, mission, inclusivity, etc. That's boilerplate/EEO? It's about company culture, not required to keep? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusivity statement is EEO-like; likely remove. Also "Work Environment and Physical Requirements:" maybe keep? It's about work environment; not a required heading but could be part of About the role? Might be considered boilerplate? It's not EEO but still generic. Might drop. We need to decide sections: About the role (intro). Responsibilities (list). Requirements (Core Background). Qualifications maybe same as Requirements? Could combine. Skills (Desirable Heath & Life Sciences Experience). Benefits (health insurance, retirement, PTO, holidays, sick leave). Pay (Pay Range + Other Types of Pay). Schedule? Not present; no schedule info. So we omit Schedule section. We must not create sections with filler like "not specified". So only include sections with real content. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep each bullet point exactly as given? We can keep the text but maybe rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. We can copy the sentences. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities list, each bullet becomes
• . For Requirements list (Core Background) maybe list items. For Skills list (Desirable Heath & Life Sciences Experience) list items. For Benefits list (health insurance, retirement, PTO, holidays, sick leave) list items. We need to use

  for prose. We need headings

  for each section. We must not repeat job title as heading. So no

  Healthcare Senior Solutions Engineer

  . Good. We need to not put Job ID/requisition numbers as headings. We need to output only HTML fragment. Let's extract content. Intro prose: combine paragraphs about role. Let's copy: "The Healthcare Senior Solutions Engineer is a strategic expert who understands the specific needs of healthcare organizations and provides business-driven consulting to both prospective and existing customers. SEs offer healthcare-centric expertise that helps our Sales team establish clear value, differentiation, and trust in our AI-powered Contact Center and CX solutions. This individual is a seasoned operator or practitioner with deep experience in healthcare environments—across providers, payers, or digital health—bringing knowledge of clinical workflows, regulatory compliance (HIPAA, HITECH), and patient engagement to every interaction. They engage throughout the entire sales lifecycle, from pre-sales engineering and technical qualification to solution architecture and post-sale expansion. The Healthcare Solutions Engineer is a recognized thought leader who confidently supports C-level discussions, accelerates deal cycles, and helps identify and expand revenue opportunities in healthcare." Make sure spacing. Now Responsibilities list: after "Key Responsibilities" heading. List items: - Conducts research to prepare for upcoming meetings with prospects to understand their business environment, market, customers, competitors and general business challenges. - Carries out discovery conversations with customers to understand their needs and requirements for a new solution. Uncovers customer pains, learns about customer's objectives and potential needs, gathers metrics necessary for pricing and/or value discussions. Listens to the customer to gather information that can be leveraged in upcoming presentations. - Uses their in-depth knowledge of Talkdesk solutions and capabilities to specify the appropriate solution(s) for customer needs and requirements. The SE is continually learning about Talkdesk solutions to keep up with innovations and new releases of TD software. - Designs and delivers presentations to customers, on-site & virtual, showing Talkdesk’s capabilities, aligned to the customer's pains and needs that were uncovered during Discovery. - Generates simple value statements illustrating the financial value of a Talkdesk solution to customers. - Assists with scoping SOWs for customer implementations as needed. - Scopes, executes and manages customer pilots and POCs. Respond to functional and technical RFI/RFP requirements and mapping said requirements to the software solution. - Work closely with product management and engineering teams to ensure that customer feedback is incorporated into product roadmaps. - Assists with marketing and demand generation events as necessary. We need to keep each as separate
• . Some items have multiple sentences; that's fine. Now Core Background (maybe Requirements). List: - B.S. Computer Science, Software Engineering, MIS or equivalent work experience. - 8+ years as a Solutions Engineer in Software, VOIP/Telecommunications, contact centers, premise or cloud selling to Commercial or Enterprise customers. - Ability to command the attention in a room by delivering compelling presentations and demonstrations. - Good problem solving skills, including the ability to meet a business requirement with a technical solution. - Ability to communicate complex technical concepts to both technical and non-technical audiences. - Excellent presentation and communication skills, including the ability to lead technical discussions and demonstrations with customers. - Knowledge of Customer Relationship Management Software, ITSM, Data Warehousing, Business Intelligence is a plus. - Knowledge of UCaaS, CCaaS software is a plus. - Knowledge in web / scripting technologies is a plus. Now Desirable Heath & Life Sciences Experience (Skills). List: - Strong working knowledge of healthcare industry standards, regulations, and data handling practices including HIPAA, HITECH, and HITRUST. - Proven ability to align technology solutions to clinical, operational, and financial healthcare KPIs. - Experience in SaaS, including 2+ years supporting healthcare-specific customers. - Experience in healthcare contact centers (patient scheduling, billing, nurse triage, or CRM integrations such as Epic, Cerner, Salesforce Health Cloud, etc.). - Strong internal and external collaboration skills; proven success working with healthcare compliance, security, and IT stakeholders. - Willingness to travel 20–50% for customer and internal meetings. Now Benefits: we have several items. - 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. We could also include "Other Types of Pay" under Pay section. Pay section: - Pay Range (OTE): $157,000 - $235,000 - 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 could combine into list. Now we need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have both Requirements and Qualifications maybe overlapping. The posting has Core Background (requirements) and Desirable Heath & Life Sciences Experience (skills/qualifications). Could treat Core Background as Requirements, and Desirable Heath & Life Sciences Experience as Skills. Qualifications maybe not needed separately. But we could also have Qualifications as same as Requirements? To avoid thin sections, we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings if we have content. We can choose to include Requirements and Qualifications separately if we have distinct content. We have Core Background (requirements) and Desirable Heath & Life Sciences Experience (skills). Could treat Core Background as Requirements, and Desirable Heath & Life Sciences Experience as Skills. Qualifications maybe not needed; we could omit Qualifications section to avoid thin. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Check if any content for Schedule: none, omit. Now ensure we don't include boilerplate like "Work Environment and Physical Requirements:" etc. Remove. Now produce HTML. Structure:

  About the role

  ...intro...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  • ...
  ...
  Make sure to preserve all details exactly as in posting. Need to watch punctuation and special characters like –, —, etc. We'll keep as is. Check for any duplicated lines: we should not repeat. Ensure each bullet appears once. Now craft. Intro paragraph