Technology Architect

At Julius Baer, we celebrate and value the individual qualities you bring, enabling you to be impactful, to be entrepreneurial, to be empowered, and to create value beyond wealth. Let's shape the future of wealth management together.

The Technology Architect is responsible for a global architecture discipline (e.g., Application architecture, Integration architecture, Software architecture, Data Technology architecture, Security architecture, Infrastructure architecture, Operation architecture and Workplace).

He assesses technology needs across all Domains, defines target architectures, defines IT Architecture Standards & Guidelines, manages adherence to those minimal controls and drives agile and flexible delivery of sustainably and operable Technology services (platform-, infrastructure services).

• Determines need for technologies based on business, application capabilities and sustainably maintain them.
• Defines proper adoption of technologies, technology stacks and global standard platforms. If new technologies are needed the Technology Architect challenges the need and decides in RFIs/RFPs. Hereby adherence to strategic drivers (GMCs, KCs, Target Directions), such as complexity reduction, simplicity, reducing technology diversity and cloud acceleration are considered. Deviations are documented with Architecture Debts.
• Ensures compliance with IT Architecture Standards and Guidelines incl. NFRs. In case of deviations to Standards and Guidelines and/or an exception is needed, the Technology Architect (Standard Owner) is responsible for justifying options, mitigating actions and approving the exception.
• Ensures Data Quality of Architecture Repositories by supporting Application & Technology Responsibles to maintain update information about Technology, Technology Stacks, Information Flows, Applications mapping to Technologies in JBAR and corresponding Application-, Infrastructure Services in the CMDB (HPSM/ServiceNow).
• Contributes to technology driven aspects of the overall solution (Solution Blueprints + Designs) by evaluating the implementation of Reference Architectures and standard building blocks (network access and application gateways, databases, integration platforms, authentication, authorization and SSO, privileged access, monitoring and logging, etc.). For solutions not able or applicable using standard patterns, adherence to controls is justified (alternative options) and design deviations approved.
• Support Product Managers (PM), Product Owners (PO), Application Responsibles (AR) and (Lead) System / Domain Architects with Architecture Runway, guardrail adherence, NFRs and Architecture governance in general.
• Support Developers, Engineers and ITSO with Infrastructure Designs (incl. automation and orchestration of deployments), adoption of Integration patterns, collaboration with infrastructure teams and security designs/concepts.
• Manage NFR process by supporting delivery organization to implement NFRs, incl. verification, tracking and reporting of NFR adherence. Objective is to successfully implement NFRs (Architecture & Operations) before going live, starting with critical applications / services and extend to all Business Applications and Robots

(>1000). Currently >90% of all applications are not implementing NFRs properly and corr. key-control is not fulfilled. After CleanUp continue to manage NFR process for all upcoming changes.