Mobile Architect

Description of the role/requirements:

Key responsibilities:

• 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, especially the migration of business logic into the integration layer and resulting ownership risks.

• Evaluate modularity and decomposition options without defaulting to microservices; recommend pragmatic target boundaries and transition steps.

• Map business capabilities to backend implementation, ownership and maturity; use BIAN as a reference model where it adds value.

• 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 that constrain change velocity.

• Contribute to the target operating model: architecture decision rights, standards, exception process, RACI, foundation-team remit and governance forums.

• Lead technical workshops and translate evidence into prioritized recommendations and an implementation roadmap.

Expected experience / skills:

• Enterprise Architect level experience with a strong Java/backend and integration architecture background.

• Deep understanding of modular monoliths, service-oriented/microservice architectures, domain-driven design and modernization patterns.

• Strong API and integration architecture skills, including synchronous/asynchronous patterns and ownership boundaries.

• Experience assessing legacy or evolved BFF/backend platforms and defining incremental modernization rather than big-bang replacement.

• Knowledge of banking and payments domains and business capability mapping; BIAN experience is an advantage.

• Strong understanding of performance, resilience, observability, recovery and production operability.

• Experience producing C4-style architecture views, target/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;

Description of the project:

A strategically important mobile banking and payments platform with native Android and iOS applications, a substantial Java backend and an internally developed integration component. The current Java backend was originally conceived as a Backend-for-Frontend (BFF), but has accumulated significant business logic and exhibits monolithic characteristics. Business logic is also emerging in the integration component, creating risks around ownership, duplicated responsibilities and architectural boundaries. The assessment will establish an evidence-based view of the current architecture and define an incremental path forward rather than change for its own sake. The scope covers architecture and integration, business capability alignment, mobile/BFF interaction, security and cryptography, quality and operability, and governance/operating model. Expected outputs include a workshop series, assessment workbook, recommendations deck, target and transition architecture, business capability map and target operating model. The proposed delivery approach consists of Mobilise, Discover, Shape and Validate phases, with approximately 10–12 workshops and an overall assessment duration of approximately 5–7 weeks, subject to final mobilisation and scheduling.