- React + Gatsby UI work (this site, Interactive Pokédex, Car-Match dashboard running on GitHub Pages).
- Express/FastAPI services that back those UIs locally or on small hosts like Render/Netlify Functions (Car-Match’s backend cold-starts on the free Render tier).
- CI/CD scripts that lint, run basic tests, and deploy to GitHub Pages or Netlify.
- AI companionship throughout—Copilot/ChatGPT help scaffold components and routes before I review them.
Full-Stack Engineer
Full-stack practice (student level)
I pair React front ends with small Node/FastAPI backends to learn the workflow. No paid work yet—just honest reps documented in public.What I actually ship
Evidence of progress
Interactive Pokédex
- Front-end React-lite build (vanilla JS + components) with accessibility checks.
- Focuses on client-side filtering + fetch flows rather than complex backend logic.
- Repo shows prompt logs + TODOs for pagination, offline mode, and testing.
ProjectHub proxy
- Express proxy that fronts AI endpoints for my own experiments.
- Includes minimal frontend embed + instructions for running locally.
- Callouts everywhere that this is a learning sandbox, not a SaaS tool.
What’s in rotation (and how confident I am)
React + Gatsby (comfortable)Vanilla JS + HTML/CSS (comfortable)Next.js (learning)Node.js + Express (learning)FastAPI (exploring)Netlify + GitHub Pages deploys (comfortable)Docker Compose for dev parity (learning)Playwright / Vitest (exploring)
Each repo annotates which pieces are stable vs. experimental so there are no surprises.
What I still need
- Building production-ready auth and session flows.
- Accessibility reviews led by experienced UX/FE engineers.
- Deeper testing discipline (unit, integration, and visual regression).
- Mentorship on prioritizing work across the stack with real stakeholders.
If your team can pair-program and coach through these gaps, I’m ready to learn.