KAYLA GILBERT // RESUME

01 About

I keep messy healthcare workflows reliable. I cover 5+ products solo, specializing in internal tools with a dozen user roles, interconnected workflows, and conditional UI. When something keeps breaking or takes too long, I build a process, template, or small tool to fix it. I use Claude and Gemini to find edge cases and clean up bad requirements.

02 Experience

Chorus Innovations · Senior QA Specialist PROMOTED 2024

Apr 2023 – Present / Remote

Own release-readiness decisions across 5+ healthcare products as sole QA—no backup, so if I'm out sick, releases either slip or ship risky. One authorization workflow alone has 6 stages, 3 PDFs per stage that need manual verification, reversions that reset state, and role-based permission checks at every transition. I'm the quality and risk gate.
Design test matrices for multi-role workflows (doctors, nurses, admins, patients) with 20+ conditional paths and UI that shifts per role and state
Caught state machine breaks where authorization workflows got stuck mid-transition or allowed invalid state jumps—like skipping approval stages that should be required. Devs test happy paths; I test what happens when users click Cancel halfway through a 6-step form
Built 14 custom scripts (video analysis, form autofill, test plan generation) that cut triage from ~4 hours to under 1 hour per release. The test plan generator has saved me multiple times—turns vague requirements into testable matrices so I'm not guessing what "works correctly" means
Catch data mismatches between UI and backend (patient records, appointment states, billing data), keeping PHI boundaries and data exposure risk in mind
Push back on happy-path-only releases, nail down requirements with product and engineering before code ships, and write Jira tickets with clear repro steps and acceptance criteria

Ultranauts Inc · Software Quality Engineer II

Oct 2021 – Feb 2023 / Remote

Worked with enterprise and startup clients, owning test strategy and determining where automation would save time vs. adding overhead
Built Selenium test suites for workflows with complex business rules (multi-step forms, conditional logic, role-based access)
Set testing standards for the team and created Confluence templates that sped up onboarding and documentation

03 Skills

QA Specializations

Healthcare / Internal Tools Testing
Role-Based Permissions Testing
Data Integrity Validation
Cross-Browser Regression
Release Readiness Assessment
Edge Case Generation
Requirements Analysis

Automation & Tools

Playwright
Selenium
Testmo
Jira & Confluence
Claude & Gemini
Python
JavaScript / TypeScript
HTML / CSS

What Doesn't Scale (Yet)

Single point of failure: If I'm out, releases slip or ship with untested edge cases
Tribal knowledge: I know which workflows break when users have multiple sessions open, which state transitions create orphaned records, which async operations fail silently—none of this is documented
Custom tooling lock-in: 14 scripts that save me hours but would take a week+ to hand off and explain

04 Projects

01

Data Confluence Pipeline

Built because Slack search was useless after 3 months and I was re-answering the same questions

Python ETL pipeline that pulls from Slack, email, Google Docs, and other apps into one searchable knowledge base. Deduplicates records and uses AI to classify thousands of entries.

PythonETLAPI Integration

02

Projects Dashboard

Built after waiting 12 minutes per rebuild got unbearable—needed sub-second iteration

Monorepo dashboard for 7+ React apps with shared components and build caching. Rebuild time: ~15s to under 200ms.

ReactTypeScriptViteTailwindTurborepopnpm Workspaces

03

QA Workflow Automation Toolkit

~75% faster test planning and setup with tools I built myself

14 custom scripts for my own workflows: AI video analysis for bug triage, form autofill, test plan generation, and Jira batch processing.

TypeScriptNode.jsClaude APIGemini APIJavaScript

05 Links

linkedin.com/in/snackdriven

GitHub

github.com/snackdriven