Technical Support Engineer

Paradigm Health
•$120,000 - $150,000•Hybrid

About The Position

Paradigm Health is rebuilding the clinical research ecosystem to enable equitable access to trials. The Technical Support Engineer role combines responsive Tier 1 support with the technical investigation depth of Tier 2. The engineer uses purpose-built dashboards, investigation tools, and AI-assisted agents to resolve tickets autonomously, reduce dependency on Engineering and Product, diagnose root causes, and continuously improve support operations. The role supports research sites, sponsor teams, and Clinical Operations staff. It includes responding to common platform and workflow issues, investigating clinical data and interface problems, building support tooling and automation, maintaining documentation, tracking support KPIs, and collaborating with Engineering, Product, Informatics, and Technical Services.

Requirements

  • Bachelor's degree in health informatics, life sciences, computer science, clinical research, or a related field, or equivalent professional experience.
  • 6–9 years in technical support, data operations, or a client-facing technical role; health tech or regulated SaaS experience is strongly preferred.
  • Working knowledge of clinical research operations, including IRB, CRF, EDC, site coordinator workflows, and the patient recruitment lifecycle.
  • Hands-on SQL experience, including querying databases to trace data flow, validate pipeline outputs, and identify missing or anomalous records.
  • Familiarity with data integration concepts, including HL7 (SIU, ADT), FHIR, file-based ETL, and interface monitoring.
  • HIPAA compliance knowledge and experience handling PHI in a technology context.
  • Proficiency with Zendesk or an equivalent support platform, including configuration and reporting.
  • Strong analytical and written communication skills, with the ability to produce rigorous root cause summaries for technical and non-technical audiences.

Nice To Haves

  • Experience building internal tooling, dashboards, or lightweight investigation apps using Python, no-code/low-code tools, or similar.
  • Exposure to AI/LLM-assisted support tooling, triage agents, or workflow automation.
  • Familiarity with EHR systems such as Epic or Cerner and how clinical data is structured and delivered.
  • Experience with clinical trial platforms, including CTMS, EDC (Medidata, Veeva), IRT, or eConsent systems.
  • Understanding of 21 CFR Part 11 for electronic records in regulated clinical environments.
  • CCRP, CCRA, CPHIMS, or equivalent clinical/health informatics certification.

Responsibilities

  • Serve as the primary contact for inbound support tickets from research sites, sponsor teams, and Clinical Operations staff through Zendesk.
  • Categorize, prioritize, and resolve common break-fix issues, including login and access, account provisioning, platform navigation, and standard trial workflow questions, within defined SLAs.
  • Monitor trial SLA milestones using support dashboards and proactively flag anomalies.
  • Provide clear, timely, and professional responses to clinical coordinators, PIs, and sponsor program managers.
  • Investigate data discrepancies across EHR/interface ingestion, department data filters, patient matching logic, and application presentation.
  • Diagnose interface-related issues by reviewing interface go-live timelines, delivery logs, and ingestion history.
  • Triage patient-trial identification feedback and route findings to the appropriate team.
  • Perform root cause analysis and produce summaries for external users and internal stakeholders.
  • Build and maintain internal support tooling, including investigation dashboards, triage applications, and AI-assisted agents.
  • Configure and optimize Zendesk to surface actionable metrics and support continuous improvement.
  • Identify recurring issue patterns and build automated detection and response workflows where appropriate.
  • Maintain and expand the internal knowledge base, including runbooks, issue playbooks, escalation criteria, and resolution documentation.
  • Participate in UAT and product release cycles to anticipate support scenarios and update tooling.
  • Liaise between Support and Engineering, Product, Informatics, and Technical Services, translating ticket patterns into defect reports and product feedback.
  • Maintain accurate ticket records and consistent tagging, priority, and resolution codes.
  • Track and report core support KPIs, including first-contact resolution rate, mean resolution time, escalation-to-engineering ratio, and ticket leakage rate.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service