Translate the requirements
Turn benefits and carrier requirements into field mappings, file specifications, business rules, and testing needs.
Benefits technology · Business systems · Data integrity
HRIS & Benefits Systems Analyst
I translate benefits requirements into data mappings, testing plans, and clear implementation workflows—connecting the business rules to the systems that carry them.
Oklahoma City · Open to remote opportunities

01 / What I bring
Benefits data moves through multiple systems and teams. My work connects the requirements, the file logic, and the people responsible for getting it right.
Turn benefits and carrier requirements into field mappings, file specifications, business rules, and testing needs.
Investigate rejected records and data inconsistencies across source values, transformation logic, transmission, and downstream output.
Build implementation workflows, documentation, and handoffs that help business and technical teams work from the same requirements.
02 / Experience
Experience spanning benefits data exchange and implementation management, supported by independent project work in benefits reconciliation.
Mapped requirements across employer, benefits administration, carrier, and billing systems. Investigated data and transmission discrepancies, coordinated resolution, and developed implementation workflows and handoff documentation.
Prepared mappings and transformation rules for benefits enrollment and carrier files. Reviewed output against carrier requirements and traced rejected records, mapping defects, and transmission problems across source data and downstream systems.
Technical context: HIPAA 834, LDEx XML, fixed-width and CSV files, SFTP, and PGP.
03 / Selected work
Independent project work adds context to my professional experience: how I define a problem, organize the data, and translate business rules into a system design.
Independent project / VPSG
Payroll, enrollment, and billing records describe the same benefits activity in different ways. This project explores how to compare those records and make discrepancies easier to investigate.
My contribution: Requirements and design work covering relational data structures, file intake, validation, reconciliation, exception handling, and reporting.
Problem: Different data sources need consistent comparison rules before a discrepancy can be interpreted.
Approach: Map source fields, define validation and comparison rules, and organize exceptions into a review workflow.
A simplified illustration of the project’s analytical approach.
04 / Next steps
I’m interested in HRIS and benefits systems analyst opportunities, including related business systems and implementation roles.