ROLE SUMMARY

The Solution Architect will work as an extension of the internal architecture team, taking assigned third party applications from documented business requirements through to developer ready design. The role produces design output continuously throughout the term rather than at the close of the engagement, operating within the institution's established design standards, documentation formats, and integration patterns.

PRIMARY RESPONSIBILITIES

• Determine the recommended integration approach and pattern for each assigned third party application.
• Select the applicable Ellucian Ethos APIs, resources, and endpoints, including the methods to be invoked.
• Define the data movement strategy, including directionality, frequency, batch or near real time treatment, and volume considerations, along with data element mappings and transformation logic.
• Recommend where Data Connect or Banner Extensibility is the correct mechanism, and identify requirements that can be satisfied through baseline functionality or vendor delivered capability rather than custom development.
• Document security, privacy, and access considerations, error handling and monitoring requirements, and the assumptions and open decisions the institution or its vendors need to resolve.
• Provide architecture advisory support to the internal team, participate in design workshops and solution review sessions, and provide written feedback on designs authored by the institution's own architects.
• Advise on the disposition of integrations built on tools and processes that are not SaaS safe.
• Transfer completed designs to the institution's developers through walkthrough sessions and provide clarification support during build.

REQUIRED BACKGROUND

• Demonstrated Banner solution architecture experience in a SaaS context, with working depth in Ellucian Ethos, Data Connect, and Banner Extensibility.
• Ability to assess existing on premise processes such as cron jobs, shell scripts, and direct database access, and define SaaS safe replacement patterns that preserve upgrade compatibility.
• Strong written design documentation, sufficient for a developer to build from without further architecture involvement.
• Ability to operate inside an established client process, including the institution's existing architecture meetings, work tracking, and communication channels.