Senior Data and Reporting Solutions Analyst - Remote

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about UnitedHealthcare mission etc. We need to extract substantive content, not repeat job title, not include metadata like Job ID. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Intro: "At UnitedHealthcare, we're simplifying the health care experience, creating healthier communities and removing barriers to quality care. The work you do here impacts the lives of millions of people for the better. Come build the health care system of tomorrow, making it more responsive, affordable and optimized. Ready to make a difference? Join us to start Caring. Connecting. Growing together You are a thought leader who thrives on developing new solutions to solve tough challenges. As a critical member of our business analysis team, you will help rewrite the future of UnitedHealth Group. Here, your analytical and innovative skills will help us with our mission of helping people live healthier lives. Yes, we share a mission that inspires. And we need your organizational talents and business discipline to help fuel that mission. Are you ready to analyze data and deliver bold, business-savvy ideas to impact the lives of millions? Payment Integrity supports - 2,000+ ASO Customers, driving - $5B in savings annually. This team supports ASO customers by supplying reporting on savings and fees, as well as processing various financial transactions. This specific role supports the database that stores all our information. You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week." That's about the role, responsibilities maybe. Then "Primary Responsibilities" list bullet points. Then "You'll be rewarded and recognized for your performance..." that's benefits? Actually it's about rewards and recognition, maybe part of Benefits. Then "Required Qualifications" list. Then "Preferred Qualifications" list. Then "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" maybe part of Requirements? Could be a note. Then "Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc. In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution (all benefits are subject to eligibility requirements). No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives. The salary for this role will range from $72,800 - $130,000 annually based on full-time employment. We comply with all minimum wage laws as applicable." Thus we have Pay and Benefits. Schedule: mention remote flexibility and office requirement for Minneapolis or DC area: "You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week." That's schedule info. Thus we can have sections: About the role (intro), Responsibilities (list), Requirements (maybe combine Required Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe list of proficiencies?), Benefits, Pay, Schedule. But we must not create sections with filler. Need to ensure each section has substantive content. Let's extract: About the role: The introductory paragraphs describing mission, team, role context, remote flexibility, office requirement? Actually office requirement is schedule. But we can include remote flexibility in About the role. Responsibilities: The bullet list under Primary Responsibilities. Requirements: Could be "Required Qualifications" (3+ years experience with SDLC, 3+ years business analysis, advanced SQL, advanced Excel). Also maybe "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" could be a requirement. Qualifications: Could be "Preferred Qualifications" list. Skills: Could be the proficiencies listed under Preferred Qualifications (PowerBI, scripting, web automation, SQL Server). But those are also qualifications. Might be redundant. Perhaps we combine Required and Preferred into Qualifications and Skills? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. We can put: - About the role: introductory narrative. - Responsibilities: bullet list of primary responsibilities. - Requirements: Required Qualifications (the mandatory ones). - Qualifications: Preferred Qualifications (the preferred ones). - Skills: maybe list of specific technical skills (SQL, Excel, PowerBI, scripting, web automation, SQL Server) but those are already in qualifications. Could instead list "Advanced or higher level of proficiency with SQL", etc. But we might avoid duplication. Perhaps we can put Skills as the list of proficiencies (SQL, Excel, PowerBI, scripting, web automation, SQL Server). But we need to ensure we don't invent content; we can extract from posting. Let's extract skills: From Required Qualifications: "Advanced or higher level of proficiency with SQL", "Advanced or higher level of proficiency with Excel". From Preferred Qualifications: "Experience working in the Health Care Industry", "Experience working with PowerBI reporting", "Advanced or higher proficiency with Scripting", "Advanced or higher proficiency with Web Automation", "Advanced or higher proficiency with SQL Server". Thus Skills could be those proficiencies. But we also have "Experience working in the Health Care Industry" and "Experience working with PowerBI reporting" which are more experience than skill. Could still be under Skills. Alternatively, we could put those under Qualifications (Preferred) and Skills could be empty? But we must not create empty sections. So we need to decide. Maybe better: Use Requirements for Required Qualifications, Qualifications for Preferred Qualifications, Skills for the technical proficiencies (SQL, Excel, PowerBI, scripting, web automation, SQL Server). But then we would duplicate some content (SQL, Excel appear both in Requirements and Skills). That's okay as long as we preserve all substantive information; duplication is allowed? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. However, we could avoid duplication by moving SQL/Excel to Skills and not repeat in Requirements? But Requirements includes those as required qualifications; we need to keep them. Could keep them in Requirements and also list them in Skills; that's duplication but preserves info. Might be okay. Alternatively, we could treat Skills as the list of specific technical proficiencies (SQL, Excel, PowerBI, scripting, web automation, SQL Server) and keep Requirements as the years of experience and business analysis etc. That seems reasonable. Thus: About the role: intro paragraphs (maybe up to before Primary Responsibilities). We'll need to trim any boilerplate like EEO etc. We'll exclude EEO, legal, drug-free workplace, etc. Also exclude application instructions, deadline, etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we will exclude: - "Application Deadline: This will be posted for a minimum of 2 business days or until a sufficient candidate pool has been collected. Job posting may come down early due to volume of applicants." - The EEO statement paragraphs. - "UnitedHealth Group is an Equal Employment Opportunity employer ..." - "UnitedHealth Group is a drug-free workplace. Candidates are required to pass a drug test before beginning employment." - Also maybe the mission statement repeated later? We'll keep only one mission statement? The intro includes mission; later there is another mission statement about helping people live healthier lives and making health system work better. That's duplicated; we should keep only one instance? The instruction says remove duplicated lines. So we should keep only one occurrence of similar mission statements. We'll keep the first intro maybe and drop the later duplicate. - Also "At UnitedHealth Group, our mission is to help people live healthier lives and make the health system work better for everyone." That's duplicate of earlier mission. We'll drop. - Also the paragraph about barriers, disparities, etc. That's maybe not duplicated but is part of EEO? It's about commitment to mitigating impact, equitable care. Might be considered boilerplate? It's not EEO but it's a corporate social responsibility statement. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly EEO but could be considered corporate responsibility; not sure. Safer to keep? It's not duplicated elsewhere. It's substantive about mission. Might be okay to keep. But it's somewhat generic. However, we need to preserve ALL substantive information; not summarizing away detail. So we should keep it unless it's considered boilerplate. It's about commitment to mitigating impact, equitable care, addressing health disparities. That's part of mission; could be considered substantive. We'll keep it. But we need to avoid duplication: we have similar mission statements earlier and later. We'll keep the first and drop the later duplicate. Now, let's extract the intro up to before "Primary Responsibilities". The intro includes: "At UnitedHealthcare, we're simplifying the health care experience, creating healthier communities and removing barriers to quality care. The work you do here impacts the lives of millions of people for the better. Come build the health care system of tomorrow, making it more responsive, affordable and optimized. Ready to make a difference? Join us to start Caring. Connecting. Growing together You are a thought leader who thrives on developing new solutions to solve tough challenges. As a critical member of our business analysis team, you will help rewrite the future of UnitedHealth Group. Here, your analytical and innovative skills will help us with our mission of helping people live healthier lives. Yes, we share a mission that inspires. And we need your organizational talents and business discipline to help fuel that mission. Are you ready to analyze data and deliver bold, business-savvy ideas to impact the lives of millions? Payment Integrity supports - 2,000+ ASO Customers, driving - $5B in savings annually. This team supports ASO customers by supplying reporting on savings and fees, as well as processing various financial transactions. This specific role supports the database that stores all our information. You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges. For all hires in the Minneapolis or Washington, D.C. area, you will be required to work in the office a minimum of four days per week." We need to ensure we don't include the asterisk footnote maybe. We'll keep remote flexibility note. Now, Responsibilities: bullet list: - Manage/Maintain SQL database that supports ASO-customer reporting for Payment Integrity savings and fees - Work with cross-functional teams to ingest new data into the database as well as maintaining existing connections - Design and Develop automations and procedures to support the savings reporting and billing processes - Implement quality control processes to ensure accurate flow of information and optimal structure of tables - Predict emerging customer needs and develop innovative solutions to meet them - Solve unique and complex problems with broad impact on the business - Participate in the development of business strategy - Translate highly complex concepts in ways that can be understood by a variety of audiences - Plan and implement every needed process steps as defined in methodologies Now, Requirements: Required Qualifications: - 3+ years of experience with full Software Development Life Cycle - 3+ years of experience with business analysis, business reporting, data quality, or similar data query work - Advanced or higher level of proficiency with SQL - Advanced or higher level of proficiency with Excel Also maybe "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" could be a requirement but it's more of a policy. Could be placed under Requirements or maybe under Schedule? It's about remote work policy. Might be better under Requirements