Workflow
Software engineer
I turn workflows into software that ships.
Messy operations turned into focused product flows, reliable services, and releases people can trust.
Selected process
From messy workflow to shipped system.
System
Turn that friction into product structure.
Interfaces, APIs, data models, roles, and deployment paths get designed together so the result feels like one system.Release
Ship it with enough proof to trust.
The case studies focus on concrete constraints, technical decisions, and outcomes instead of a gallery of disconnected screens.Reliable systems for real workflows.
Confidential-safe stories about the business problems, engineering trade-offs, and shipped outcomes behind real software systems.

Outcome-led build
ERP System
Scattered spreadsheets became one production ERP across job orders, quotations, inventory, and sales.
Manual tracking across spreadsheets and disconnected documents.
A role-based production system with real-time dashboards, backups, and VPS deployment.
Chose MongoDB with Mongoose ODM for flexible schemas and fast iteration on changing business requirements.
Dockerized multi-service deployment with Nginx reverse proxy, real-time WebSocket updates, and automated database backups

Outcome-led build
ParkLocator
A parking idea became a multi-surface platform with mobile discovery, admin operations, geospatial search, and reservation flow.
Parking discovery and venue operations were split across generic maps, manual status checks, and missing admin tools.
Flutter mobile, Angular admin, NestJS API, PostGIS, Redis, and PayMongo connect into one reservation platform.
Chose Flutter for its native performance, rich widget library, and strong geolocation/maps ecosystem (Very Good CLI for project structure).
Monorepo with three independent apps (Flutter + NestJS + Angular) sharing a PostGIS-backed spatial API for parking spot discovery

Outcome-led build
SVCI Online Document
Manual document requests became a role-based workflow for students, admins, departments, payments, clearance, and release.
Requests, payment proof, clearances, and release tracking moved through disconnected manual handoffs.
A Laravel/Inertia system tracks request state, verifies payments, handles clearance, protects files, and notifies users.
Used Inertia to keep Vue pages while letting Laravel own routes, authorization, validation, and workflow orchestration.
Multi-role document workflow with private file delivery, payment verification, department clearance, release tracking, and browser/PHP test coverage

Outcome-led build
Smart Pomodoro
Calendar blocks became recoverable app-local focus sessions with planning, presets, runtime state, and history.
Study plans lived in the calendar while actual timer sessions lived somewhere else.
A Next/Nest product reads focus calendar blocks, generates local intervals, and runs a resilient focus timer.
Read selected focus calendar events and generate intervals inside the app instead of writing generated sessions back to Google Calendar.
Read-only Google Calendar planning flow with app-local intervals, resilient timestamp-based timer runtime, and encrypted OAuth token storage

Outcome-led build
QA Appliance
Appliance-store sales, inventory, installment accounts, payments, reports, and maintenance became one local-first desktop system.
Inventory, serial numbers, receivables, payments, and backups were hard to keep consistent without a dedicated tool.
A Tauri/Rust/SQLite app runs locally with transactional sales, installment tracking, reports, and recovery tools.
Built a Tauri app with React UI and Rust/SQLite backend commands for all core workflows.
Local-first retail operations app with transactional sales, installment receivables, SQLite WAL mode, backup/restore, and export workflows
How I approach reliable software.
I build around the workflow first, then connect product, engineering, and operations decisions so the system can be shipped and maintained with confidence.
Start with the workflow
The best software maps to how people actually work, then removes the friction around it.
Own the full path
Interface, API, database, deployment, and operations need to fit together before a product feels reliable.
Make trade-offs explicit
Every stack choice has a cost. Good engineering means choosing the cost that fits the business constraint.
Ship systems people can trust
Authentication, backups, performance, and maintainability matter because real users depend on the result.
A bit about me
I'm a product-focused software engineer based in Dipolog City, Philippines. I specialize in building complete systems: from database design and backend APIs to polished frontends and CI/CD pipelines. I focus on shipping working software with sound engineering judgment, not just writing code.
Let's build something.
I'm open to full-time roles and select consulting engagements. If you're looking for a software engineer who knows what to do, let's talk.

