The posting
Experience: 10+ Years Role: System Analyst
Key Responsibilities
1. Technical Delivery & Systems Analysis
- Own tokenised deposit delivery across requirements → solution design → integration → testing → rollout.
- Produce engineering‑ready specifications:
- API specs (REST/JSON), OpenAPI/Swagger definitions Microservices interface contracts, event schemas, callback payloads Sequence diagrams, state machines, mapping specs, error models
- Define end‑to‑end orchestration flows for:
- Wallet creation, maintenance and payee registration Payment submission using tokenised deposits, including end-to-end authorization workflows. Payment pre-validation, rejection and return
- Specify robust pre‑processing logic:
- Customer/account validation Entitlement and authorisation checks Funds availability Fraud/AML/sanctions gating Limits, thresholds, duplicate suppression Idempotency, retry and timeout handling Lead the technical analysis, microservices integration design, and end‑to‑end delivery of’ Tokenised Deposits Platform. This role requires strong engineering expertise in API standards, microservices orchestration, event‑driven patterns, and reuse of existing platform components from previous projects. Key Responsibilities 1. Technical Delivery & Systems Analysis Own tokenised deposit delivery across requirements → solution design → integration → testing → rollout. Produce engineering‑ready specifications: API specs (REST/JSON), OpenAPI/Swagger definitions Microservices interface contracts, event schemas, callback payloads Sequence diagrams, state machines, mapping specs, error models Define end‑to‑end orchestration flows for: Wallet creation, maintenance and payee registration Payment submission using tokenised deposits, including end-to-end authorization workflows. Payment pre-validation, rejection and return Specify robust pre‑processing logic: Customer/account validation Entitlement and authorisation checks Funds availability Fraud/AML/sanctions gating Limits, thresholds, duplicate suppression Idempotency, retry and timeout handling 2. API & Microservices Architecture Define API and microservices designs using existing components from previous builds: Payment initiation microservices Validation & entitlement services Fraud/AML adapters Core banking and ledger integration patterns Reuse existing: API standards (naming conventions, response structures, error formats) Security models (OAuth2/JWT, mTLS, signature validation) Eventing patterns (Kafka topics, event schemas, DLQ handling) Common libraries for logging, telemetry, utility functions Ensure microservices follow engineering principles: Loose coupling, clear domain boundaries Async event‑driven integration where applicable High availability and horizontal scalability Observability (structured logs, metrics, tracing) 3. User Journeys, Entitlements & Authorisation Define user journeys for: Wallet and Payee creation and management Inward Payment using tokenised deposit query and advice report Tokenised Deposit Payment Authorization and return flows Align journeys with entitlements and auth rules: Per‑transaction and daily limits Maker‑checker workflows for corporates Channel‑specific access rights Coordinate with channel teams to maintain parity across Mobile, Internet Banking, H2H and API Banking. 4. Integration & Platform Engineering Design integration between: Payment Hub / RFP Orchestrator Token Custody and Payment Provider Payment Downstream and Integration Layer Core banking, ledger, AML, fraud Use existing microservices blueprints for: Error propagation and code mapping Schema validation and transformation Event lifecycle management Callback patterns and async updates 5. Scheme, Regulatory & Risk Alignment Translate Tokenised Deposit Payment scheme rules into: Validation rules Reason code mappings Reversal/return workflows Embed mandatory controls: AML/CFT & sanctions Fraud monitoring Non‑repudiation and evidence capture TRM, cybersecurity and audit trail requirements 6. Testing, Deployment & Operational Readiness Support SIT/UAT/E2E test scenario design for: Wallet and Payee creation or maintenance Inward and Outward Payment Workflows Timeouts, retries, negative tests Work with Engineering & Ops to ensure: Monitoring dashboards and alerts Reconciliation and exception queues Runbooks for replay, retry and operational fixes Support scheme certification and phased deployment. · Collaborate with Blockchain and Digital Assets, Payments, Treasury, Operations, Risk, and Compliance to refine use cases and delivery scope. Success Measures High‑quality Functional and Technical Design Delivery with minimal defects. Strong reuse of existing microservices, reducing build complexity and time‑to‑market. High STP rates, stable performance and consistent low‑latency behaviour. Clear, engineering‑ready specifications enabling smooth developer adoption. Strong governance alignment across Product, Engineering, Operations and Risk. Requirements: Key Skills & Experience Strong understanding of tokenised deposits, digital money architecture, and regulated digital assets. Strong engineering/technical skills: API design (REST/JSON, OpenAPI/Swagger) Microservices architecture Event‑driven patterns (Kafka or equivalent) State machine and sequence diagram modelling HA/DR and low‑latency systems Experience integrating with AML, fraud, entitlements and ledger systems. Ability to reuse and extend existing platform components and code frameworks. Leadership & Soft Skills Structured, analytical problem solver with strong documentation discipline. Ability to translate complex DLT and settlement concepts into clear requirements. Skilled at influencing and aligning diverse business, tech, and regulatory stakeholders. Strong ownership mindset and attention to detail. Key Skills: · Open API, Microservices · Java · Blockchain Technology and know-how · Digital Assets like Stablecoins, TokenizedDeposit, CBDC



