At OurPass, I worked with compliance and operations on identity verification and account updates. I maintained Node.js, AWS, and PostgreSQL services, automated review steps, and used validation and SQL transactions to keep related updates consistent. My inventory work used NestJS and PostgreSQL.
OurPass verification work supported the teams reviewing customer documents and updating accounts. I also contributed to a separate set of inventory services for business product records.
01 / Verification & account operations
I reduced the manual work in account verification.
Compliance and operations teams needed to review customer information and update accounts. Manual steps slowed that work, and related records needed to agree after an update.
MY CONTRIBUTION
I maintained the verification services and built APIs for user verification and administrator-led account changes. Working with the teams using them, I automated review steps and added input validation and transactional SQL.
THE IDEA, ILLUSTRATED
Keep related changes together
TRANSACTIONAL SQL · A COMPLETE CHANGE OR NO CHANGE
PostgreSQL transactionReady to update
ACCOUNT RECORD 01
Verification record
Original state
ACCOUNT RECORD 02
Account update
Original state
BEGINApply changesPending
Try the completed and interrupted paths to see why related data changes belong in one transaction.
Related account updates succeed together or roll back together. A failure cannot leave the account with only half the changes saved.
THE DECISION
Related changes had to succeed together.
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.
WHAT CHANGED
Review cycles became shorter and account data more consistent. The backend supported the operations team’s verification workload with fewer manual steps.
Document reviews / month
2,000+Monthly verification workload supported by the backend services.
Review cycle time
−35%Reduction after automating verification and administrator-led account updates.
Data consistency
99.9%Across KYC workflows using transactional SQL and input validation.
I built APIs for the details a business manages every day.
Inventory work needed more than a product name. Price, quantity, category, availability, and publication status described different things, and users needed to create, find, and update those records.
MY CONTRIBUTION
I contributed NestJS APIs for creating and managing inventory, using PostgreSQL and TypeORM for storage. I added request validation and filters to narrow the catalogue by the fields a business was working with.
THE IDEA, ILLUSTRATED
Give a product a useful record
BUSINESS INVENTORY · A STRUCTURED PRODUCT RECORD
Inventory · Product details
01
PRODUCT RECORD
Desk lamp
Draft
Sale price45.00
Cost28.00
One record also holds its name, category, item type, and publication status.
NestJS endpointTypeORMPostgreSQL
Product details become structured fields a business can retrieve and update.
A product can be published but out of stock, or available but not yet published. Each status answers a different question.
THE DECISION
An unpublished product is not an out-of-stock product.
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.
WHAT CHANGED
The inventory services supported structured product entry, filtered retrieval, and updates. Businesses could manage those details through defined API operations.
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.
“Bliss doesn't just complete tasks; he takes deep ownership of them, ensuring that the final output is always executed to the highest standard.”