Solution Architect - Agentic / AI Systems Architecture

Solution Architect - Agentic / AI Systems Architecture

ContractC2C Dallas, TX Visa: US CitizenGreen CardGC-EADH1BH4-EADTNEAD We need candidates who have experience in Agentic AI - Solution architecture with a Healthcare background. Solution Architect Dallas, TX 1. Agentic / AI systems architecture (the core differentiator) Multi-agent system design — this person architects against HAIO master-agent/sub-agent hierarchy and must design scheduling capabilities that plug into an agent platform someone else owns LLM application architecture: tool/function calling, orchestration patterns, prompt/context management, evaluation and guardrail design Browser-agent automation architecture — headless browser fleets (browserless.io specifically), designing agents that generalize to unseen websites, idempotency and duplicate-booking prevention, resilience to site changes and bot controls Fallback-chain / graceful-degradation design — the four-tier scheduling ladder (API browser agent dialer self-service) is fundamentally a resilience architecture problem 2. Integration architecture REST API integration at enterprise scale, webhook/event-driven architectures (the NexHealth confirm/modify/cancel event flows), API gateway patterns (they design against X42) EDI familiarity Healthcare interoperability is a strong plus: FHIR, HL7, EHR ecosystem knowledge (NexHealth syncs to EHRs — understanding what's underneath the API matters when things break) 3. ML / personalization system design Not building the models personally, but architecting the NBA orchestration layer: how propensity signals from pharmacy, health, and MinuteClinic domains resolve into one coherent recommendation Understanding of propensity/ranking models, feature pipelines, and event-driven personalization well enough to design contracts between the data layer (Adobe Analytics, member events) and the recommendation layer — especially tricky here because that data infrastructure is being built in parallel so the architecture must tolerate evolving signal sources 5. Healthcare domain & compliance fluency HIPAA/PHI data-flow design: data minimization in agent payloads, Clinical-appropriateness guardrail design — knowing that a recommendation engine in healthcare needs approved recommendation classes and prohibited ones, with compliance review gates Legal-exposure awareness for automation: T&C permissibility gating for the browser agent, TCPA-adjacent calling conduct for the dialer Prior payer/provider/pharmacy domain experience is what separates a good candidate from the right one here Ideal profile in one line: a hands-on architect (12–15+ years) who has shipped LLM/agentic systems in production, has healthcare payer or provider domain scars, has integrated against third-party scheduling or EHR APIs, and can operate as the client-facing technical face of a fixed-bid engagement. The two hardest-to-find intersections — and where I'd focus screening — are production agentic-AI experience + healthcare compliance fluency, and architecture depth + fixed-bid estimation discipline. Plenty of candidates have one side of each pair; this engagement genuinely needs both

Refer