Applications Architect

Required Knowledge, Skills & Abilities

·       The Applications Architect must possess demonstrated knowledge of:

·       Enterprise application architecture patterns (layered/n‑tier, microservices, cloud‑native, event‑driven, domain‑driven design) and solution architecture practices (reference architectures, patterns, guardrails).

·       API and integration design: REST/JSON, GraphQL, gRPC, asynchronous messaging (queues, topics), event streaming, enterprise service buses, and API gateways.

·       Identity, security, and compliance: OAuth 2.0/OpenID Connect, SSO, role‑based access control, secrets management, encryption, secure SDLC, and alignment with state/federal standards in Medicaid/MES/FX programs.

·       DevOps and CI/CD: build/release pipelines, automated testing, artifact/version management, blue‑green/canary deployments, and infrastructure as code.

·       Observability and reliability engineering: logging, tracing, metrics, APM, performance/load testing, capacity planning, high availability, disaster recovery, and fault tolerance.

·       Relational database design and SQL fundamentals (including SQL Server schema design, indexing, query optimization) and how applications interact with enterprise data platforms (EDW/analytics).

·       Cloud platforms and services: designing application workloads on Azure and AWS, including compute, storage, networking, identity, monitoring, and platform services; integrating with enterprise data warehouse capabilities.

·       Governance and architecture practices: standards, reference models, technical debt management, and design reviews aligned to enterprise frameworks.

·       ASP.NET (Core & Framework), Blazor, C#, SQL Server/T‑SQL, .NET, Visual Studio/VS Code;

·       Azure App Service, Functions, API Management, Azure DevOps/GitHub Actions, Application Insights;

·       AWS ECS/Lambda/API Gateway; containers (Docker), orchestration (Kubernetes/AKS/EKS); Splunk Enterprise (observability), Tenable/Trend Micro (security).

·       Experience with agentic/AI frameworks (e.g., Codex, Claude) for workflow augmentation is a plus.

The Applications Architect must have the ability to:

·       Communicate complex technical concepts to non‑technical stakeholders and executive leadership in clear, outcome‑focused language.

·       Work independently with minimal supervision; demonstrate ownership and follow‑through.

·       Manage multiple priorities in a fast‑paced environment and make pragmatic tradeoffs.

·       Collaborate across bureaus, vendors, and leadership teams to drive consensus and delivery.

·       Adapt to evolving business and technical requirements while maintaining architectural integrity.

·       Support Agency objectives for Medicaid modernization and modular enterprise applications (FX/MES, Enterprise), including integration with EDW to enhance service delivery, flexibility, security, and outcomes for Floridians.

Preferred Experience

·       Experience leading Medicaid or public sector enterprise application implementations and modular FMMIS solutions (API‑first, configurable business rules).

·       Experience transitioning ownership of applications/platforms (vendor → state) and establishing sustainable operational models.

·       Familiarity with CMS reporting, federal data submissions, and analytics support from an application perspective (interfaces, data contracts, service orchestration).

·       Experience working in hybrid vendor/state environments and navigating governance/OCM practices.

·       Experience with large‑scale enterprise application development/system implementation projects across Azure & AWS.