Skip to content
jayson.dev
Contact

Open to full-time roles & freelance work

Jayson Lance Casaclang

Web Developer & QA Engineer · 5+ years

I build web apps in React and TypeScript — and having come up through QA, I spend about as much time on how they fail as on how they work.

Milpitas, CA@Jayson924

Experience

Where I've been

Eight years at a growing engineering organization — starting in customer support, moving into QA, then into building the internal tools the engineering team ran on. Almost all of that code is in private repositories, which is why the side projects further down are the ones I can show you in full.

  1. Oct 2020 — May 2026

    QA Scalability Engineer · Streaming platform, later distributed compute

    Owned QA and scalability testing for feature rollouts on a 2–5 person engineering team. Built the internal side in React and TypeScript — admin panels, monitoring dashboards, QA utilities — along with the Node.js services, MongoDB, Postgres, and Next.js tooling behind them, and worked with product and engineering on customer-facing features. The company's product shifted from consumer streaming toward distributed compute while I was there; the internal tooling was the constant.

    ReactTypeScriptNext.jsNode.jsMongoDBPostgreSQLDocker
  2. Jan 2018 — Oct 2020

    Customer Support Lead · Streaming platform, later distributed compute

    Sole support contact for streamers and viewers through a period of rapid product change — triage, documentation, and direct escalation to engineering on high-impact issues. Spotting the pattern behind a pile of individual reports is what moved me into QA.

  3. Jan 2017 — Jan 2018

    Zendesk Admin / Support Specialist · Food-ordering platform

    Administered Zendesk and ran support operations for a food-ordering platform, working across operations and engineering.

    Zendesk

Happy to walk through any of the private work in detail.

What I do

How I can help

Whether you're hiring or you need something built, these are the areas I'm strongest in.

QA & reliability

Five years owning QA and scalability testing for a small engineering team. Not every bug is worth catching before release — the skill is knowing which ones are, then building the tests and tooling that catch those. Because I write the code too, I can usually fix what I find instead of filing a ticket about it.

  • QA & scalability testing
  • Failure-mode analysis
  • Internal QA tooling

Full-stack web apps

From a blank repo to something in production: data model, UI, auth, deploy pipeline. Both ends of it: admin panels, dashboards, and the internal tooling a team works in daily, plus the customer-facing features that sit in front.

  • Next.js / React / vanilla JS
  • Postgres schema design
  • Auth & access control

Real-time & integrations

The messy middle: wiring OAuth, syncing services that were never designed to talk to each other, gluing an LLM into a workflow, keeping several clients on the same state without going stale.

  • Supabase Realtime
  • Discord bots & OAuth
  • Serverless functions

Mobile & cross-platform

React Native via Expo when the thing genuinely belongs on a phone — notifications, offline storage, printable reports, over-the-air updates.

  • Expo / React Native
  • TypeScript end to end
  • iOS + Android from one codebase

Toolbox

What I work with

Practices
QA & scalability testingInternal toolingMonitoring dashboardsCross-functional collaboration
Languages
JavaScript (ES2022+)TypeScriptSQLHTMLSCSS / CSSJavaPHP
Frontend
ReactNext.jsReact Native / ExpoViteTailwind CSSChart.js
Backend & data
Node.jsSupabasePostgreSQLMongoDBRow-level securityRealtime subscriptionsREST APIs
Platform
DockerNetlify FunctionsVercelEAS UpdateGitHub ActionsGit
Integrations
Discord API (discord.js)OAuth 2.0Claude APIGoogle Sheets API

Side projects

What I build on my own time

These are hobby projects, which is exactly why I can show them in full — code included. Most of my professional work is in private repositories, covered under Experience above. Each one has a write-up on what the problem was, how it's put together, and what I'd change.

AFTL Raid Manager

2025 – present

Operations platform for a gaming guild — roster management, raid scheduling, a loot ledger, and a real-time PvP tournament arena.

Commits
246
Screens
16
Serverless functions
16
Schema migrations
53
Vanilla JSViteSupabasePostgreSQLNetlify FunctionsSCSS

Read the case study

AFTL Companion Bot

2025 – present

A Discord bot sharing one Postgres database with the raid manager — pushing roster changes, raid threads, and loot payouts into the chat where the guild already lives.

Commits
76
Slash commands
13
Event handlers
8
Lines of code
6.3k
Node.jsdiscord.js v14SupabaseClaude API

Read the case study

A cross-platform medication tracker built around separate profiles — dosing schedules, refill tracking, reminders, and printable adherence reports, all offline.

Lines of TypeScript
4.7k
Platforms
iOS + Android
Type coverage
100% TS
React NativeExpoTypeScriptExpo Router

Read the case study

About

A bit about me

I came into development sideways: support first, then QA, then building the internal tools the engineering team depended on. Eight years at the same growing engineering org, the last five-plus of them writing React and TypeScript — nearly all of it in private repositories I can talk through but can't link to, which is why the projects on this page are the ones I own outright.

They're also the ones where you can see the whole thing end to end: the schema, the migrations, the mistakes, and the parts I'd rebuild. I've spent as much time on permissions and "why did this break at 11pm" as on the fun parts. I care about interfaces that stay legible as they grow, and about not shipping abstractions before I've earned them.

Contact

Hiring, or have something you want built?

Email is the fastest way to reach me — I read everything and reply within a day or two. Tell me roughly what you have in mind and I'll tell you honestly whether I'm the right fit.

cjayson924@gmail.comGitHub