Selected work

Case studies, not project cards.

Each case separates system context, my responsibility, the engineering approach, and the evidence I can defend.

Core banking modernization

Temenos T24 R25 delivery platform

Context

Sacombank upgraded its core banking platform to Temenos T24 R25. The delivery challenge combined a multi-component system, strict environment promotion, OpenShift deployment, and production cutover.

My responsibility

CI/CD automation, Helm architecture, artifact and image promotion, environment-specific delivery, release standardization, and production go-live support.

Engineering

Umbrella Helm architecture for T24 R25 Transact / Transact Servlite.

18 component/workload charts with reusable templates for deployments, services, configuration, volumes, probes, and resources.

Delivery across Develop, SIT, UAT, Staging, DR, and Production.

Image/tag promotion, configuration separation, resource controls, and OpenTelemetry annotations.

18 workloads6 environments2 weeks → 3 days upgrade window Sacombank official announcement ↗

CI/CD platform engineering

Enterprise delivery platform for ~400 repositories

Context

A large banking application estate spans OpenShift microservices, WebSphere, JBoss, .NET/IIS, mobile, integration, and specialized application platforms.

My responsibility

Shared Jenkins/Groovy delivery design, onboarding, build/test/security orchestration, artifact management, approvals, and environment promotion.

Engineering

Reusable shared pipelines and stages driven by project configuration instead of repository-specific duplication.

Build paths for Maven, Gradle, Ant, Node.js, .NET, Python, Flutter, Android/iOS, and specialized workloads.

Security integration with Coverity, SonarQube, Black Duck, Aqua, OWASP ZAP, Zimperium, plus automated testing with Katalon.

Artifact and image management through Nexus with controlled promotion between environments.

~400 repositoriesMulti-stack deliverySecurity gatesDEV → PROD governance

Open source engineering

Jenkins Ansible Tower Plugin

Context

The plugin connects Jenkins jobs and pipelines to Ansible Tower, AWX, and Ansible Automation Platform. Reliability and compatibility matter because it sits directly in deployment workflows.

My responsibility

Plugin maintenance and modernization in the Jenkins project.

Engineering

Improved workflow polling resilience and transient-failure handling for AAP/AWX.

Improved build-console diagnostics while keeping logs secret-safe.

Fixed Job DSL data-binding compatibility around importTowerLogs.

Modernized Jenkins/JDK baselines, regression coverage, UTF-8 request handling, and security scanning.

Jenkins projectPublic code & reviewsCompatibility engineering View repository ↗

Release & availability engineering

High-availability rollout across mixed platforms

Context

Banking workloads run on both container platforms and traditional clustered middleware. A single rollout model is not sufficient.

My responsibility

Design deployment strategies around the failure modes and traffic topology of each platform.

Engineering

Rolling, canary, and blue-green strategies for OpenShift/Kubernetes workloads.

Node-by-node and server-group rollout for WebSphere/JBoss with traffic drain, deployment, validation, and restoration.

JBoss AML topology redesign using independent server groups and load-balancer coordination to reduce deployment disruption.

Health validation, rollback paths, observability, and release gates integrated into deployment flow.

OpenShiftWebSphereJBossControlled traffic transition