SOLUTION ARCHITECT
Job Description
Job purpose
The Solution Architect is responsible for transforming approved business and technical solution requirements into secure, scalable, resilient, maintainable and implementation-ready solution architectures aligned with the Bank's enterprise architecture, technology strategy and engineering standards.
The role provides end-to-end technical architecture leadership across applications, microservices, APIs, enterprise integrations, data, security, identity, platforms, cloud/container environments, DevSecOps, observability and operational resilience.
The Solution Architect shall own the solution architecture lifecycle from: Validated Solution Definition, Architecture Options, Architecture Decisions, HLD, LLD, Implementation-Ready Architecture, Architecture Review & Approval, Engineering Handover, Implementation Assurance, Architecture Change Control.
The Solution Architect must be capable of making and defending technical decisions based on business requirements, architectural principles, engineering trade-offs, security, resilience, cost, operational complexity and long-term technology strategy. This is a hands-on architecture and engineering leadership role, not a documentation, coordination, or project-management role.
Principal responsibilities
Solution Architecture Ownership: Own end-to-end technical architecture for assigned initiatives from validated solution requirements through implementation and production readiness.
•
Architecture Options & Trade-off Analysis: Develop and objectively evaluate architecture alternatives considering business value, complexity, security, resilience, scalability, maintainability, cost, technology maturity and strategic alignment.
•
Architecture Decision Making: Establish and document significant technical decisions through ADRs and other approved governance mechanisms, including rationale, alternatives, trade-offs and consequences.
•
High-Level Architecture Design: Produce HLDs defining system context, architectural boundaries, major components, integrations, security zones, data flows, platforms, external dependencies and deployment topology.
•
Low-Level / Implementation-Ready Architecture: Develop sufficiently detailed LLDs covering components, interfaces, APIs, events, queues, persistence, state management, failure handling, security controls, deployment, observability and runtime behavior to guide engineering implementation.
•
Application Architecture: Define appropriate application architecture including modular monoliths, microservices, event-driven architectures, distributed systems, micro-frontends and other patterns based on justified requirements rather than technology preference.
•
Integration Architecture: Define integration boundaries, APIs, ESB/API Gateway usage, synchronous/asynchronous patterns, messaging, events, orchestration/choreography, service contracts, retries, idempotency, reconciliation and failure handling.
•
API & Contract ArchitectureGovern API/service boundaries, contracts, versioning, security, lifecycle, reuse, interoperability and backward compatibility.
•
Data & Persistence Architecture: Define transactional boundaries, persistence patterns, relational/NoSQL selection, caching, data consistency, ownership, replication, CDC and other application-level data architecture requirements in alignment with enterprise data standards.
•
Security Architecture: Translate security requirements into architecture covering IAM, OAuth2/OIDC, authorization, service identities, TLS/mTLS, encryption, secrets, network boundaries, API security, auditability and zero-trust principles.
•
Resilience & Distributed Systems Design: Architect solutions for high availability, fault tolerance, timeouts, retries, circuit breakers, bulkheads, idempotency, graceful degradation, recovery, reconciliation and disaster scenarios.
•
Platform & Deployment Architecture: Define how solutions are deployed and operated across Kubernetes/container platforms, cloud/on-premises environments, middleware, databases, messaging infrastructure and other runtime platforms.
•
DevSecOps Architecture: Ensure architecture is compatible with Git-based source management, CI/CD, automated testing, security scanning, artifact management, infrastructure automation and controlled deployment practices.
•
Observability Architecture: Define logging, metrics, distributed tracing, correlation, dashboards, alerting and telemetry requirements using enterprise observability capabilities.
•
NFR Architecture: Translate approved NFRs into measurable architectural mechanisms addressing availability, performance, scalability, capacity, security, resilience, recoverability and maintainability.
•
Log in to read the full job — and 1256 more open right now
You are reading the opening of this advert. An account is free and opens the rest of it, including the requirements and exactly how to apply before the deadline.
- The complete description, requirements and how to apply
- Build a professional CV aimed at this exact role
- Link your WhatsApp and get every morning’s new jobs sent to you
How to Apply
The employer’s application route — the email, portal or form, and the deadline — opens as soon as you have a free account.
Create a free account or log in