Frontend
What the user touches
- React
- JavaScript (ES6+)
- HTML5
- CSS3
- Tailwind CSS
- shadcn/ui
- EJS
- Responsive layout
Everything here is something I've used on a real project — the platform I run, the clinic app I built during my internship, or my capstone.
What the user touches
APIs and application logic
Schema design and queries
2+ years on a live platform
Local stacks and live servers
How I work with a team
PandaAuth is my own platform, so QA has never been someone else's job. Two years of release passes taught me to treat the API as the contract: check the happy path, then break it on purpose.
Collections per endpoint covering valid requests, expired licenses, missing fields, and wrong roles. Run before every deploy.
Quick one-off probes from the server itself — malformed payloads, bad headers, unauthenticated calls, and status-code checks.
Capture live traffic, inspect real request and response pairs, then replay and tamper with them to confirm validation actually holds.
Two years of this on PandaAuth — a platform where a bad release means a real user can't log in.
QA Analyst · 2+ yearsMy testing so far has been hands-on and manual. The next step is making it automatic, so the suite runs without me.
Tell me what your stack looks like — I pick things up quickly and I'll say so honestly if I haven't used it yet.