Back to work

wedbush securities and truist bank · via infosys

Banking products from the ground up

Three years, four products, one job: take what regulation and operations demand, and turn it into software that advisors and clients actually use. Requirements, workflows, rule configuration, and testing across the full lifecycle.

the problem

Everything ran on PDFs, email, and patience.

Onboarding a new account meant PDF forms, email approvals, and roughly forty-seven manual steps across more than a week of back and forth, with about a third of submissions bouncing for missing or inconsistent data. Moving money required coordination across systems that did not talk to each other. Operational requests from advisors lived in inboxes where nobody could see status. And every one of those processes had to satisfy KYC, AML, and audit requirements at each step.

what i built

Four products, one connected platform.

wedbush securities

Money Movement

ACH and wire transfers on BNY Mellon rails. I led the banking API integrations into the money movement platform and authored the system integration specs, data flow diagrams, and API contract documentation that engineering built from.

wedbush securities · truist bank

Account Onboarding

A dual-view digital platform: advisors initiate and track, clients complete forms and sign electronically, with real-time field validation replacing rework loops. Digitizing the approval workflows cut onboarding turnaround by nearly half and submission errors by more than half.

wedbush securities

Service Request Portal

Advisors used to chase operational requests like policy changes, death claims, surrenders, and commission questions through email, with no visibility into status. The portal replaced that with a structured catalog of request types, each routed to the right operations queue with its own target date. I owned requirements and testing. Advisors submit in a few clicks and see exactly where every request stands; ops teams work prioritized queues instead of inboxes.

banks · kyc/aml

Vendor API Integrations

The compliance layer underneath everything: automated KYC and AML rule engines configured by translating regulatory requirements into system logic, plus the vendor integrations that feed them. Manual intervention in compliance review dropped by roughly seventy percent, and every audit passed on first submission.

exhibits

The system, drawn the way I spec it.

Advisor portalinitiate · trackClient portalforms · e-signValidationreal-time checksKYC/AML engineautomated rulesstatus updates back to the advisor

exhibit a · dual-view onboarding flow, advisor and client paths meeting one validation and compliance spine

Money movementwedbush platformAPI gatewayauth · limitsBNY Mellonach · wire railstransfer requestsubmitacknowledgements, statuses, and exceptions flow back the same pathintegration specs, data flow diagrams, and api contracts authored per rail

exhibit b · money movement rails, platform requests to bny mellon with acknowledgements flowing back

outcomes

What changed.

Onboarding that took around two weeks now clears in days, with submission errors down by more than half.

Every KYC and AML audit passed, first submission, across three years of releases.

Compliance review runs mostly without human touch; manual intervention fell by roughly seventy percent.

Advisors stopped chasing requests through email. Every service request has an owner, a queue, and a target date.