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

for headings. Use

• for lists. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Thus we need to include all substantive info from posting, but we can combine similar items. Let's extract substantive content: About the role paragraph(s): "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 role. Responsibilities list (Key Responsibilities): - 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 sentences are long; we can keep as is. Core Background (Requirements/Qualifications): - 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. Desirable Heath & Life Sciences Experience (maybe Qualifications/Skills): - 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. Benefits: - 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. Pay: - 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. Schedule: - Willingness to travel 20–50% for customer and internal meetings. (maybe also mention 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.) That's work environment, not schedule. Could be included under Schedule? The instruction says include Schedule section only if posting actually states them. It does mention work environment but not schedule. Travel is schedule-related. We'll include travel under Schedule. We also have other info like "Method of Application: Apply online." etc which we must drop (application instructions). Also "Application Window: ..." drop. Also EEO etc drop. Also "Talkdesk is pioneering..." etc is marketing boilerplate; we should drop as it's not substantive about the job? It's about company but maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The marketing paragraph about Talkdesk being pioneer etc might be considered boilerplate? It's not EEO but could be considered fluff. However it's substantive about company but not job details. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The marketing paragraph is not about the job but about company; maybe it's considered boilerplate? It's not explicitly listed to remove, but it's not job-specific. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say remove marketing fluff. However earlier: "Prefer a few substantive sections over many thin ones." The marketing paragraph is not a section heading; we could include as a paragraph under About the role? But it's not about role. Might be considered not needed. I'd lean to omit it because it's not directly about the job and could be considered boilerplate. However it's not explicitly prohibited. But to be safe, I'd omit it because it's not required and could be considered fluff. The instruction says preserve ALL substantive information; if we consider it substantive about company, we might need to keep. But the job posting includes it as part of the description; it's substantive about the company. However the instruction about sections: we only need to output sections for role, responsibilities, etc. The marketing blurb could be placed under About the role as extra paragraph? But it's not about role. Might be considered duplicate of earlier? Not duplicate. Given the ambiguity, I'll include it as a paragraph under About the role? Actually the About the role already described role; adding company description may be okay. But the instruction says "Prefer a few substantive sections over many thin ones." Adding a paragraph about company may be thin. I'd omit. Also "Work Environment and Physical Requirements:" we could include under Schedule? Not schedule. Could be its own section? Not in allowed headings. Could be omitted. But it's substantive about work environment. However not in allowed headings list; we could maybe put under Schedule? Not appropriate. Could be omitted as not fitting headings. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding other headings not in list? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should only use those headings. So we should not add other headings like Work Environment. So we must drop that info or incorporate into existing sections if possible. Could incorporate travel under Schedule, and maybe mention "Primarily office-environment work..." under Schedule? Not really schedule. Could put under About the role as extra detail? Might be okay but not about role. Could put under Requirements? Not. Given constraints, I'll drop the Work Environment paragraph. Now we need to output HTML. Structure:

  About the role

  ... (the about role paragraph(s))

  Responsibilities

  • ... each responsibility

  Requirements

  • ... core background items (education, years experience, abilities, knowledge plus)

  Qualifications

  • ... desirable healthcare & life sciences experience items (excluding travel? travel goes to Schedule)

  Skills

  • ... maybe combine some overlapping? But we already used abilities in Requirements. Could move some to Skills. However we need to avoid duplication. Let's think: Requirements could be education and experience. Qualifications could be healthcare-specific experience. Skills could be presentation, problem solving, communication, knowledge of CRM, ITSM, etc., UCaaS, CCaaS, web/scripting. That seems logical. Thus