Solution Architect (with hand on Technical skillls) who can move fluidly between designing end-to-end integration solutions (HLD/LLD, ADRs, sequence and data-flow diagrams) and going hands-on in code, infrastructure, and production issues. This is not a purely design-facing or purely hands-on role but a person that can do both, and work with onsite Lead Architect on a daily basis.
Architecture & Design
• Co-own solution design for Health integration programs — healthcare document/record retrieval, EMR (Epic) integrations, ROI/canvassing workflows, and downstream systems (Digital House, Maestro, Tangible, HIDS retrieval services).
• Produce and maintain design artifacts consistent with existing program documentation: motivations, scope of review, compromises/trade-offs, architecture diagrams, and service-level change descriptions.
• Participate in architecture decisions as a second reviewer/co-author, not just an implementer — able to defend design trade-offs to stakeholders and Jira/PM leads.
• Build working knowledge of the existing Health service landscape (e.g., hids-digital-retrieval-service and related services) quickly enough to propose changes independently within the first few months.
Hands-On Engineering & Operations
• Integration & API work: design, build, and debug REST/JSON APIs, OAuth2/JWT-based service-to-service auth, webhooks, and vendor API integrations (e.g., Tangible, Epic FHIR endpoints).
• Cloud & infrastructure: AWS scaling and infra troubleshooting, environment configuration, and capacity issues.
• CI/CD & quality: pipeline maintenance, automation, unit testing, and release support; comfortable resolving merge conflicts and unblocking a team stuck in git.
• Security & credentials: certificate expiry, encryption key rotation/issues, and authentication/authorization troubleshooting (the team is already tracking a planned move from basic auth to bearer/JWT that this role can help drive).
• Production support: triage alerts, diagnosing performance issues, and lead or support incident response across services in scope.
• Data: troubleshoot data-related issues in document/record retrieval flows, including mapping and normalization across vendor responses.
• Migrations: support service and API migrations (e.g., legacy-to-new-vendor API cutovers) with minimal disruption to in-flight requests.
Requirements
Required Skills & Experience
• 12–18+ years in software engineering with 3+ years in a Solution/Technical Architect capacity spanning design and hands-on delivery.
• Strong API design and integration experience — REST, JSON, OAuth2/JWT, webhooks, service-to-service authentication.
• Working AWS experience: scaling, infra troubleshooting, common services used in a services-based backend.
• Solid CI/CD, git (including resolving merge conflicts), automated testing, and release engineering fundamentals.
• Practical security exposure: certificate management, encryption/key handling, auth troubleshooting.
• Comfortable owning production issues end-to-end: alert triage, performance debugging, root-cause analysis.
• Experience with data migrations or system cutovers with real production stakes.
• Able to write and review architecture artifacts (HLD/LLD, ADRs) that hold up to stakeholder and delivery scrutiny.
Domain Fit
• Healthcare interoperability exposure: EMR systems (especially Epic), FHIR, ROI (Release of Information) workflows, HIPAA/PHI handling.
• Experience integrating with or building on top of vendor medical-records APIs (Epic app model, document/record retrieval vendors).
• Prior work in a services-based microservice environment with multiple downstream partner integrations.