OurPass.

I automated account verification and kept related records consistent.

2,000+Document reviews / month

Monthly verification workload supported by the backend services.

−35%Review cycle time

Reduction after automating verification and administrator-led account updates.

01 / Verification & account operations

Account reviews took less time.

Manual verification steps slowed account updates, and a failed operation could leave related records inconsistent. I automated verification and administrator-led updates, adding input validation and SQL transactions so related changes succeeded or rolled back together.

2,000+Document reviews / month
−35%Review cycle time
99.9%Data consistency
ACCOUNT REVIEW01
Example accountDocuments submitted
Identity documentValid
Account detailsValid
Required fieldsComplete
✓VALIDATEDReady for the account update
ONE SQL TRANSACTION02
Saved
together.
01
Verification recordReview completed
✓
02
Account recordStatus updated
✓
COMMIT BOTHRelated records agree.
IF A WRITE FAILSRollback both changes.The original records stay intact.
Illustrative reconstruction of the workflow. Example content, no customer data.
How I built itRead the engineering details

Rejecting an invalid request early prevented bad input from reaching storage. A transaction addressed a different failure: one valid operation saving only some of its changes. I used both so faster account operations would not leave inconsistent records.

Node.js & AWS
Maintain backend services supporting verification and account operations.
PostgreSQL transactions
Commit related writes together or roll them back when an operation fails.
Input validation
Reject invalid requests before they change stored account data.

2,000+ Document reviews / month. Monthly verification workload supported by the backend services.

−35% Review cycle time. Reduction after automating verification and administrator-led account updates.

99.9% Data consistency. Across KYC workflows using transactional SQL and input validation.

02 / Business inventory

Businesses could find and update product records.

Businesses needed to create, find, and update inventory without confusing stock availability with publication status. I built NestJS and PostgreSQL APIs with searchable records, validation, partial updates, ownership checks, and separate stock and publication fields.

CATALOGUE FILTERS
Category: PantryPublishedIn stock
Combine the fields that matter.
PRODUCT DETAILSSKU · 014
Product
details.
Oat blendPantry essentials
STOCK QUANTITY24 units
PUBLICATIONPublishedVisible in the catalogue
AVAILABILITYIn stockReady to sell
SEPARATE FIELDSPublished ≠ in stock.

A visible product can be sold out.
A stocked product can still be a draft.

Illustrative reconstruction of the workflow. Example content, no customer data.
How I built itRead the engineering details

I kept publication and availability as separate fields rather than compressing them into one status. Create and update requests shared validation rules, while partial updates let a user change a field without resubmitting the entire record.

NestJS & TypeScript
Express product operations with clear request types and API boundaries.
ValidationPipe & DTO validation
Reject invalid field values and keep create/update rules aligned.
TypeORM & PostgreSQL
Store product records and combine the filters people supply.
FROM SOMEONE I WORKED WITH

“Bliss doesn't just complete tasks; he takes deep ownership of them, ensuring that the final output is always executed to the highest standard.”

Victoria IgbobiSolutions Architect · Teammate at OurPass
MY CONTRIBUTION AT OURPASS

My work here connected the needs of compliance and operations with backend changes they could use: faster verification steps, consistent account updates, and structured inventory records.

Back to selected workDiscuss an opportunity
Illustrations use explanatory examples, not company screens or private data. Reported impact figures come from my résumé.