Monthly Findings Quality Reviewer

MerlinJourneys reports every bug with an explanation and a suggested fix. A report is only useful when people trust it, so we want an experienced tester reading a sample of findings every month and telling us which ones are right. Each month you review an agreed sample of findings from demo projects and projects that have agreed to this review. For each one you decide whether it is real, how severe it is, and whether the explanation and fix would help a developer. Deliverable: a labeled spreadsheet and a short note on the patterns behind false alarms and wrong severity. Done for a month means the whole sample is labeled and the top three patterns are written up with examples. Mandatory: software QA, browser DevTools, reading console and network errors, UX judgment. Nice to have: Ruby on Rails or Next.js, accessibility audits, data labeling experience.