01
Core Banking
Temenos Transact customization, Java Extensibility L3, InfoBasic, lifecycle routines, screens, and OFS.

Core banking / Fintech / Enterprise systems
Software Engineer specializing in Core Banking, Financial Technology, API Integration, and Enterprise Systems
I work on Temenos Transact customizations, Java extensibility, IRIS API integration, and engineering tools for complex financial platforms.

01
Temenos Transact customization, Java Extensibility L3, InfoBasic, lifecycle routines, screens, and OFS.
02
IRIS Dynamic APIs, Apache Camel routing, Java, REST APIs, Spring Boot, and ActiveMQ.
03
Docker, Kubernetes, AWS, ELK, packaging, deployments, upgrades, and environment support.
04
Karate API testing and monitoring plus Python, Bash, Shell, and Batch scripting.
01 / Selected work
Anonymized examples of core-banking customization, integration, delivery, and engineering support work. Details are intentionally abstracted to protect clients and systems.
Case study / 01
anonymizedAn anonymized integration case study covering API routing between an external channel and a core-banking platform.
Outcome: Created a reusable, maintainable integration approach while keeping external and internal system details abstract.
Read case studyCase study / 02
anonymizedAn anonymized case study of translating business workflow needs into Transact screens and backend behavior.
Outcome: Delivered custom screen and workflow changes aligned with business requirements.
Read case studyCase study / 03
anonymizedAn anonymized case study of reusable utilities supporting repeated Transact customization needs.
Outcome: Established reusable building blocks for repeated customization and integration needs.
Read case studyCase study / 04
anonymizedAn anonymized case study of controlled packaging, deployment, upgrade, and environment support work.
Outcome: Supported controlled change delivery and environment maintenance for Transact implementations.
Read case studyCase study / 05
anonymizedAn anonymized case study of automation, API validation, monitoring, and troubleshooting practices.
Outcome: Improved repeatability around technical tasks, API validation, and operational investigation.
Read case study02 / Technical scope
A focused view of the engineering areas behind the selected work—from core-banking customization to safe technical delivery.
Pillar / 01
Customizing Temenos Transact workflows, screens, routines, and integrations for complex core-banking requirements.
Text equivalent: A business workflow is expressed through a Transact screen or enquiry, then handled by Java and InfoBasic customization before a controlled core-banking process. This is conceptual and not a production diagram.
Pillar / 02
Building and supporting API flows that connect external channels, integration layers, and core-banking services.
Text equivalent: A digital channel sends a request to an API or IRIS layer. Apache Camel routes it through generalized provider processing to a core-banking service. This is conceptual and does not represent a client production topology.
Pillar / 03
Supporting containerized deployment, cloud environments, monitoring, and safe operational change around enterprise applications.
Text equivalent: An application is prepared as a container image, deployed into a Kubernetes environment with generalized AWS-hosted services, and made observable through logs and operational visibility. This is illustrative only.
Pillar / 04
Using automation, testing, monitoring, and practical troubleshooting to improve repeatability in technical delivery.
Text equivalent: A change or API workflow is validated automatically, producing results and diagnostics that support monitoring or follow-up. The flow is illustrative and contains no live operational data.
03 / Experience
A resume-backed progression across application development, Temenos Transact customization, integration, and enterprise delivery.
May 2025 – Present
Confidential enterprise financial systems role
March 2020 – May 2025
24Labs · UK
February 2019 – March 2020
PDS Ltd. · Pakistan
04 / Approach
01
Complex financial systems require careful implementation, troubleshooting, and change delivery.
02
Integrations and customization should be understandable to the teams that maintain them.
03
Shared Java and InfoBasic utilities can make repeated work more consistent.
04
Packaging, testing, deployments, and monitoring are part of engineering work, not afterthoughts.
05
An ongoing interest in computer science and emerging technologies informs practical engineering work.
05 / Contact
For opportunities involving core banking, integration engineering, Java, APIs, or enterprise delivery, get in touch.
Karachi, Pakistan