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.
- Catch state machine breaks where authorization workflows get stuck mid-transition or allow invalid state jumps. Devs test happy paths; I test what happens when users click Cancel halfway through a 6-step form.
- Built 14 custom scripts 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.
Ultranauts Inc
·
Software Quality Engineer II
Oct 2021 – Feb 2023 / Remote
- Figured out early that automation isn't always faster. First job where I pushed back on "automate everything": some workflows just create maintenance debt that way.
- Wrote unit tests with Jest for NestJS/TypeScript apps [↗]. Started with zero testing knowledge, ended writing 200+ line test files. 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 and Databricks.
03
Skills
QA Specializations
- Healthcare / Internal Tools Testing
- Role-Based Permissions Testing
- Data Integrity Validation
- Cross-Browser Regression
- Release Readiness Assessment
- Edge Case Generation
Automation & Tools
- Playwright
- REST / GraphQL
- React / Vue
- SQL
- Claude & Gemini
- Python
- JavaScript / TypeScript
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 and 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
Data Confluence Pipeline
Finds patterns across 6,671+ tickets that individual issue views miss
Data aggregation pipeline across 6,671+ healthcare platform tickets. Python scripts pull patterns and feature timelines that aren't visible ticket-by-ticket. Source data: JIRA exports, Confluence docs, conversation history. Used for release planning and tracking where technical debt actually lives.
PythonETLSQL
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