Field Solutions Engineer

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. The posting includes: Position Summary (maybe About the role), Key Responsibilities, Qualifications, Preferred Qualifications, Key Attributes for Success, Working Conditions, Pay Transparency (including hiring range), Benefits of working at Lumeris (list), Location, Time Type, etc. Also there is "Position: Field Solutions Engineer" but we should not repeat job title as heading. Also we should not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Your Future is our Future At Lumeris..." maybe that's about the role? Could be considered "About the role". We'll need to preserve substantive info. We need to decide sections: About the role (maybe from opening paragraph and position summary). Responsibilities (Key Responsibilities). Qualifications (Qualifications). Preferred Qualifications maybe part of Qualifications or separate? Could be under Qualifications but we could have a "Qualifications" section that includes both required and preferred. Or we could have separate "Preferred Qualifications" but not required heading list includes Qualifications, Skills. We could put Skills under Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include those that have content. We have Responsibilities, Qualifications, Benefits, Pay. Possibly Skills (maybe from Key Attributes for Success). Could treat Key Attributes as Skills. Also we have Working Conditions maybe not needed. Location and Time Type maybe not needed as separate headings (Schedule? maybe not). The posting includes "Location: Virtual – Microsoft Teams" and "Time Type: Full time". That could be considered Schedule? Not exactly schedule but maybe we could put under Schedule if we have info. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state Benefits and Pay (hiring range). It does not explicitly state Schedule (like hours). It says Time Type: Full time, which could be considered schedule but not explicit schedule like "Mon-Fri 9-5". Might be okay to include Schedule section with "Full time". But better to avoid if not explicit schedule. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Benefits and Pay. For Schedule, it's not explicitly stated; "Time Type: Full time" maybe considered schedule but ambiguous. Safer to omit Schedule. Thus sections: About the role, Responsibilities, Qualifications, Skills (maybe from Key Attributes), Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections. Let's extract content. About the role: The opening paragraph: "Your Future is our Future At Lumeris, we believe that our greatest achievements are made possible by the talent and commitment of our team members. That's why we are actively seeking talented and collaborative individuals who are passionate about making a difference in the healthcare industry. Join us today as we strive to create a system of care that every doctor wants for their own family and become part of a community that values its people and empowers you to make an impact. We're excited to consider every qualified candidate authorized to work in the United States, although we are unable to sponsor visas for this role at this time." Also Position Summary: "As a Field Solutions Engineer, you are the primary, front-line solution partner and key technical specialist for customer pursuits. Supporting 2 to 3 Sales Leaders, you will engage deeply with prospective clients early in the sales cycle. Your core focus is to translate Lumeris’s complex product suite—specifically our AI capabilities ("Tom")—into tailored, clinically meaningful, and operationally viable solutions. You will go both deep and wide: deep into clinical workflows and data architecture, and wide across the prospects priorities and strategies to build trust, show what is possible, and ensure long-term delivery success." We can combine these into About the role section. Responsibilities: The "Key Responsibilities" bullet list with several items each with sub-bullets? Actually each responsibility is a heading then description. We need to capture all details. We'll produce a

  with each responsibility as
  • containing the description (maybe with further
    for subpoints?). The instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll keep each responsibility as
    • and inside we can have paragraphs. We need to preserve all details: Discovery & Solution Scoping, Clinical & Technical Storytelling (Demos & Workshops), Solution Blueprinting & Deal POV Strategy, Commercial Proposals & Value Case Development, Cross Functional Handoffs for Go Live Success. We'll include each as
    • with the description. Qualifications: The "Qualifications" bullet list (required). Then "Preferred Qualifications" bullet list. Also "Key Attributes for Success" maybe skills. We need to include all details. We'll put required qualifications as
      • items. Then maybe a separate

        for Preferred Qualifications? Not in allowed headings list but we could incorporate under Qualifications as separate

        with heading? But we cannot create new headings not in list? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

        for section headings (e.g ...)". It implies we should use those headings for sections. It doesn't say we cannot use other headings, but better to stick to those. We could put Preferred Qualifications inside Qualifications section as a note. Or we could treat Key Attributes as Skills. Thus Qualifications section will contain both required and preferred qualifications, maybe separated by a paragraph. Skills section: Could be Key Attributes for Success. Benefits: list of benefits. Pay: hiring range and note about factors. We must not include boilerplate like "Disclaimer:", "EEO/AA employer", etc. Also remove "Your Future is our Future..."? That's part of About the role, keep. Also remove "Position: Field Solutions Engineer" (job title) as heading; we already not using. Remove "Position Summary:" maybe treat as part of About. Remove "Job Description:" maybe not needed. Remove "Working Conditions" maybe not needed as separate section; but we could include as a paragraph under About? But it's substantive: "While performing the duties of this job, the employee works in normal office working conditions." Could be included in About the role or maybe as a separate paragraph. Since we have no specific heading for Working Conditions, we could include it in About the role as a paragraph. But we must preserve all substantive info; we can add a

        after the About role content. Similarly "Location: Virtual – Microsoft Teams" and "Time Type: Full time" could be included in About the role or maybe as a separate paragraph. We'll add a

        after About role. Also "Be part of a team that is changing healthcare!" is tagline; keep. Also "Member Facing Position: No- Not Member or Patient Facing Position Drug Screen Requirement: No MVR Required: No Credit Check Required: No" - these are metadata; we could drop as minor metadata? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." This is minor metadata; we can fold into a short

        or drop. Probably drop to keep concise. Also "Lumeris and its partners are committed to protecting our high-risk members & prospects when conducting business in-person..." etc. That's about vaccination requirement; could be considered minor metadata; maybe drop. Also "Disclaimer: ..." drop. Also "Lumeris is an EEO/AA employer M/F/V/D." drop. Now produce HTML. Structure:

        About the role

        ... (combined opening paragraph + position summary + location/time type + working conditions + tagline)

        Responsibilities

        • Discovery & Solution Scoping: Lead discovery sessions with clinical, technical, and operational executives and leaders to uncover current-state workflows, pain points, data infrastructure constraints, and strategic priorities. Map client requirements to viable, high-impact Tom use cases, defining how the platform can address the specific needs for the prospect account. Identify solution risks, feasibility issues, and implementation dependencies early, coordinating validation across cross-functional teams before commercial commitments are made.
        • Clinical & Technical Storytelling (Demos & Workshops): Deliver highly engaging, workflow-oriented custom demonstrations that illustrate the future state of care delivery enabled by Tom. Facilitate Tom Immersion Studio experiences, using clinical storytelling to make complex data, integration, and AI capabilities tangible for executive and clinical buyers. Bridge the gap between algorithmic/technical mechanics (such as AI models, RAG, and data ingestion) and clear business/clinical value.
        • Solution Blueprinting & Deal POV Strategy: Co-create deal-specific Points of View (POVs) and customized solution blueprints detailing use cases, integration/configuration assumptions, pilot parameters, and phased deployment approaches. Partner with Growth team account owners to craft account-level strategy, ensuring proposed solutions align with both client ambitions and Lumeris product scalability.
        • Commercial Proposals & Value Case Development: Partner with Finance and Revenue teams to co-develop client-specific value hypotheses, ROI models, and business-case inputs. Serve as a key technical contributor to RFIs, RFPs, and security questionnaires (DDQs), leveraging internal knowledge bases to address complex technical and clinical objections.
        • Cross Functional Handoffs for Go Live Success: Ensure a seamless, highly disciplined handoff from Sales to the Implementation and Customer Success teams. Provide thorough documentation of agreed-upon use cases, workflow designs, scoped parameters, success metrics, and clinical/technical assumptions to guarantee delivery integrity.

        Qualifications

        Required:

        • 7+ years of progressive experience in healthcare solution engineering, clinical transformation, healthcare consulting, technical pre-sales, or healthcare SaaS sales.
        • Deep understanding of provider/payer economics, population health management, and the operating priorities of health systems.
        • Proven ability to engage customer executives, clinical leadership (physicians, nursing executives), and technical practitioners. You can talk comfortably about APIs, EHR workflows, and clinical protocols in the same conversation.
        • Track record of active participation in complex, multi-stakeholder enterprise sales cycles with a focus on shaping custom technical/clinical strategies.
        • Strong presentation, facilitation, and clinical/technical storytelling skills, with the ability to distill highly complex topics into clear value propositions.

        Preferred:

        • A clinical degree or license (e.g., Registered Nurse (RN) or comparable clinical background) is highly preferred.
        • Experience working with AI-enabled healthcare platforms, Conversational AI, or modern data architectures (e.g., FHIR, HL7, cloud databases, and interoperability tools).
        • Experience in startup minded organization with the ability to pivot quickly, build new processes, and support ongoing iterations for tools, templates, and playbooks.

        Skills

        Key Attributes for Success:

        • You connect the dots between strategic enterprise goals, day-to-day clinical workflows, underlying technology, data structures, and financial ROI.
        • You balance a client's aspirational vision with Tom's platform capabilities, ensuring