System Analyst (ISO, Swift Payments)

Responsibilities

• Broad experience in designing, programming, and implementing large distributed systems with microservices.
• Deep understanding of Application, Infrastructure and security architecture and non-functional aspects like Performance, Scalability, Reliability, Availability etc.
• Translate functional requirements to design.
• Work with technical SMEs to understand their requirements and ensure these are met.
• Define best practices and standards for the microservice implementation.
• Identify and define implementation patterns.
• Lead activities to build accelerators and tools to increase the quality of deliverables.
• Evaluates industry technologies to shape design of services in consideration of cost, portability, compatibility, or usability factors.
• Identifies and makes appropriate changes to technologies, integrated platforms, and systems to meet customer and operational requirements.
• Continuously seeks to more efficiently manage and utilize technology, platforms, and systems.
• Highlights design risks, provide alternative options, and recommend quality solution to specified problem.

Essential Requirements (Skills Requirements)

• Bachelor's degree and 10-15 years of technical experience within architecture development, integration of backend systems and development. Strong Hands–on experience in developing applications using Java/J2EE, with Spring boot framework knowledge and experience.
• Must Have :
• ISO 20022 (MX messages preferred)
• End-to-end payment processing knowledge
• Hands-on experience with SWIFT and domestic/global payment rails
• Java (ability to understand and discuss logic)
• SQL (reconciliation queries, defect analysis, data validation)
• Solution / Application Design ownership
• Integration patterns: APIs, MQ/event-driven flows, file-based processing
• Database design awareness (schemas, indexing, performance considerations)
• XML (ISO message structures), JSON (API payloads), YAML (config / CI-CD)
• Interface & integration specification design
• Non-functional requirements (scalability, resiliency, performance, observability)