Vetted QA Engineers in California

“Meta engineer who owned a heavily used internal goals/performance management feature end-to-end, driving major responsiveness improvements by restructuring frontend data loading and adding backend caching (Memcached), cache warmups, and query/index tuning. Strong focus on production quality: observability, error monitoring, and improving test coverage to prevent regressions during peak review cycles.”

“Game QA Lead/embedded QA with live production experience supporting a public alpha, owning narrative/early-game content quality and quest progression stability. Known for driving rapid resolution of high-impact blockers via consistent repros, cross-discipline coordination, and data-backed reporting (including bot-based success/failure measurement), while maintaining sprint-aligned test plans and documentation in JIRA/Confluence and leading developer playtests for gameplay feel/polish.”

“QA/engineering background spanning Riot Games (VALORANT leaderboard systems) and early-stage startups. Has hands-on experience improving performance and reliability via caching, rate limiting, deduplication/idempotency, and shipping/validating high-stakes production hotfixes; also builds Next.js/TypeScript projects and automation/internal tools (Python).”

“Game/interactive software QA professional with experience spanning AAA titles (Activision Black Ops 3; Halo 4/Forge) and VR at Meta (The World Beyond). Notable for modernizing QA operations at Lego BrickLink Studio by implementing Testmo and dramatically increasing test coverage and user satisfaction, plus quickly diagnosing and unblocking a critical public-launch issue caused by misconfigured gatekeeper flags.”

“QA automation engineer with healthcare web experience who owned an end-to-end automated test suite (Java/Cucumber/Selenium and Cypress) and integrated it into CI/CD (Jenkins to GitHub Actions, qTest DoD gates). Known for boosting regression coverage to ~93%, stabilizing flaky Cypress tests, and catching production-impacting pipeline/environment redirect issues through workflow updates and cross-browser/regional scenario testing.”