Observe the current process
I look for who creates the data, who re-enters it, who checks status, which edge cases slow people down, and where mistakes usually appear.
About
I turn observed workflows into full-stack products people can trust.
I build React/TypeScript products where user workflows, API rules, and database state have to stay in sync. Recent work includes an internal operations platform at Comgen America used by 60+ office and factory-floor users, with PDA scanner flows, NestJS APIs, PostgreSQL records, and admin visibility tools. My work is strongest when the software has to prevent bad status, bad handoff data, or invalid actions before they spread across teams.
Background
Process discovery, architecture, implementation, and production support.
At Comgen America, I worked on an internal operations platform used by about 60+ people across office and factory-floor roles. The old process depended on paper notes, messenger updates, Excel files, email handoffs, and people asking around for the latest status.
My role was not limited to assigned tickets. I led process discovery, helped shape architecture decisions, and served as the primary implementation contributor for shipping and quality workstreams. I also coordinated one junior engineer who implemented a related receiving module.
That work turned into React screens, PDA scan flows, NestJS APIs, PostgreSQL current/history records, and admin dashboards. The practical goal was simple and transferable: capture the action once, validate it close to the user, and make the result visible from a shared system instead of another spreadsheet or message thread.
How I work
I stay close to the work before and after launch.
The pattern is practical: watch how the job is done, model the rules, build the product surface, then use production feedback to close the gaps.
Turn rules into boundaries
Statuses, permissions, validation, recovery paths, and history requirements become React UI states, API checks, and database records.
Build the narrow path
For daily operations, the best screen often removes choices: scan this, check this status, save this record, then show the next step.
Stay close after launch
Training, production debugging, and user feedback show where the software still disagrees with how the work happens in practice.
Transferable strengths
Relevant beyond one domain.
The same engineering problems show up in internal tools, logistics software, SaaS admin surfaces, marketplaces, healthcare/fintech operations, and products where users act on shared records.
Map the work before building
I start with the actual sequence people use today: forms, scans, spreadsheets, approvals, shortcuts, recovery cases, and status questions.
Keep UI, API, and records aligned
The interface guides the user, but API validation and durable records still own important state changes, permissions, and history.
Ship for stateful products
The pattern carries to internal tools, logistics software, SaaS admin surfaces, healthcare/fintech ops, marketplaces, and any product built around shared records.
Experience snapshot
- Built full-stack product surfaces across React, TypeScript, NestJS, PostgreSQL, scanner/PWA workflows, and admin dashboards
- Worked from process discovery through architecture, implementation, launch support, and production debugging for systems used by 60+ users
- Served as the primary implementation contributor for shipping and quality workstreams inside a broader internal operations platform
- Coordinated one junior engineer on a related receiving module while keeping shared workflow and data-model decisions aligned
Technical focus
Workflow-heavy product surfaces
Turning real user steps into screens that reduce re-entry, status chasing, and ambiguous handoffs instead of simply digitizing a form.
API and data contracts
Modeling statuses, blocked transitions, permissions, and current/history records so the backend protects the workflow even when the UI is fast.
Operational visibility
Building dashboards, tables, filters, modals, and scanner/PWA interactions that help non-technical users act from the same source of truth.
Need an engineer who can turn operations into React software users trust?
I work across frontend UX, API validation, PostgreSQL records, and production support for teams that need accurate status and clear next steps.