Senior Business Analyst resume example

• As workstream lead, translated claims-workflow requirements into a user story and acceptance criteria in Jira; documented exception rules and obtained business review before developers estimated the change.
• With responsibility for the review standard, used SQL to reconcile migrated records and identify duplicate identifiers before Agile acceptance testing; attached failing examples to the acceptance criteria so the business owner could make a traceable sign-off decision.
• As workstream lead, automated SQL reconciliation with Python against a de-identified AWS staging extract. Grouped differences by business rule and attached reproducible exceptions to Jira; resolved the disputed acceptance criteria with the business owner before migration sign-off.
• Mapped business rules to data fields and acceptance tests, reconciled contradictory stakeholder requests, and walked users through exception scenarios before sign-off.
• Owned a requirements review using SQL metric reconciliation, resolved conflicting business definitions and completed Agile acceptance criteria with the process owner.
• Built a Python validation notebook using an approved AWS data extract, reduced reconciliation preparation from 85 to 35 minutes and published the metric assumptions.

• Coordinated UAT with business users using scenario-based test cases, a defect triage log, and explicit sign-off owners; aligned review standards and decision owners across the participating teams. Working with partner teams, kept unresolved control failures visible instead of treating every completed test as a pass.
• Reviewed a delivered feature against acceptance criteria with design and engineering, documented the unresolved usability issue, and agreed whether it should block release or enter the next iteration.
• Traced a late scope request to the underlying user need, compared it with the agreed release goal, and worked with delivery partners to split required behavior from a follow-up enhancement. Updated acceptance criteria before development continued.

• Used SQL to reconcile source transactions against the proposed reporting model, testing null values, duplicate invoices, and currency conversion dates; aligned review standards and decision owners across the participating teams
• Used a public product workflow to map the user problem, decision points and acceptance criteria; marked assumptions separately from observed behavior and prioritized an experiment before specifying a complete redesign.
• Prepared a decision log showing alternatives, dependencies and the metric that would reverse the recommendation; walked through an exception path and updated the acceptance criteria when ownership was unclear.
• Owned the independent prototype review using task-based acceptance criteria, resolved an ambiguous exception path and completed a test plan with an explicit stopping rule.

Relevant coursework: Financial accounting, statistics, operations management, organizational behavior

• Published a personal product case study using the project decision log, explaining rejected alternatives, testable assumptions and the evidence needed before a production launch.