Full-Stack Engineer

Full-stack practice (student level)

I pair React front ends with small Node and FastAPI backends to practice full-stack workflows. I have not completed paid full-stack engineering work; projects are documented publicly for transparency.

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 don’t have yet

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.

Front-end demos (public)

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)

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.

Interactive Pokédex

Next.js static export with client-side filtering for the original 151 Pokémon.
Focuses on front-end data fetching and search UX rather than backend services.
Repository includes prompt logs and TODOs for pagination, offline mode, and testing.

Proof links: Case study, GitHub

Car-Match

React frontend + Express backend with MongoDB persistence.
Focuses on auth, matching, forums, and messaging flows.
Deployments and known limitations are documented in the README.

Proof links: Case study, GitHub

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.

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 provides mentorship and pair-programming support in these areas, I am open to discussing opportunities.

Full-Stack Engineer

Full-stack practice (student level)

Clear scope, upfront

What I have

What I don’t have yet

What I’m doing next

What I actually ship

Front-end demos (public)

Back-end pairings (small-scale)

Evidence of progress

Interactive Pokédex

Car-Match

What’s in rotation (and how confident I am)

What I still need