Network Pricing Consultant - Remote

We need to output HTML fragment with sections: About the role? The posting includes description about Optum, mission, etc. We need to decide sections: maybe "About the role" (summary), "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". Must only include sections with real content. We need to parse content: - Intro paragraph about Optum: "Optum is a global organization...". That's about the company, could be "About the role"? Actually "About the role" is typical heading for role description. But we have a description of the role: "OptumRx is looking for a curious, adaptable, and self-motivated analyst...". So we can put that under "About the role". Also we have "Position Description" and "Primary Responsibilities". So we can have "Responsibilities" section with bullet list of responsibilities. - "Required Qualifications" and "Preferred Qualifications" can go under "Qualifications" maybe separate "Required Qualifications" and "Preferred Qualifications"? But we can combine under "Qualifications" with subheadings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Qualifications" heading and list required and preferred as bullet points. - Skills: maybe we can extract skills from qualifications: proficiency in SQL, Python, Tableau, communication skills, etc. Could put under "Skills". But we might also include them in Qualifications. However we need to avoid thin sections. If we have both Qualifications and Skills, we need to ensure each has substantive content. We could put skills under Qualifications and not create separate Skills section if not enough distinct content. But we have explicit skill mentions: "Advanced proficiency in performing financial impact analysis, risk management, and data manipulation", "Proficiency in SQL, Python and/or Tableau", "Proven solid written and verbal communication skills". That's enough for a Skills section. - Benefits: The posting mentions "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)." Also earlier: "Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities." Also "You'll be rewarded and recognized for your performance...". So we have benefits content. - Pay: The posting includes "The salary for this role will range from $72,800 to $130,000 annually based on full-time employment." Also "Pay is based on several factors including but not limited to local labor markets, education, work experience, certifications, etc." So we have pay info. - Schedule: The posting mentions "You'll enjoy the flexibility to work remotely * from anywhere within the U.S. as you take on some tough challenges." That's schedule/remote work. So we can have Schedule section with remote work flexibility. We must not include boilerplate like EEO, legal, application instructions, etc. Remove duplicated lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format as bullet lists. We must not repeat the job title as a heading. The job title is "analyst" maybe not needed. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment, no /, no markdown fences. Let's craft sections:

About the role

OptumRx is looking for a curious, adaptable, and self-motivated analyst to be part of our Network Pricing team. This is an intermediate analytics role where you will learn the business fundamentals of drug pricing and client performance management, the underlying data flows, and the tools and systems used in this type of financial analysis. The person in this role will work with and have regular exposure to analysts and projects in our global data science and network pricing teams. In addition, solid communication skills are important as this role partners with other departments including Underwriting, Contracting, Account Management, Operations and Tech teams to innovative new product offerings and effectively oversee client and pharmacy performance. You'll enjoy the flexibility to work remotely from anywhere within the U.S. as you take on some tough challenges.

But note we already have remote flexibility in Schedule; maybe we mention remote work in About the role but also schedule. Could keep remote mention in About the role but also schedule. It's okay. Now Responsibilities: we have a big list under "Position Description" and "Primary Responsibilities". We need to capture all bullet points. Let's extract responsibilities: From Position Description: - Supports and validates Provider Network (physicians, hospitals, pharmacies, ancillary facilities, etc.) contracting and unit cost management activities through financial and network pricing modeling, analysis, and reporting. - Conducts unit cost and contract valuation analysis in support of network contracting negotiations and unit cost management strategies. - Manage unit cost budgets, target setting, performance reporting, and associated financial models From Primary Responsibilities (list): - Support the development of new products or strategic initiatives aimed at reducing the total cost of care - Represent Network Pricing in cross functional meetings (governance, strategy discussions, client implementations) - Transforms data into meaningful and easy to understand insights for various audiences - Create specifications to bring data into a common structure, create product specifications and models, developing data solutions to support data analysis - Partner with stakeholders to understand data requirements and business needs and develop tools and models, and to assist building of dashboards and data visualizations - Develop insights and proposals for improved business processes to enable speedy deployment and testing of future projects - Build operational workflows, documentation and QA controls for repeatable and compliant pricing execution - Product, service, or process decisions are most likely to impact multiple groups of employees and/or customers (internal or external) - Lead and perform financial analysis and modeling as it relates to setting prescription drug prices - Monitor pricing performance against financial targets, approve deviations, and adjust strategies as necessary. - Perform data mining, claims research, and QA drilling down on drivers associated to client performance - Prepare regular and ad hoc reports on pricing performance, financial outcomes, and client reporting - Concisely summarize and communicate complex concepts, statistical findings and conclusions in ways that can be understood by a variety of audiences - Translate and decipher contract language as it relates to client commitments and reconciliation - Proactively identify and resolve issues - Partner with other departments including Underwriting, Legal, Operations, and Account Management to effectively oversee client performance management - Conduct or support market intelligence research for competitive drug costs, including supply chain, insured benefits, discount card (i.e. cash card), NADAC, and other reference points - Enhance and utilize pricing trackers and tools to forecast trends and recommend adjustments for new product offering Also earlier: "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." That's more about benefits/culture, maybe not responsibility. We'll include all these as

