Sumitomo Mitsui Banking Corporation
1 week ago
VP of Integration Analytics - Sumitomo Mitsui Banking Corporation
Sign up to save this job, get alerts, and apply with an optimized CV.
Company information
- Company
- Sumitomo Mitsui Banking Corporation
- Location
- Singapore Singapore
- Posted
- 1 week ago
Job description
This candidate will assume the role of techno-functional System Analyst / Integration Specialist of APAC Payment Services Team to support the design and delivery of transaction banking payment platforms across Asia Pacific. The role bridges Payments requirements, architecture, and engineering, translating market, regulatory, operational, and enterprise-system needs into consistent, implementable technical solutions.
Key Responsibilities
Techno-Functional Analysis and Planning
• Plan analysis, design, testing, implementation, and migration activities with delivery, architecture, engineering, testing, and dependent-system teams.
• Translate business outcomes into detailed system, integration, data, operational, and non-functional requirements.
• Define end-to-end payment journeys, process flows, system interactions, event triggers, data handling, operational states, and exception scenarios.
• Perform fit-gap, impact, and risk assessments across current and target processes, systems, interfaces, and controls.
• Identify design decisions, constraints, assumptions, and dependencies early and drive them to closure.
Payments and Integration Design
• Apply Transaction Banking Payments knowledge across initiation, validation, enrichment, routing, screening, posting, clearing, settlement, returns, exceptions, reconciliation, and reporting.
• Determine whether market, regulatory, scheme, or enterprise-system requirements should be supported in the core payment platform, Payment Orchestration Layer, or surrounding integration services.
• Define end-to-end integration designs across Oracle Banking Payments, core banking, screening, messaging, clearing, settlement, and other enterprise systems.
• Own Integration Specification Documents covering interface contracts, message flows, security, error handling, retries, idempotency, audit, observability, and service-level requirements.
• Establish reusable API, event-driven, messaging, file-based, synchronous, and asynchronous integration patterns.
• Protect the consistency of the core payment platform by ensuring local deviations and system limitations are handled outside the product wherever appropriate.
Data Mapping and Technical Documentation
• Define standardized payment and integration data structures and maintain traceability to market, regulatory, product, and enterprise-system requirements.
• Produce source-to-target field mappings covering ownership, transformation, code translation, defaulting, enrichment, validation, and reconciliation rules.
• Define interface layouts and the handling of mandatory, optional, conditional, and repeating information.
• Maintain consistency in naming, definitions, message structures, relationships, and error semantics across interfaces.
• Create and maintain data-flow, sequence, component, class, logical, and physical integration diagrams as required.
Delivery, Testing and Governance
• Provide design oversight during build and testing, resolve engineering queries, and review implementation against approved requirements and designs.
• Ensure integration, end-to-end, negative, operational, and regression tests cover critical payment flows, failures, and exception scenarios.
• Support defect triage, impact analysis, root-cause identification, prioritization, and corrective-action design with Technical Leads and vendors.
• Coordinate integrated implementation requirements, configurations, cutover sequencing, runbooks, validation, rollback, migration, and reconciliation.
• Maintain end-to-end traceability from business and regulatory requirements through design, mapping, implementation, and test coverage.
• Review and quality-check requirements, designs, mappings, test specifications, configurations, and runbooks to identify gaps and inconsistencies.
• Participate in architecture reviews, design authorities, change control, defect governance, and payment-platform decision forums.
Stakeholder, Vendor and Capability Leadership
• Act as the techno-functional bridge across product, architecture, engineering, testing, operations, and vendors.
• Communicate design choices, trade-offs, risks, and impacts clearly to technical and senior non-technical stakeholders.
• Challenge vendor proposals and deliverables, ensuring SMBC retains ownership of requirements, mappings, integration standards, and design decisions.
• Build reusable templates, patterns, knowledge, and working practices to strengthen SMBC's internal System Analysis and Payments integration capability.
Requirements
Experience and Domain Knowledge
• Bachelor's degree in Information Technology, Computer Science, Engineering, or an equivalent discipline.
• Minimum 10 years of senior System Analyst, Integration Specialist, Solution Design, or related experience in financial services, preferably Payments or Transaction Banking.
• Strong knowledge of payments, clearing and settlement, exceptions, reconciliation, and payment-system integration.
• Experience with payment hubs or processing platforms; Oracle Banking Payments / OBPM / OBPay experience is strongly preferred.
• Knowledge of payment message standards and formats, preferably ISO 20022, SWIFT, domestic clearing, real-time payments, ACH, or RTGS.
• Working knowledge of financial-services regulation, security, operational resilience, and high-availability processing environments.
Technical and Delivery Skills
• Advanced experience in source-to-target field mapping, message and data modelling, transaction-flow analysis, and interface specification.
• Strong understanding of APIs, middleware, messaging, events, file-based integration, synchronous and asynchronous processing, and integration security.
• Ability to read and review diagrams, data models, API specifications, schemas, configurations, and technical designs.
• Ability to assess scalable, resilient, secure, observable, and operationally supportable integrations.
• Proven full-SDLC experience across analysis, design governance, testing, implementation, migration, and production support.
• Experience leading complex multi-system, multi-team, and multi-vendor initiatives through influence and collaboration.
Professional Attributes
• Strong analytical, problem-solving, facilitation, negotiation, and stakeholder-management skills.
• Excellent written and verbal communication, including executive-level presentation of complex technical topics.
• Detail-oriented, with a strong focus on accuracy, consistency, traceability, and design integrity.
• Ability to operate effectively across distributed business, technology, and vendor teams in a regulated environment.
Required skills
- communication
- negotiation skills
- engineering
- validation
- audit
- analysis
- operations
- analytical skills
- security
- reporting
- financial services
- information technology
- delivery
- collaboration
- testing
- prioritization
- problem-solving skills
- risk assessment
- architecture
- bachelor's degree
- api
- migration
- payments
- swift
- observability
- computer science
- events
- messaging
- stakeholder management
- vendor management
- product
- implementation
- api specifications
- iso 20022
- written communication
- verbal communication
- transformation
- knowledge sharing
- regulatory requirements
- returns
- system analyst
- technical documentation
- detail-oriented
- data modelling
- technical solutions
- configurations
- facilitation skills
- reconciliation
- real-time payments
- business outcomes
- integration testing
- regression testing
- settlement
- change control
- influence
- technical designs
- screening
- vendors
- data handling
- core banking
- traceability
- middleware
- payment platforms
- data mapping
- production support
- test coverage
- data structures
- process flows
- business requirements
- error handling
- data requirements
- non-functional requirements
- enterprise systems
- asia pacific
- rtgs
- event-driven
- end-to-end testing
- architecture reviews
- payment flows
- transaction banking
- distributed teams
- constraints
- message flows
- clearing
- assumptions
- idempotency
- integration specialist
- risks
- system requirements
- impact assessment
- enrichment
- regulated environment
- technology teams
- payments domain
- technical leads
- non-technical stakeholders
- impacts
- schemas
- dependencies
- retries
- operational resilience
- integration services
- design decisions
- stakeholder-management skills
- business teams
- quality check
- technical stakeholders
- interface specification
- trade-offs
- operational requirements
- runbooks
- ach
- requirements translation
- sequence diagrams
- integration standards
- implementation review
- system interactions
- executive-level presentation
- test specifications
- exceptions
- reusable templates
- rollback
- component diagrams
- design governance
- operational testing
- integration requirements
- defect triage
- class diagrams
- root-cause identification
- interface layouts
- event triggers
- vendor teams
- reusable patterns
- design authorities
- asynchronous integration
- vendor proposals
- interface contracts
- resilient integrations
- financial services regulation
- multi-team initiatives
- scalable integrations
- failure scenarios
- payment journeys
- capability leadership
- negative testing
- integration security
- synchronous integration
- reconciliation rules
- design choices
- working practices
- defect governance
- apac payment services
- techno-functional analysis
- operational states
- exception scenarios
- fit-gap assessment
- core payment platform
- payment orchestration layer
- oracle banking payments
- integration specification documents
- service-level requirements
- messaging integration
- file-based integration
- source-to-target field mappings
- code translation
- defaulting
- mandatory information
- optional information
- conditional information
- repeating information
- naming consistency
- definition consistency
- message structure consistency
- relationship consistency
- error semantics
- data-flow diagrams
- logical diagrams
- physical integration diagrams
- design oversight
- build and testing
- engineering queries
- corrective-action design
- integrated implementation
- cutover sequencing
- payment platform decision forums
- vendor deliverables
- requirements ownership
- mapping ownership
- design decision ownership
- system analysis capability
- payments integration capability
- transaction banking domain
- clearing and settlement
- payment system integration
- payment hubs
- processing platforms
- obpm
- obpay
- payment message standards
- domestic clearing
- high-availability processing
- source-to-target field mapping
- message modelling
- transaction-flow analysis
- secure integrations
- observable integrations
- operationally supportable integrations
- full-sdlc
- multi-system initiatives
- multi-vendor initiatives
- accuracy focus
- consistency focus
- traceability focus
- design integrity focus
Interested in this position?
Create your free account and tailor your CV to match this job.