Product concept kept private. Engineering work shown.
I’m intentionally not publishing the real product flow or unblurred UI in an open portfolio. What I can show publicly is the scale and type of engineering work behind it.
Shotzy
This is my most technically ambitious product work. I took a firsthand problem from discovery through architecture, implementation, testing, security hardening, and release-readiness decisions.
What I’ve owned
- Product requirements, user journeys, and workflow architecture
- Next.js application flows and API integrations
- Supabase/PostgreSQL data model, authentication, and row-level security
- Stripe payment lifecycle, retries, refunds, and failure handling
- Automated testing, security remediation, and explicit release gates
What it demonstrates
I can work across product thinking and implementation details without losing sight of reliability. I’m comfortable with permissions, state, stale events, payments, privacy, and knowing when the evidence says a release should wait.
Stack Next.js · React · Supabase · PostgreSQL · Vercel · Stripe · Twilio · REST APIs