Under minimal direction, the Enterprise Architect is responsible for designing cloud-native solutions, deconstructing our legacy architecture, and defining clear, executable roadmaps to modernize OCFCU’s technology platforms.
This role will work across core banking (Symitar/Episys), digital banking (e.g., Lumin), lending & payments, data & analytics, and integration platforms to move OCFCU from tightly coupled legacy systems to modern, scalable, secure, and observable architectures. This includes leveraging cloud services, APIs, event-driven patterns, and AI/LLM capabilities where they make sense, and ensuring everything is properly documented and ready for handoff to Operations.
This role will spend a significant portion of time embedded with teams reviewing designs, building reference implementations, prototyping, and helping teams ship better systems that can be operated reliably by OCFCU’s Infrastructure and Operations teams.
ESSENTIAL FUNCTIONS
1. Enterprise & Solution Architecture (Hands-On)
- 01Designs target-state architecture for key OCFCU domains including:
- 02Core banking & surrounding ecosystem (Symitar, Jack Henry integrations, payments, statements, ancillary services).
- 03Digital banking channels (online, mobile, APIs, third-party fintech integrations).
- 04Lending, onboarding, and back-office platforms.
- 05Creates end-to-end solution designs: context diagrams, sequence/flow diagrams, APIs, data models, non-functional requirements (NFRs), and security patterns.
- 06Develop reference architecture for:
- 07Cloud-native services (e.g., Azure/AWS), APIs, and integration layers.
- 08Event-driven workflows (e.g., member activity, transactions, alerts, service).
- 09Builds and maintains a living architecture blueprint and application portfolio for OCFCU, including current state, target state, and interim milestones that align with the technology roadmap.
2. Legacy Decomposition & Modernization
- 10Deep-dives into OCFCU’s existing legacy and vendor platforms: Symitar customizations, batch jobs, flat-file/EDI interfaces, on-prem services, and custom applications.
- 11Documents current-state architectures, dependencies, data flows, and technical debt in a form usable by engineers, operations, and leadership.
- 12Defines pragmatic modernization strategies, such as:
- 13Encapsulating legacy systems via APIs.
- 14Strangler patterns to incrementally replace monolithic functionality.
- 15Re-platforming or re-architecting high-risk/high-value components.
- 16Prioritizes modernization efforts in partnership with the CIO, VP-level leaders, and business/product owners based on member impact, operational risk, and business value.
- 17Works closely with delivery teams to execute modernization iteratively, favoring measurable wins over “big bang” cutovers.
3. Cloud-Native & AI/LLM Patterns for Financial Services
- 18Designs solutions that leverage cloud platforms (e.g., Azure/AWS) with a focus on:
- 19Security and regulatory compliance (NCUA, FFIEC, GLBA).
- 20Resiliency, performance, and cost optimization.
- 21Observability (logging, metrics, tracing, dashboards).
- 23Containerization and/or serverless workloads.
- 24API gateways, integration hubs, and secure connectivity to Symitar and other vendors.
- 25Messaging/event-driven architectures (e.g., for real-time alerts, fraud signals, member interactions).
- 26Establishes reference patterns for integrating AI/LLM capabilities into OCFCU workflows and member experiences, such as:
- 27Intelligent document processing (KYC, loan docs, servicing).
- 28AI-powered member support, agent assist, and knowledge retrieval.
- 29Analytics and decisioning enhancements (working with Data & Analytics teams).
- 30Partners with InfoSec and Risk to ensure AI use follows appropriate governance, privacy, and model/data protection practices.
4. Technical Leadership, Delivery Support & Handoff to Operations
- 31Embeds with OCFCU project teams and squads on critical initiatives as the lead architect, participating in design sessions, code/design reviews, and troubleshooting.
- 32Builds prototypes and reference implementations that:
- 33Demonstrate new patterns (e.g., new API gateway patterns, event bus usage, AI integration).
- 34De-risk complex integrations between core, digital banking, and external fintech partners.
- 35Provides hands-on guidance on API design, domain modeling (including domain-driven design where appropriate), data flows, and integration strategies around Symitar and other key platforms.
- 36Helps teams make thoughtful tradeoffs between the “ideal” architecture and practical delivery constraints, always ensuring a clear path toward the target state.
- 37Ensure solutions are fully prepared for handoff to Operations, including:
- 38Up-to-date architecture diagrams and system overviews.
- 39Runbooks, support models, and escalation paths.
- 40Defined SLOs/SLAs and capacity/performance expectations.
- 41Clear ownership boundaries between Application, Infrastructure, Security, and vendor teams.
- 42Collaborates closely with Infrastructure, Operations, and Service Desk teams to confirm monitoring, alerting, backup, and recovery procedures are in place before go-live.
5. Architecture Standards, Governance & Documentation
- 43Defines lightweight architecture principles and standards tailored to a credit union environment, focusing on member experience, security, resilience, and simplicity.
- 44Participates in or leads architecture/design reviews for major OCFCU initiatives, evaluating risk, reusability, and alignment with OCFCU’s target architecture.
- 45Maintains clear, concise architectural documentation (diagrams, architecture decision records, standards) that engineers, operations, and auditors can rely on.
- 46Partners with InfoSec, Risk, and Compliance to ensure that architecture support OCFCU’s obligations around data protection, business continuity, vendor management, and incident response.
6. Stakeholder Collaboration & Communication
- 47Translates complex technical topics into clear, non-technical language for OCFCU leadership, risk committees, and business partners—highlighting options, tradeoffs, and risks.
- 48Partners with leaders in Digital Banking, Core & Operations, Lending, Member Experience, and Data & Analytics to ensure architectures support their strategies and roadmaps.
- 49Contributes to OCFCU’s multi-year technology roadmap, including:
- 50Core & digital modernization.
- 51Data & analytics platform evolution.
- 52Integration and automation capabilities.
- 53Mentors’ senior engineers and technical leads in good architecture practices and patterns, helping to raise the architectural maturity across the organization.