The Solutions Architect plays a critical role in designing secure, scalable, cloud-native solutions for Lirio’s platform across both our Lirio-hosted SaaS environment and our customer-hosted deployment model.
This Solutions Architect role is primarily focused on Microsoft ecosystem integrations, including Azure, Power Platform, Dynamics 365 and Dataverse, and Copilot-enabled experiences.
Partnering with Product, Engineering, Cloud, Data, AI, and Behavioral Science teams to translate product and client requirements into actionable system, integration, and data designs aligned with Lirio’s architecture standards.
Defining clear integration boundaries between Lirio and customer ecosystems, including system-of-record decisions, data ownership, and stable integration contracts that meet latency, scale, reliability, and compliance requirements.
Designing the agentic layer of the Lirio solution, including AI-centered workflows, services, and interoperability.
Contributing to Lirio’s Architecture Team, shaping work before it enters delivery, producing design artifacts, and building prototypes or reference integrations to validate patterns and reduce customer-by-customer variability.
Requirements
10+ years of related experience
Experience designing distributed, cloud-native systems in SaaS or large-scale enterprise environments.
Experience designing agentic products and workflows where the product is a component in a larger Agent ecosystem.
Experience working closely with cross-functional technical and product teams.
Healthcare or other regulated industry experience preferred.
Expert knowledge of software architecture and the Azure ecosystem.
Dynamics 365 (including Customer Insights – Journeys) and Dataverse.
Dataverse integration architecture (data model familiarity, Web API integration patterns, incremental synchronization approaches, and reliability-at-scale practices such as batching/retries/caching/idempotency).
Power Platform delivery and governance (solutions, environment strategy, lifecycle/deployment practices, and enterprise guardrails including DLP).
Copilot and agent integration patterns (designing secure actions/connectors/tools that invoke external services and return structured outputs).
Microsoft Entra ID security patterns (app registrations, least-privilege design, cross-tenant access where required, and secure service-to-service identity patterns).