• . Now Qualifications: Required and Preferred. Required Qualifications: - 5+ years of analytical experience in financial analysis, healthcare pricing, network management, healthcare economics, or related discipline - 2+ years of experience in creating and using financial modeling tools, spreadsheets, and information acquisition tools including experience in interpreting and/or displaying financial modeling results to inform actionable decisions - Advanced proficiency in performing financial impact analysis, risk management, and data manipulation Preferred Qualifications: - Previous Healthcare or PBM experience - Experience in product development or supporting new service offerings - Proficiency in SQL, Python and/or Tableau - Proven solid written and verbal communication skills Also note: "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" - that's maybe a note but could be under Schedule or Benefits? It's a policy; we could include under Schedule as note. Now Skills: we could extract skills: financial impact analysis, risk management, data manipulation, SQL, Python, Tableau, communication skills, financial modeling tools, spreadsheets, data acquisition, etc. But we already have qualifications covering similar. To avoid duplication, maybe we don't need separate Skills section; we can put skills under Qualifications. But the instruction allows Skills section; we need to decide if we have enough distinct content for Skills beyond qualifications. Since qualifications already list experience and proficiency, we could still create Skills section focusing on technical skills: SQL, Python, Tableau, financial modeling, data visualization, communication. But that would duplicate content. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicating is okay as long as we preserve info, not omit. However we should avoid unnecessary repetition? Not prohibited. But better to avoid thin sections. If we create Skills section, we need to ensure it's substantive. We could list skills: SQL, Python, Tableau, financial modeling, spreadsheets, data acquisition, data visualization, communication, financial impact analysis, risk management. That's substantive. But we already have qualifications that include those. It's okay to repeat. Alternatively, we could combine Required and Preferred under Qualifications and not have Skills. That would reduce sections. The instruction says "Prefer a few substantive sections over many thin ones." So better to have fewer sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's 6 sections. That's fine. We'll not create Skills section. Now Benefits: we need to capture all benefits info. From posting: - "Here, you will find a culture guided by inclusion, talented peers, comprehensive benefits and career development opportunities." - "You'll be rewarded and recognized for your performance in an environment that will challenge you and give you clear direction on what it takes to succeed in your role as well as provide development for other roles you may be interested in." - "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." Also earlier: "comprehensive benefits and career development opportunities." Also maybe "comprehensive benefits package" etc. We'll create bullet list. Pay: we have salary range and note about factors. Schedule: remote work flexibility, mention telecommuter policy. Now we need to ensure we don't include boilerplate like EEO, legal, drug-free workplace, etc. Remove those. Also remove "Application Deadline: This will be posted for a minimum of 2 business days..." etc. Also remove "At UnitedHealth Group, our mission..." etc (mission statement) maybe considered boilerplate? It's about mission but could be considered part of About the role? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement is not explicitly listed as boilerplate, but it's generic. However it's substantive about organization's mission; could be considered part of About the role? The posting already has an introductory paragraph about Optum's mission. That is substantive. We can keep that as part of About the role maybe. But we already have About the role focusing on the role; we could incorporate the mission paragraph there. However we must not repeat job title as heading. It's okay to include mission description. We need to preserve ALL substantive information; we cannot remove mission statement unless it's considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Mission statement is not those. So we should keep it. Thus About the role could include both the introductory paragraph about Optum's mission and the role description. Let's craft About the role paragraph(s) maybe multiple

  tags. We'll produce:

  About the role

  Optum is a global organization that delivers care, aided by technology to help millions of people live