Software Engineer ASP.Net- Remote
Optum · Eden Prairie, MN · 4 wk ago
Engineering$73k–$130k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about Optum Tech, then description of role. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove things like "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" maybe part of requirements? It's a policy but maybe not needed. We need to preserve all substantive information.
We need to decide sections:
- About the role: could include introductory description: "As a Software Engineer within the MCDS team at Optum Technology, you will play a key role..." plus earlier paragraphs about Optum Tech mission. That seems like about the role/company.
- Responsibilities: list bullet points under "Primary Responsibilities". Those are specific.
- Requirements: maybe "Required Qualifications". That's required qualifications.
- Qualifications: maybe "Preferred Qualifications". Could be separate section "Preferred Qualifications" but we only have headings: Requirements, Qualifications, Skills. Could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills to something else? But we have Skills heading; we could put skills like experience with certain technologies under Skills. However we already have qualifications covering experience. Might be better to have Requirements (required), Qualifications (preferred), Skills (maybe technical skills). But we need to avoid filler. Let's see content:
Required Qualifications:
- 3+ years professional software engineering experience designing, developing, deploying applications
- 2+ years experience with object-oriented programming languages (e.g., ASP .Net Python, C#, TypeScript)
- 2+ years experience working with relational or non-relational databases (e.g., MySQL, PostgreSQL, MongoDB, or Oracle)
- 1+ years experience leveraging enterprise-approved AI tools or developer efficiency utilities to streamline software development tasks and workflows
- 1+ years experience with modern version control systems (e.g., Git) and CI/CD pipelines
Preferred Qualifications:
- Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field
- Experience supporting or maintaining legacy software applications while building next-generation enterprise solutions
- Experience building cloud-native applications on platforms such as Azure, AWS, or GCP
- Experience with microservices architecture, RESTful APIs, and containerization technologies (e.g., Docker, Kubernetes)
- Familiarity with agile software development methodologies and automated testing frameworks
- Proven solid problem-solving abilities and a proactive mindset toward adopting modern tools to optimize engineering productivity
Also there is a line: "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" - could be part of Requirements? It's a policy but maybe not needed. Might be considered boilerplate? It's not EEO but it's a policy. Might keep as a note under Requirements? But it's not a qualification. Could be omitted as it's not substantive? It's a condition. Might be considered minor metadata; we could fold into a short p. But we are told to drop minor metadata into a short p or drop it. This is a policy requirement; maybe we keep as a short p under Requirements? However it's not a qualification. Could be placed under Requirements as a note.
Pay: The posting includes: "The salary for this role will range from $72,800 - $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. So we should include a Pay section.
Benefits: "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 "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." So we have benefits info. So include Benefits section.
Schedule: The posting mentions: "In this 100% remote role, you will collaborate..." and "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." Also "You'll enjoy the flexibility to work remotely * from anywhere within the U.S." So schedule info: remote flexibility, but for certain locations office 4 days/week. So we have schedule info. So include Schedule section.
Skills: Could we extract skills like "object-oriented programming languages", "databases", "AI tools", "version control", "CI/CD", "cloud-native", "microservices", "RESTful APIs", "containerization", "agile", "automated testing". But those are already covered in qualifications. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Skills into Qualifications or Requirements. But we have headings: Requirements, Qualifications, Skills. We could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills to something like "Technical Skills" but we might not need separate Skills if content overlaps. However we must only include sections when posting has real specific content for it. If we put Skills but content is same as qualifications, it's still specific. But we might be duplicating. Better to have Requirements (required), Qualifications (preferred), and maybe Benefits, Pay, Schedule, About the role, Responsibilities. That's 6 sections. Skills could be omitted.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Check if any other sections like "Skills" not needed.
Now we need to format:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove things like "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" maybe part of requirements? It's a policy but maybe not needed. We need to preserve all substantive information.
We need to decide sections:
- About the role: could include introductory description: "As a Software Engineer within the MCDS team at Optum Technology, you will play a key role..." plus earlier paragraphs about Optum Tech mission. That seems like about the role/company.
- Responsibilities: list bullet points under "Primary Responsibilities". Those are specific.
- Requirements: maybe "Required Qualifications". That's required qualifications.
- Qualifications: maybe "Preferred Qualifications". Could be separate section "Preferred Qualifications" but we only have headings: Requirements, Qualifications, Skills. Could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills to something else? But we have Skills heading; we could put skills like experience with certain technologies under Skills. However we already have qualifications covering experience. Might be better to have Requirements (required), Qualifications (preferred), Skills (maybe technical skills). But we need to avoid filler. Let's see content:
Required Qualifications:
- 3+ years professional software engineering experience designing, developing, deploying applications
- 2+ years experience with object-oriented programming languages (e.g., ASP .Net Python, C#, TypeScript)
- 2+ years experience working with relational or non-relational databases (e.g., MySQL, PostgreSQL, MongoDB, or Oracle)
- 1+ years experience leveraging enterprise-approved AI tools or developer efficiency utilities to streamline software development tasks and workflows
- 1+ years experience with modern version control systems (e.g., Git) and CI/CD pipelines
Preferred Qualifications:
- Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field
- Experience supporting or maintaining legacy software applications while building next-generation enterprise solutions
- Experience building cloud-native applications on platforms such as Azure, AWS, or GCP
- Experience with microservices architecture, RESTful APIs, and containerization technologies (e.g., Docker, Kubernetes)
- Familiarity with agile software development methodologies and automated testing frameworks
- Proven solid problem-solving abilities and a proactive mindset toward adopting modern tools to optimize engineering productivity
Also there is a line: "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" - could be part of Requirements? It's a policy but maybe not needed. Might be considered boilerplate? It's not EEO but it's a policy. Might keep as a note under Requirements? But it's not a qualification. Could be omitted as it's not substantive? It's a condition. Might be considered minor metadata; we could fold into a short p. But we are told to drop minor metadata into a short p or drop it. This is a policy requirement; maybe we keep as a short p under Requirements? However it's not a qualification. Could be placed under Requirements as a note.
Pay: The posting includes: "The salary for this role will range from $72,800 - $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. So we should include a Pay section.
Benefits: "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 "No matter where or when you begin a career with us, you'll find a far-reaching choice of benefits and incentives." So we have benefits info. So include Benefits section.
Schedule: The posting mentions: "In this 100% remote role, you will collaborate..." and "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." Also "You'll enjoy the flexibility to work remotely * from anywhere within the U.S." So schedule info: remote flexibility, but for certain locations office 4 days/week. So we have schedule info. So include Schedule section.
Skills: Could we extract skills like "object-oriented programming languages", "databases", "AI tools", "version control", "CI/CD", "cloud-native", "microservices", "RESTful APIs", "containerization", "agile", "automated testing". But those are already covered in qualifications. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Skills into Qualifications or Requirements. But we have headings: Requirements, Qualifications, Skills. We could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills to something like "Technical Skills" but we might not need separate Skills if content overlaps. However we must only include sections when posting has real specific content for it. If we put Skills but content is same as qualifications, it's still specific. But we might be duplicating. Better to have Requirements (required), Qualifications (preferred), and maybe Benefits, Pay, Schedule, About the role, Responsibilities. That's 6 sections. Skills could be omitted.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
Check if any other sections like "Skills" not needed.
Now we need to format:
About the role
... combined intro paragraphs about Optum Tech and role description.
We must not repeat job title as heading. The job title is "Software Engineer". Not used. We need to preserve all substantive information. Let's extract the intro: "Optum Tech is a global leader in health care innovation. Our teams develop cutting-edge solutions that help people live healthier lives and help make the health system work better for everyone. From advanced data analytics and AI to cybersecurity, we use innovative approaches to solve some of health care's most complex challenges. Your contributions here have the potential to change lives. Ready to build the next breakthrough? Join us to start Caring. Connecting. Growing together. As a Software Engineer within the MCDS team at Optum Technology, you will play a key role in maintaining our legacy MCDS application while actively participating in the development of next-generation CCS 2.0 solutions. In this 100% remote role, you will collaborate with cross-functional engineering teams to deliver robust, scalable technology solutions that directly enhance healthcare systems. You will leverage enterprise-approved AI tools and modern software engineering techniques to optimize code quality, automate routine tasks, and drive continuous workflow efficiency and innovation. 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 a lot; we can keep as paragraph(s). Might split into two paragraphs for readability but okay. Now Responsibilities: list bullet points under- .
Responsibilities list:
- Design, develop, test, maintain, and deploy high-quality software solutions and applications aligned with business requirements
- Support and maintain legacy MCDS applications to ensure high availability, performance, and system stability
- Participate in the architectural design, feature development, and deployment of CCS 2.0 applications
- Use enterprise-approved AI tools to streamline workflows, automate tasks, and drive continuous improvement
- Evaluate emerging trends to inform solution design and strategic innovation
- Collaborate with product managers, system architects, and cross-functional engineering teams to refine application design and deliver resilient healthcare systems
- Participate in code reviews, technical documentation, and quality assurance efforts to ensure solutions adhere to enterprise security and architectural standards
- Troubleshoot, debug, and optimize application performance across full-scale production environments
Now Requirements (Required Qualifications):
- 3+ years of professional software engineering experience designing, developing, and deploying applications
- 2+ years of experience with object-oriented programming languages (e.g., ASP .Net Python, C#, TypeScript)
- 2+ years of experience working with relational or non-relational databases (e.g., MySQL, PostgreSQL, MongoDB, or Oracle)
- 1+ years of experience leveraging enterprise-approved AI tools or developer efficiency utilities to streamline software development tasks and workflows
- 1+ years of experience with modern version control systems (e.g., Git) and CI/CD pipelines
- All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy (maybe include as note)
Now Qualifications (Preferred Qualifications):
- Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field
- Experience supporting or maintaining legacy software applications while building next-generation enterprise solutions
- Experience building cloud-native applications on platforms such as Azure, AWS, or GCP
- Experience with microservices architecture, RESTful APIs, and containerization technologies (e.g., Docker, Kubernetes)
- Familiarity with agile software development methodologies and automated testing frameworks
- Proven solid problem-solving abilities and a proactive mindset toward adopting modern tools to optimize engineering productivity
Now Benefits:
- comprehensive benefits package
- incentive and recognition programs
- equity stock purchase
- 401k contribution
- far-reaching choice of benefits and incentives (maybe note)
We could phrase as
- ...
heading and then content. For About the role: maybe two paragraphs: first about Optum Tech, second about role specifics. Could combine. Let's craft:
About the role
Optum Tech is a global leader in health care innovation. Our teams develop cutting-edge solutions that help people live healthier lives and help make the health system work better for everyone. From advanced data analytics and AI to cybersecurity, we use innovative approaches to solve some of health care's most complex challenges. Your contributions here have the potential to change lives. Ready to build the next breakthrough? Join us