System Analyst/ QA Manager

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate. Need to parse the posting. Let's extract content. The posting text: "Due to the number of years exp with Medicaid they are seeking, I will consider candidates that need to relocate to Richmond, however the preference still stands for candidates that are already within 50 mile radius of Richmond VA. Web interview, 3 days a week onsite. Preference for candidates that currently reside within 50 mile Radius of Richmond VA. ON SITE REQUIRED: 3 days onsite. Parking is not provided for contractors This position is for a Systems Analyst/QA Manager for the HR1 Medicaid project will lead all Quality Assurance activities, ensuring deliverables meet state Medicaid requirements while coordinating closely with multiple state agencies, business teams, and external vendors. This role manages the full testing lifecycle, including designing the overall test strategy, planning, execution, reporting, detailed test data preparation, and overseeing End to End (E2E) testing. The SA/QA Manager will coordinate testing efforts with business teams to obtain user scenarios and test cases, organize meetings, support UAT, ensure proper test coverage and traceability, and perform test readiness reviews. Additional responsibilities include maintaining defect management processes, validating data integrity across systems, ensuring consistent QA documentation and standards, and conducting post test assessments to confirm resolution of issues. The role also identifies risks early, partners with the PMO office for project oversight, and ensures strong communication across agencies, vendors, and project leadership throughout the HR1 implementation. Responsible for all System Integration Testing (SIT), User Acceptance Testing (UAT), and End2End Testing (E2E) for the MMIS and MES modules as well as the testing of configured Commercial off the Shelf (COTS) applications, and the testing of conversion and integration of data from other systems in Medicaid Enterprise Systems (MES Modules and COTS products). Significant experience in managing the defect triage calls with multiple vendors and tracking the defects to closure in a timely fashion is required.Expected to have the ability to understand the requirements and design of the project and able to develop test cases, test data and verify the software changes and to problem solve issues that are escalated and serve as liaison between the developer and the Business User. Responsible for communicating and reporting to a variety of stakeholders about the results and progress of all UAT Testing including Test Summary and Execution metrics. Escalating and tracking UAT defects through the resolution. Mainframes Experience Is Required Track and maintain historical UAT Testing information. Able to meet deadlines with a high level of integrity, professionalism, customer service and motivation. Significant experience in managing UAT, defect triage calls and Co-ordination involving multiple systems/Vendors/Teams is required. Skills Matrix: Experience with Teradata queries is Preferred. Skill Required / Desired Min Yrs Exp Required Actual Yrs Exp Year Last Used Experience with a large Scale Medicaid Member Eligibility Processing Software Required 15 Experience with coordination of SIT, UAT and End2End Testing activities on a large scale project Required 10 Experience with Test Scenario Development, Test Case Creation, Test Data Preparation, Test Case Execution, Defect Tracking, Metrics reporting Required 10 Excellent communication and stakeholder engagement skills, including the ability to explain technical concepts to non technical audiences Required 15 Executive/Management Reporting & Presentations Required 10 Experience with Mainframes Required 10 Experience in Data Analysis Required 10 Meeting Facilitation Required 10 Knowledge of programming logic Required 10 Experience collaborating with vendors, system integrators, and multidisciplinary teams Required 10 Experience with Teradata Desired 1" We need to separate sections: About the role (maybe a brief description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have location/relocation info, interview type, onsite requirement, parking not provided. That could be part of About the role or maybe Schedule? Actually schedule: "Web interview, 3 days a week onsite." "ON SITE REQUIRED: 3 days onsite." So schedule: 3 days onsite per week. Also maybe mention web interview (but that's part of hiring process, not schedule). Could include schedule section: "3 days onsite per week". Also mention "Parking is not provided for contractors" maybe as a note under Benefits? Actually benefits: none mentioned. So we should not create Benefits section if no specific content. Pay: none mentioned. So we omit Pay and Benefits. We need to include About the role: maybe a paragraph summarizing the role: Systems Analyst/QA Manager for HR1 Medicaid project, leading QA activities, etc. Responsibilities: list bullet points from responsibilities paragraphs. Requirements: maybe the years of experience matrix? Or required experience? Could be "Experience with a large Scale Medicaid Member Eligibility Processing Software Required 15", etc. Those are requirements with years. Qualifications: maybe the skills matrix? But we have Skills section separate. Could treat Skills as separate. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. So we need to include the location preference, relocation consideration, web interview, 3 days onsite, parking not provided. We need to include the responsibilities list: lead QA activities, ensure deliverables meet state Medicaid requirements, coordinate with agencies, manage full testing lifecycle, design test strategy, planning, execution, reporting, detailed test data preparation, oversee E2E testing, coordinate testing efforts with business teams to obtain user scenarios and test cases, organize meetings, support UAT, ensure proper test coverage and traceability, perform test readiness reviews, maintain defect management processes, validate data integrity across systems, ensure consistent QA documentation and standards, conduct post test assessments to confirm resolution of issues, identify risks early, partner with PMO office for project oversight, ensure strong communication across agencies, vendors, and project leadership throughout HR1 implementation, responsible for all SIT, UAT, and E2E testing for MMIS and MES modules, testing of configured COTS applications, testing of conversion and integration of data from other systems in Medicaid Enterprise Systems (MES Modules and COTS products), manage defect triage calls with multiple vendors, track defects to closure timely, understand requirements and design, develop test cases, test data, verify software changes, problem solve escalated issues, serve as liaison between developer and business user, communicate and report to stakeholders about UAT results and progress including Test Summary and Execution metrics, escalate and track UAT defects through resolution, Mainframes experience required, track and maintain historical UAT testing information, meet deadlines with integrity, professionalism, customer service, motivation, significant experience managing UAT, defect triage calls and coordination involving multiple systems/vendors/teams. Also "Skills Matrix: Experience with Teradata queries is Preferred." plus the list of skills with required years. We need to separate Skills section: list each skill with required years? The posting includes a "Skill Required / Desired Min Yrs Exp Required Actual Yrs Exp Year Last Used" then lines: Experience with a large Scale Medicaid Member Eligibility Processing Software Required 15 Experience with coordination of SIT, UAT and End2End Testing activities on a large scale project Required 10 Experience with Test Scenario Development, Test Case Creation, Test Data Preparation, Test Case Execution, Defect Tracking, Metrics reporting Required 10 Excellent communication and stakeholder engagement skills, including the ability to explain technical concepts to non technical audiences Required 15 Executive/Management Reporting & Presentations Required 10 Experience with Mainframes Required 10 Experience in Data Analysis Required 10 Meeting Facilitation Required 10 Knowledge of programming logic Required 10 Experience collaborating with vendors, system integrators, and multidisciplinary teams Required 10 Experience with Teradata Desired 1 We could present as a list with each skill and required years. Qualifications: maybe the years of experience overall? Could be "Due to the number of years exp with Medicaid they are seeking" but that's vague. Might be better to treat Qualifications as the same as Requirements? But we need to follow instruction: include sections only when posting has real specific content. We have content for Responsibilities, Skills, maybe About the role, Schedule. Requirements could be the years of experience matrix? But that is also skills. Might combine Requirements and Skills? However we need to decide. We could treat: - About the role: brief paragraph summarizing role and location preferences. - Responsibilities: bullet list of duties. - Requirements: list of required experience (the years matrix) maybe as bullet list. - Skills: maybe the same as Requirements? But we could separate: Requirements = the years of experience for each area; Skills = the specific technical skills (Teradata, Mainframes, etc). However the matrix includes both. Better: Use Requirements for the years of experience (the matrix). Use Skills for the specific technical skills like Teradata, Mainframes, etc. But the matrix already includes those. Alternatively, we could have only About the role, Responsibilities, Requirements (which includes the skill/experience matrix), and Schedule. Avoid Skills if duplicate. But the instruction says to use headings for sections like Skills, Benefits, Pay, Schedule. It's okay to omit Skills if not distinct. We need to include Schedule: "3 days onsite per week" plus maybe "Web interview" (though that's not schedule). Could include "Web interview (initial), 3 days onsite per week". Also mention parking not provided for contractors (maybe under Schedule? Not really). Could add a note under About the role. Let's craft. About the role paragraph: combine location preference, relocation consideration, web interview, 3 days onsite, parking not provided, role title. Responsibilities: bullet list. Requirements: bullet list of required experience with years (the matrix). Could phrase each as "Experience with X: 15 years required" etc. Schedule: bullet: "3 days onsite per week (onsite required)". Could also mention "Web interview (initial)". We must not invent or summarize away detail. Must preserve all substantive info. So we need to include each bullet from responsibilities exactly as in text, not summarizing too much. But we can condense slightly but must keep all details. However we can combine similar items but must not lose detail. Safer to list each responsibility as separate bullet, preserving the meaning. Let's extract responsibilities sentences: - "lead all Quality Assurance activities, ensuring deliverables meet state Medicaid requirements while coordinating closely with multiple state agencies, business teams, and external vendors." - "manage the full testing lifecycle, including designing the overall test strategy, planning, execution, reporting, detailed test data preparation, and overseeing End to End (E2E) testing." - "coordinate testing efforts with business teams to obtain user scenarios and test cases, organize meetings, support UAT, ensure proper test coverage and traceability, and perform test readiness reviews." - "maintaining defect management processes, validating data integrity across systems, ensuring consistent QA documentation and standards, and conducting post test assessments to confirm resolution of issues." - "identifies risks early, partners with the PMO office for project oversight, and ensures strong communication across agencies, vendors, and project leadership throughout the HR1 implementation." - "Responsible for all System Integration Testing (SIT), User Acceptance Testing (UAT), and End2End Testing (E2E) for the MMIS and MES modules as well as the testing of configured Commercial off the Shelf (COTS) applications, and the testing of conversion and integration of data from other systems in Medicaid Enterprise Systems (MES Modules and COTS products)." - "Significant experience in managing the defect triage calls with multiple vendors and tracking the defects to closure in a timely fashion is required." - "Expected to have the ability to understand the requirements and design of the project and able to develop test cases, test data and verify the software changes and to problem solve issues that are escalated and serve as liaison between the developer and the Business User." - "Responsible for communicating and reporting to a variety of stakeholders about the results and