Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
Outcomes® is seeking a Technical Support Engineer II to join our Support Engineering team in Orlando. The role focuses on owning complex customer investigations across pharmacy platforms, workflows, software, data, hardware, and integrations, while applying established troubleshooting and escalation practices.
Projects may include priority-incident leadership, on-site support, mentoring, and development of support automation.
The Technical Support Engineer II is an experienced individual contributor and technical escalation resource within Support Engineering. The role routinely owns complex customer investigations across pharmacy platforms, integrated workflows, software, data, operating systems, hardware and peripheral environments, integrations, and customer-specific configurations. The engineer independently applies established troubleshooting, change-control, security, and escalation practices; partners with Incident Management, Product Engineering, Product Management, IT, vendors, and customer-facing teams; and produces complete technical findings that enable efficient resolution. Depending on business need and assignment, the role may participate in priority-incident technical leadership, on-call coverage, cross-regional handoffs, customer-site support, mentoring, and development of support automation. Senior or Lead-level ownership of support strategy, organizational standards, or broad technical direction is outside the routine scope of this position.
Own complex, high-impact, or unresolved customer investigations through resolution, approved handoff, or closure. Troubleshoot Rx30, Computer-Rx, point-of-sale and integrated workflows, Windows and Linux environments, hardware, peripherals, workstations, software, data, and basic network or connectivity contributors. Reproduce behavior, review evidence, analyze logs and system data, isolate likely causes, document findings, validate results, and upscale high-risk or unusual matters appropriately. Production changes, configuration changes, data remediation, scripts, and deployments must follow established review, testing, approval, audit, and change-control requirements. Security-sensitive, broadly customer-impacting, or high-risk actions require approval from the designated technical, security, or business owner before execution.
When assigned, serve as the Technical Lead for support-owned priority incidents. The Technical Lead owns technical triage, containment and mitigation recommendations, recovery execution, and recovery validation. The Incident Manager owns incident coordination, stakeholder cadence, communications, timeline management, and overall process facilitation. The Technical Lead provides structured technical updates, identifies technical risks and decision points, and contributes findings, Problem Management inputs, and corrective actions to post-incident reviews. Technical actions remain subject to role authority and required production, security, and customer-impact approvals.
Determine whether issues represent software defects, data conditions, configuration problems, environmental factors, integration failures, training opportunities, or expected behavior. Partner with Product Engineering, Product Management, IT, vendors, and customer-facing teams to reproduce defects, validate findings, clarify ownership, and drive resolution. Provide a complete escalation package containing customer and business impact, supporting evidence, troubleshooting completed, reproduction information, relevant environment details, a working hypothesis, and the specific action or decision requested. Escalations are expected to contain sufficient, accurate information for the receiving team to begin work without avoidable rework or repeated discovery.
When requested or when meaningful progress can continue outside the originating region's working hours, maintain case continuity primarily through structured handoffs. Handoffs must identify current status, customer impact, evidence and troubleshooting completed, working hypothesis, owners, blockers, requested action, and next steps. Cross-regional support does not imply continuous individual availability outside the employee's assigned schedule.
As a core responsibility, read existing application code and system behavior, use relational database concepts, and develop appropriately scoped investigation or remediation approaches. Effectively leverage approved AI-assisted tools to support technical triage, code and system exploration, troubleshooting, solution development, documentation, and appropriately scoped code changes. When assigned and approved, create scripts, queries, utilities, diagnostic tools, automation, code changes, configuration changes, or data-remediation solutions. Engineers remain responsible for validating AI-assisted analysis and outputs. All changes must follow applicable source-control, peer-review, testing, deployment, security, audit, data-handling, and change-management requirements. Document expected and actual results, limitations, approvals, and follow-up work.
Routinely create and maintain accurate troubleshooting documentation, diagnostic procedures, escalation guidance, known-error records, and knowledge articles based on completed work. When assigned, provide peer coaching, escalation feedback, scenario review, and just-in-time technical guidance.
When business need and leadership approval require onsite support, travel to customer locations to perform hands-on troubleshooting, validate environmental factors, coordinate resolution activities, and document findings. Routinely identify recurring incident and escalation drivers and recommend practical improvements to process, tooling, documentation, monitoring, supportability, and training. Implementation of automation or broader improvements occurs when prioritized and assigned.
Apply secure coding, data-handling, access-control, approval, and change-management practices, including appropriate protection of PHI and other sensitive information. Translate technical findings into clear business language and balance customer impact, urgency, risk, effort, and long-term supportability when recommending actions or workarounds. Do not independently execute security-sensitive, broadly customer-impacting, or high-risk changes without the required approval.