Solution Architect

5)Delivery Excellence & Quality

• On-time delivery of milestones; manages dependencies and risks; Completeness of documentation (Solution Design, Runbooks, Deployment Guides);Coordinates with Dev for delivery, quality, readiness and sign-offs; Defect leakage and production incident rates; adherence to coding standards.

6)Business Impact & Value Realization

• Solutions demonstrably improve KPIs (cycle time, adoption, data quality);Proposes enhancements aligned to business roadmap

7)Leadership, Mentoring & Collaboration

• Coaches engineers/consultants; encourages best practices; Promotes standards, reusable assets, and knowledge sharing.

8)Continuous Learning & Innovation

• Pursues relevant certifications (eg. MB-700, PL-400/PL-200, AZ-204/AZ-300+);Pilots features from recent Dynamics 365 release waves; Applies AI/analytics (Copilot features, Power BI) to enhance processes.

Basic Team Responsibilities for a Solution Architect Include:

• Attending all Agile Ceremonies, including Daily Standup and Parking Lot, Sprint Planning, Sprint Demonstration, Sprint Retrospective. Meetings start promptly at the time indicated on the calendar, and team members are expected to have their cameras on during official Agile ceremonies.
• Additional Illinois Connect sessions where we’d require a Solution Architect: Inspect and Adapt, Program Increment Planning (in-person, unless remote is approved for unforeseen circumstances), Intact and Preventative Services Weekly Steering Committee (our team level senior leadership meeting).
• Work hours should be consistent with the rest of the team: 8:30 AM-5:00 PM Central Time. All overtime or time worked on weekends and holidays should be preapproved by Product Manager.
• Attendance at Project-Level Solution Architect sessions: I’d like to know when these are and what topics are being discussed. A general description up front, in addition to periodic updates from the Solution Architect would be appreciated.
• Team level work assignments will be tracked by JIRA tasks and will be assigned to the Solution Architect by the Scrum Lead in alignment with sprints. If there are directives that come from executive leadership aligned with project-level architectural decisions, those should be communicated to the Product Manager and Scrum Lead so we can track them as a JIRA task and factor this work in to the Solutions Architect’s capacity in the relevant sprint. If the Product Manager disagrees with the priority and is being directed by their division leadership to prioritize other initiatives, they will discuss this issue with the appropriate executive leadership to determine if an adjustment to work assignment needs to be made., * Developing a security framework that allows for users to have access to “cases” and “teams” contingent on case and team assignment, and assistance defining the concept of a “business unit” within the framework
• Providing additional clarification and finalizing the model for integrating with Family Engagement/Core Solution
• Developing the design for the “non-hotline intake” that will enable preventative services and child welfare cases to be opened when they do not originate from a hotline call or Investigation
• Establishing clear security boundaries between “child welfare cases” and “prevention cases”, as well as defining a mechanism that will allow for tracking of different program types within those cases
• Developing a design for “queues” that will replace the concept of “mailboxes” within the legacy system to allow for efficient “routing” of “cases” from one team to another, both within and cross business units
• Identifying downstream dependencies that impact finance and federal reporting, or other program areas

1)Technical Expertise

• Deep knowledge of Dynamics 365, proficiency of Power platform and Azure services, customization vs configuration judgement, Security & compliance

2)Solution Architecture & Design

• Produces scalable, maintainable architectures; clear logical/physical diagrams; Applies Microsoft-recommended patterns; Performance optimization;Fit-gap analysis and extensibility decisions aligned with product roadmap

3)Integration & Data Strategy

• Designs reliable integrations (REST, OData, Plugin messages, Azure Logic Apps); Master data and reference data governance; handling of multi-entity transactions.

4)Stakeholder Engagement & Communication

• Clear communication across business, devs, test, and change teams; Manages expectations; translates complex technical topics to business outcomes, * Required: Experience with Microsoft Dynamics .
• Required: Strong communication skills and the ability to translate technical terminology to business partners in non-technical roles
• Required: Ability to facilitate ongoing development work in alignment with design standards
• Required: Ability to conduct effective discovery to connect technical requirements to functional requirements
• Preferred: Experience in healthcare or public sector system
• Preferred: Experience utilizing a CRM for CCWIS or other public sector case management system