Professional experience

Banking system change from requirements through release verification.

Banking system delivery at Hitachi eBworx since 2019 across loan origination, business credit, retail banking, and FX-system change. Responsibilities distinguish my contribution from team delivery and exclude confidential client details.

View resume summary

Apr 2023 - Present

Hitachi eBworx

Business Analyst

Support banking system enhancements from requirement clarification through testing, defect triage, production verification, and post-release follow-up.

Contribution focus

Translate business change into observable system behavior and delivery evidence, while keeping decision ownership with the accountable business and control stakeholders.

Loan OriginationBusiness CreditRetail BankingFX Dealing

Analyze and translate requirements across business, operations, and technology stakeholders for loan origination and business credit enhancements.
Maintain requirement-to-test traceability and support integration testing, SIT, UAT, regression, and production verification across interconnected modules.
Prepare reusable test assets, review UI and system behavior, and validate functional, interface, and backend outcomes with delivery teams.
Facilitate defect triage and root-cause investigation using reproducible evidence, logs, business impact, and controlled retest scope.
Support document-generation automation, field mapping, template validation, and output verification for operational documentation.
Coordinate release readiness, post-release monitoring, issue follow-up, and stakeholder decisions without exposing internal bank information.

Sep 2019 - Apr 2023

Hitachi eBworx

Associate Business Analyst

Built a foundation in banking requirement documentation, test execution, defect control, audit evidence, and post-go-live support.

Contribution focus

Turn requirements into structured test coverage and evidence that lets business, QA, and technology teams make clearer delivery and closure decisions.

Requirement DocumentationUATDefect ManagementProduction Support

Translated business requirements into functional specifications and testable behavior for SIT, UAT, and regression delivery.
Prepared and maintained structured test cases, evidence templates, execution status, and end-to-end audit records.
Coordinated defect ownership, business-impact clarification, retest evidence, closure decisions, and release-day verification.
Used JIRA, Confluence, and HP ALM to manage requirements, test execution, defects, traceability, and delivery communication.
Supported users after go-live by clarifying reported behavior, reproducing issues, and coordinating resolution within agreed service expectations.

Working evidence

Methods and tools used to make delivery decisions clearer.

These are working practices, not claims of sole programme ownership. Public metrics are intentionally omitted unless they can be supported with a defensible source and calculation.

Business Analyst

Methods

Requirement clarification, functional behavior, business rules, and acceptance criteria
Impact and regression scoping across UI, workflow, data, document, interface, and backend behavior
UAT planning, defect triage, evidence-based retest, release readiness, and post-release follow-up

Tools and system evidence

JIRA, Confluence, and HP ALM for traceability and delivery communication
SQL, logs, data validation, and UI/service/backend reasoning for investigation
Document-generation tooling for field mapping, template validation, and output checks

Associate Business Analyst

Methods

Functional specification, test-case design, execution tracking, and audit-evidence management
Positive, negative, regression, retest, and release-day verification
Business-impact clarification, defect lifecycle control, and production-issue reproduction

Tools and system evidence

JIRA, Confluence, and HP ALM for requirements, testing, defects, and traceability
Structured evidence templates, status reporting, and controlled release communication

See evidence-based case studies