Professional delivery
Digital Banking Engineering
Backend Java contribution to enterprise digital banking platforms at IdeaHub, including delivery for HNB and DFCC: Spring Boot services, REST flows, Oracle SQL checks, and production investigations backed by logs and API evidence.
investigation-workspace · digital-banking
- 1ControllersREST endpoints
- 2ServicesBusiness rules
- 3RepositoriesSQL / JPA
- 4MiddlewareCore banking calls
Layered Spring Boot · no proprietary bank UI
POST /api/v1/transfers
{ "ref": "CORR-****",
"amount": "***",
"channel": "MOBILE" }HTTP/1.1 200 OK
{ "status": "ACCEPTED",
"latencyMs": 214,
"traceId": "t-****" }14:02:11 INFO handler.start path=/api/v1/transfers
14:02:11 DEBUG middleware.await timeoutMs=3000
14:02:12 WARN slow.core.response durationMs=1842
14:02:12 INFO handler.complete status=200
SELECT status, updated_at FROM txn_**** -- redacted WHERE corr_ref = :corr; -- 1 row · status matches API
- T+0Reproduce in SIT/UAT
- T+1Collect Java + middleware logs
- T+2Compare request/response
- T+3Confirm state with Oracle SQL
- T+4Root-cause note for BA/QA
SIT
stable
UAT
stable
Postman
collections
Swagger
OpenAPI
Role
Software Engineer
Clients
HNB · DFCC (team delivery)
Focus
Java · Spring Boot · REST
Evidence
Logs · SQL · payloads
NDA-safe engineering workstation: layered APIs, request/response comparison, logs, Oracle SQL checks, and investigation timeline - not a bank customer UI.
HNB and DFCC are named only as clients of enterprise platforms I contributed to as part of the IdeaHub engineering team. This is not a claim that I built or own those bank products. Private repositories, confidential payloads, and proprietary system internals are not published.
Overview
Problem
Enterprise digital banking platforms need reliable APIs and fast, evidence-based support when something fails across services, middleware, and core banking responses.
Solution
Contribute to Spring Boot REST services as part of the engineering team, then investigate defects with reproducible evidence: Java logs, middleware logs, Oracle SQL, payloads, correlation references, and timing. Write findings clearly for BA, QA, and bank-side stakeholders.
Architecture
Layered Spring Boot services expose REST endpoints, persist and query through SQL-backed access, and integrate through middleware toward core banking. Client banks (HNB, DFCC) are named only at delivery level. Investigation workflows stay outside proprietary internals and never publish confidential bank data.
Tech stack
Responsibilities
- Develop and maintain Java/Spring Boot services and REST APIs for enterprise digital banking workflows.
- Worked on enterprise digital banking solutions for HNB and DFCC as part of the backend engineering team.
- Support banking flows such as payments, fund transfers, accounts, transactions, exchange rates, status handling, and error investigations.
- Investigate SIT/UAT and production-related issues using logs, Oracle SQL, payloads, and API timing.
- Review middleware behaviour on Linux for timeouts, waiting time, and slow core calls.
- Work with BA, QA, mobile/web, and bank-side teams to reproduce defects and verify fixes.
Challenges
- Faults rarely sit in one layer; they span APIs, middleware, and core responses.
- Stakeholders need written root cause, not only chat updates.
- Release windows leave little room for speculative debugging.
Results
- Ongoing contribution to enterprise digital banking delivery at IdeaHub, including projects for HNB and DFCC.
- Clearer defect notes grounded in logs, SQL, and request evidence.
- Practical experience with enterprise banking delivery constraints as part of a team.
Lessons learned
- Start from reproducible evidence before changing code.
- Timeouts and slow core calls deserve the same attention as application bugs.
- Name bank clients carefully: contributed as part of the team; do not claim product ownership or publish internals.
Timeline
- Apr 2025Software Engineer Trainee at IdeaHub
- Oct 2025 – Sep 2026Associate Software Engineer / Backend Java Developer
- Sep 2026 – PresentSoftware Engineer / Backend Java Developer
Downloads
No public binaries or bank deployment packages - confidential client delivery. Use Experience and Resume instead.