Work

Software Engineer

Problem

A startup needed production product software — features that go from requirement to a running system, not throwaway prototypes.

What I build

• Own feature work across the UI, API, and data path.
• Ship, debug, and improve after release.
• Use AI integrations when the product needs them, not as the whole story.

Systems

TypeScript, React, Next.js, Node.js, PostgreSQL, REST APIs. Public product names stay conservative until confirmed.

Production operational systems

Problem

Client operations needed software that matched real floor and office workflows: inventory, production, dispatch, and devices that keep working when the network drops.

What I built

• A production-oriented ERP around multi-stage business workflows and relational data.
• Offline-first behavior, synchronization, QR workflows, and hardware integrations.
• Took requirements through architecture, implementation, and handoff.

What mattered

The hard part was the data flow between stations, APIs, and the database — not a single screen. Client identities stay confidential.

Software Engineering Intern

Problem

Healthcare tools needed form-heavy web workflows that fit an existing product.

What I built

• Meal-planning and quiz features in Next.js and TypeScript.
• Worked inside an existing codebase instead of starting from zero.

Self-directed products

Problem

The fastest way I learn a system is to own it end to end.

What I built

• Simple Form — form builder, validation, submissions, analytics.
• Recipe Reveal — Next.js full-stack app with SSR / SSG, then deployed.
• Other small products used to practice APIs, databases, and production deploys.