Solution Architect

Job Description

Solution Architects assess a project’s technical feasibility, as well as implementation risks. They are responsible for the design and implementation of the overall technical and solution architecture. They define the structure of a system, its interfaces, the solution principles guiding the organisation, the software design and the implementation. The scope of the Solution Architect’s role is defined by the business issue at hand. To fulfil the role, a Solution Architect utilises business and technology expertise and experience.  Provide technology leadership and solution architecture for large‑scale Cards, Lending, and Banking transformations, leveraging a modern Java and AWS ecosystem. The role focuses on client‑facing solution design, target‑state architecture definition, and mentoring design teams while driving application modernization and cloud adoption.

Job Description - Grade Specific

Key Responsibilities

• Design and review Java‑based application architectures aligned with cloud‑native principles and AWS best practices.
• Lead end‑to‑end solution architecture for enterprise banking and cards domain ecosystem, covering new application builds, modernization, and platform transformation initiatives.
• Provide architectural leadership across microservices adoption, API strategy, event‑driven design, and asynchronous processing.
• Drive architecture for interface development, including internal and external system integrations, third‑party services, and partner ecosystems.
• Engage with client stakeholders to understand business objectives, constraints, and regulatory needs, and translate them into scalable and resilient technical solutions.
• Define and govern to‑be architecture including application layers, integration strategy, data flows, security, and deployment models.
• Mentor and manage junior solution designers and aspiring architects, ensuring quality, consistency, and architecture governance.
• Support delivery teams through design walkthroughs, solution reviews, and implementation alignment
•  
• Domain Experience (Mandatory)

• Strong domain knowledge in Cards (Issuing and/or Acquiring) or Lending
• Understanding of banking transaction flows, authorization patterns, lifecycle events, and integration touchpoints.
• Exposure to regulatory, risk, and compliance considerations in financial systems.

Leadership & Stakeholder Skills

• Proven client‑facing experience, leading solution discussions and architecture workshops.
• Ability to influence design decisions and articulate complex solutions to both technical and non‑technical stakeholders.
• Experience guiding teams through architecture governance, design standards, and best practices.
• Strong coaching mindset to develop future architects and senior designers.