Full-Stack Engineer

Full-Stack Engineer

Full-stack practice focused on putting both sides together

I pair React frontends with small backend services to practice full-stack workflows. The difference between this page and my backend page is scope: backend is about the API itself, while this page is about getting the frontend and backend working together as one experience.
  • Public UI work: this site, the Pokédex, and other live front-end projects.
  • Integrated project: Car-Match combines frontend flows with a deployed Express backend.
  • Shipping focus: deploys, CI checks, and documented limitations across the stack.
Honesty upgrade

Clear scope, upfront

What I have

  • Public front-end deployments accessible via live URLs.
  • Small backend services paired with these demos.
  • Documentation that identifies missing features and known risks.

What I am still working toward

  • Ownership of production full-stack systems or large-scale traffic environments.
  • Cross-team delivery and real stakeholder timelines.
  • Deep testing discipline across the stack.

What I’m doing next

  • Strengthen authentication and session management workflows.
  • Improve test coverage and CI reliability.
  • Practice accessibility reviews with peers.
Reality snapshot

What I actually ship

Front-end demos (public)

The frontend side is where I ship the most often, but the full-stack part matters when the UI is tied to real data and backend behavior.

  • React and Gatsby UI development for this site and the Interactive Pokédex.
  • GitHub Pages deployments for AnimalSounds and other demonstration projects.
  • CI scripts perform linting and build validation before deployment.

Back-end pairings (small-scale)

This is what makes the page different from the frontend-only work: wiring the interface to auth, persistence, and backend flows.

  • Car-Match backend is deployed on Render with MongoDB Atlas.
  • Free-tier cold starts can take several minutes; this limitation is documented in the README.
  • Copilot and ChatGPT are used to scaffold routes before manual review.
Work samples

Evidence of progress

Interactive Pokédex

Focus: frontend-heavy project that demonstrates data fetching, search, and deployment, not a backend-heavy system.

  • Next.js static export with client-side filtering for the original 151 Pokémon.
  • Repository includes prompt logs and TODOs for pagination, offline mode, and testing.

Proof links: Case study, GitHub

Car-Match

Focus: the clearest full-stack example on this site because the frontend and backend have to work together for auth, matching, forums, and messaging.

  • React frontend + Express backend with MongoDB persistence.
  • Deployments and known limitations are documented in the README.

Proof links: Case study, GitHub

Toolbox

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 repository documents which components are stable and which are experimental to indicate maturity.

Growth plan

What I still need

  • Building auth and session flows for deployed demos.
  • 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 provides mentorship and pair-programming support in these areas, I am open to discussing opportunities.