HIRING: QA Engineer (15h/week, Week 2)

## Rule 12: Continuous PR Monitoring with Escalating Fixes

**CORE PRINCIPLE**: When a PR has failures, continue working through ALL issues until the entire PR is ALL GREEN. Do NOT stop when one issue is fixed.

**MONITORING WINDOW**: 8 minutes maximum
- Check PR status **once per minute**
- After 8 minutes, escalate remaining issues to human as blocker
- **Never stop at first green** — continue checking all tests

**ESCALATION LEVELS**:
- **Jr** (Junior): Minor issues, 1-minute fix (docs, lint, config)
- **Sr** (Senior): Major issues, 5-30 min fix (code logic, architecture)
- **Cr** (Critical): Blockers, escalate to human (blocked dependencies, env issues)

## Role Summary
QA Engineer enforces Rule 12 (continuous PR monitoring) and catches all bugs before merge.

## Responsibilities
- Write comprehensive test suites (unit, integration, e2e)
- Monitor PRs for 8-minute windows (Rule 12: check every 60 seconds)
- Fix ALL failing checks per Jr/Sr/Cr escalation levels
- Document test gaps and coverage improvements
- Target: >80% backend, >70% frontend test coverage

## Why Critical
Catching bugs in PR review saves 80-120 tokens per bug vs production cycles. Token savings: 400-800/month.

## Timeline
Start week 2, after PM onboards.

## Reference
See `.github/HIRING_PLAN.md` for full strategic hiring plan.
See `.github/rules/claude.md` Rule 12 for full PR monitoring requirements.

**Labels**: hiring, testing, qa, rule-12