The problem
In banking operations, a form often becomes a process: capture information, collect documents, route it to the right person, request corrections and record the decision. As the business changes, those journeys change too.
Building a new frontend for every variation creates repeated work. Keeping the process, the data and the review experience aligned is the more useful engineering problem.
My contribution
I was the lead fullstack engineer on Orbit/workflow work. I built the workflow portal, created the Vant Flow package used in it, and built the IAM and messaging portals.
The surrounding work spans Spring services and Angular applications. The workflow foundations include versioned process definitions, human tasks, service tasks, decision steps, document attachments and an audit history around cases.
From a form to a business process
The frontend uses a shared form model instead of treating every business document as an unrelated screen. Vant Flow provides builder and renderer capabilities, while the host application keeps control of its APIs, identity, storage and workflow rules.
On the backend, case data and process state need to remain understandable together. Configurable definitions, persisted tasks and background jobs support processes that extend beyond a single request.
The tradeoff
Configuration moves repeated changes out of individual screens, but it introduces a platform to maintain. Definitions need versioning, permissions remain an application concern, and flexible rules need validation and guardrails.
That is the engineering balance I worked on: reuse the common process mechanics while preserving the business-specific behaviour.
What it demonstrates
This work connects backend design, Angular delivery, reusable tooling and technical leadership. It shows how I approach a business process as a system, with capture, review and operation considered together.