Target role
General full-stack software engineer: React product surfaces, API contracts, data modeling, and production support
Full-stack software engineering
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. I am strongest when the product has to make a messy real-world process reliable: UI states, API validation, and database records all agreeing on what happened.
At a glance
Target role
General full-stack software engineer: React product surfaces, API contracts, data modeling, and production support
Production context
60+ daily users across office and factory-floor roles inside a broader internal operations platform
Production stack
React/TypeScript, PWA scanner flows, NestJS APIs, PostgreSQL current/history records, AWS, and Nginx
Ownership
Process discovery, co-architecture, primary implementation for shipping and quality, plus junior-engineer coordination on receiving
Selected work
Shipping, quality, and visibility share an internal operations foundation, but each case study emphasizes a different full-stack problem: handheld validation, role-aware state transitions, and dashboard/query design.
Built React dashboard and admin surfaces that gave office users live visibility into production, shipping, inventory, and quality state.
Built shipping and PDA scanner flows that replaced paper/checklist/email steps with scan, validate, save, and immediate website visibility.
Built the quality module that turned inspection, hold, release, and exception decisions into React screens, API validation, and PostgreSQL current/history records.
Technical focus
Turning real user steps into screens that reduce re-entry, status chasing, and ambiguous handoffs instead of simply digitizing a form.
Modeling statuses, blocked transitions, permissions, and current/history records so the backend protects the workflow even when the UI is fast.
Building dashboards, tables, filters, modals, and scanner/PWA interactions that help non-technical users act from the same source of truth.
Transferable strengths
The same habits apply outside manufacturing: understand the domain, make the UI hard to misuse, and keep the record trustworthy through API and database boundaries.
I start with the actual sequence people use today: forms, scans, spreadsheets, approvals, shortcuts, recovery cases, and status questions.
The interface guides the user, but API validation and durable records still own important state changes, permissions, and history.
The pattern carries to internal tools, logistics software, SaaS admin surfaces, healthcare/fintech ops, marketplaces, and any product built around shared records.
Experience snapshot
I work across frontend UX, API validation, PostgreSQL records, and production support for teams that need accurate status and clear next steps.