Dear Hiring Manager,
Coordinating UAT across 20 testers at Meridian Health Systems taught me that a defect found in Jira on a Tuesday is cheaper than the same defect found by a member after release. I triaged 60 of them on the claims project and tracked each one to closure, which is how that release landed at a 0.4% post-release defect rate. The same discipline starts upstream, in the acceptance criteria themselves: I write SQL against the data warehouse to confirm eligibility logic actually holds before a single test case is run. A claims and eligibility consolidation at Cypress Ridge Health Plan is the kind of work where that order of operations pays off.
At Meridian I elicited requirements from 12 clinical and billing stakeholder groups through workshops and interviews, producing BRDs and more than 140 user stories that cut mid-sprint requirement changes by 38%. I mapped current- and future-state claims workflows in BPMN, surfacing 9 process gaps that informed a redesign and trimmed average claim handling time from 11 days to 7. Earlier, at Northpoint Financial, I partnered with QA to define test scenarios that lifted first-pass UAT acceptance from 72% to 91% over four releases, so the requirements I wrote held up once they reached delivery.
I hold the CBAP and the IIBA-AAC from IIBA, but the part that matters here is the habit underneath them: requirements that are traced, validated against the source data, and held accountable in UAT before anything ships to a member. If you bring me on, the first thing I would scope is your eligibility rules, mapping where each one actually lives and where two definitions disagree. I am open to a call this week or next to talk through where Cypress Ridge would want a business analyst to start.