Mobile Architect

A strategically important mobile banking and payments platform with native Android and iOS applications, a substantial Java backend and an internally developed integration component.

• Enterprise Architect level experience with strong Java backend and integration architecture background.
• Deep understanding of modular monoliths, service-oriented and microservice architectures, domain-driven design, and modernization patterns.
• Strong API and integration architecture skills including synchronous and asynchronous patterns and ownership boundaries.
• Experience assessing legacy or evolved BFF/backend platforms and defining incremental modernization approaches.
• Knowledge of banking and payments domains and business capability mapping; experience with BIAN is advantageous.
• Strong understanding of performance, resilience, observability, recovery, and production operability.
• Experience producing C4-style architecture views, target and transition architecture, and modernization roadmaps.
• Ability to operate at enterprise level across technology, business capability, governance, and operating model concerns.
• Strong stakeholder facilitation and executive communication skills in English.

• Assess the current Java backend, originally designed as a BFF but now containing substantial business logic and monolithic characteristics.
• Map backend modules, dependencies, data flows, APIs, integrations and downstream systems to identify coupling and architectural hotspots.
• Assess the internally developed integration component, focusing on migration of business logic and ownership risks.
• Evaluate modularity and decomposition options without defaulting to microservices and recommend pragmatic target boundaries and transition steps.
• Map business capabilities to backend implementation, ownership, and maturity; use BIAN as a reference model where valuable.
• Assess non-functional characteristics including performance, scalability, resilience, recovery, observability, capacity, and operability.
• Review security architecture, trust boundaries, cryptography, and sensitive-data flows across backend and integration components.
• Define target and transition architecture, integration patterns, migration guardrails and prioritized modernization initiatives.
• Identify architectural risks, technical debt, duplicated responsibilities, and dependencies constraining change velocity.
• Contribute to the target operating model including decision rights, standards, exception process, RACI, foundation-team remit, and governance forums.
• Lead technical workshops and translate findings into prioritized recommendations and an implementation roadmap.