I own QA for 5+ healthcare products. No backup means I'm a single point of failure. I test edge cases manually and build scripts when processes waste time repeatedly. 4-hour triage became a 1-hour script, 63-section forms became templates. 14 tools later, I've automated myself out of the boring work but not the job. Still need humans to catch what breaks in weird ways.
01
About
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). 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 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
- Tested software for fintech and SaaS clients. First job where I had to figure out when automation saves time vs when it just creates maintenance work. Learned to push back on "automate everything" and argue for manual testing when it made sense.
- Wrote unit tests with Jest for NestJS/TypeScript apps [↗]. Started with zero testing knowledge, ended writing 200+ line test files with mocks, error handling, and edge cases. Tests broke when requirements changed, which taught me to test behavior instead of implementation.
- Built BI dashboards with Vue.js and D3 [↗]. Wrote Cube.js schemas [↗] to define SQL measures and dimensions, then built frontend components to visualize financial data (fund cohorts, borrower demographics, CF prepayment rates). First time working with SQL, Databricks, and semantic layers.
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
- API Testing
- React / Vue
- SQL
- 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
Analyzes patterns across 6,671 tickets that aren't visible when looking at individual issues
Data aggregation pipeline for strategic decision-making across 6,671+ healthcare platform tickets. Python scripts extract patterns, feature timelines, and product roadmaps that aren't visible when looking at individual JIRA tickets. Consolidates JIRA exports, Confluence docs, and conversation history into queryable insights for release planning and technical debt analysis.
PythonETLSQL
02
Projects Dashboard
Built after 12-minute rebuilds got unbearable. Needed sub-second iteration
Monorepo dashboard managing 16 React/Vue apps with shared components and build caching. Rebuild time: ~15s to under 200ms.
ReactTypeScriptViteTailwindTurborepopnpm Workspaces
03
QA Workflow Automation Toolkit
Cut test planning from ~40 minutes to under 10 with custom scripts
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