Vind je volgende kans

Exerizon is a fast-growing strategy and technology consulting firm founded by former senior leaders from global consulting and cloud organizations. We help current and future market leaders tackle their greatest challenges — from digital strategy and cloud transformation to data & AI platforms and application modernization. We redefined the traditional consulting model: we share risk with our clients through impact-based remuneration, and we share ownership with our people from day one. We are looking for a Solution Architect (mid or senior) who understands healthcare from both sides: the clinical side (patient journey, care pathways, medical records, orders and results, diagnostics, telemedicine) and the commercial side (patient acquisition and scheduling, subscriptions and insurance products, B2B contracts, claims and billing, provider networks, customer service). You will design solutions for healthcare providers and insurers that span these two worlds — the systems that run a clinic and the systems that run the business around it. What you will do: Design end-to-end solution architectures for healthcare clients: patient-facing channels (web, mobile, contact center), scheduling and appointment management, medical records and clinical workflow, diagnostics (lab, imaging), telemedicine, subscription and insurance products, claims and billing, CRM and customer service, analytics Translate business and clinical needs into architecture: capability maps, current-state and target-state designs, options with trade-offs, and roadmaps — in language that both a medical director and a CFO can act on Own the solution design across the stack: application landscape, integration patterns (APIs, events, file-based exchange, integration engines), data model and data ownership, identity and access, and non-functional requirements (availability, performance, data residency) Design for regulation and clinical safety: GDPR health data, Polish medical records law, consent and audit trails, accessibility, and MDR considerations when software has a medical purpose Build on Azure (or AWS / GCP) with regulated-industry controls, and deliver the deployment architecture, not only the logical one Run build-vs-buy and vendor evaluations with knock-out gates and scored criteria (HIS / EHR, scheduling, CRM, contact center, integration, data platforms) and defend the recommendation with primary-source evidence Produce architecture deliverables that survive review: C4 and ArchiMate views, decision records, non-functional requirements, capacity and cost models Use AI tooling as a daily instrument for research, document production, data mapping and code review — with the discipline to verify every claim it makes before it reaches a client Work with client CIOs, CMIOs, business owners, clinical, data, security and legal teams; present and defend decisions in architecture forums; guide engineering teams through delivery Contribute to Exerizon's healthcare practice: reusable assets and reference architectures, proposals and pre-sales 5+ years (mid) or 8+ years (senior) in solution architecture or senior engineering roles with end-to-end design responsibility for production systems 2+ years in healthcare, on the provider or payer side, with a working understanding of both the clinical process (patient journey, care pathways, medical records, orders and results, diagnostics, telemedicine) and the commercial process (acquisition and scheduling, subscription and insurance products, B2B contracts and occupational medicine, claims and billing, provider networks, customer service) Solid architecture toolkit: integration patterns (REST / GraphQL APIs, event-driven, file transfer, integration engines), data modelling and data ownership, identity and access (OAuth2 / OIDC), non-functional requirements — and the judgement to choose boring technology when it fits Cloud architecture at the solution level on Azure or another hyperscaler: compute, networking, identity, data services, data residency, cost Experience designing for GDPR health data, consent and audit; familiarity with Polish medical records law and the EHDS direction Structured vendor and option evaluation: you define criteria before looking at products, verify claims against primary sources, and show your scoring Strong written and spoken communication: clear architecture documents and decision records, executive summaries, and the ability to defend a design under hostile review Full professional fluency in Polish and English Nice to have: Interoperability standards: HL7 FHIR, HL7 v2, IHE profiles, SMART on FHIR, openEHR — hands-on with a FHIR server Clinical terminologies (SNOMED CT, LOINC, ICD-10, ICD-9-PL) and terminology services Polish e-health ecosystem: P1 / e-zdrowie, e-recepta, e-skierowanie, EDM exchange, NFZ integrations Health insurance and subscription product systems: policy administration, claims, pricing, partner networks Data platforms and clinical analytics: lakehouse, OMOP CDM, medical NLP MDR and software-as-a-medical-device classification ArchiMate / LeanIX, TOGAF or Azure architect certifications Building your own AI tooling: custom agents, MCP servers or prompts for architecture and mapping work Real ownership of the architecture you design and direct contact with client CIOs and clinical leads — no ten-layer review pyramid Competitive compensation on B2B contract Annual training and certification budget Remote work model with access to a central Warsaw office A seat at the table in shaping a young firm: our healthcare practice, methods, hiring and culture