Software Engineer-Remote
Optum · San Francisco, CA · 3 wk ago
Engineering$73k–$130k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about Optum Tech, then description of role, responsibilities, qualifications, etc. We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. Let's parse. Content: - Intro: "Optum Tech is a global leader..." This is about the company and role overview. Could be "About the role". We'll include that as prose
. - Then: "This role supports the Identity Management rebuild initiative..." This is also role description. Could be part of About the role. - Then "Primary Responsibilities" heading in original. We'll create
Responsibilities
and list bullet points. - Then after responsibilities, there is a paragraph: "You'll be rewarded and recognized..." That's maybe benefits? Actually it's about rewards and recognition, could be part of Benefits or maybe not. We'll treat as Benefits? But there is later a Benefits section with details: "In addition to your salary, we offer benefits such as, a comprehensive benefits package, incentive and recognition programs, equity stock purchase and 401k contribution". So we can combine. - Then "Required Qualifications" heading -> we can map to Requirements or Qualifications. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where to put qualifications vs requirements. Usually "Required Qualifications" is qualifications. "Preferred Qualifications" also qualifications. "Required Qualifications" could be Requirements. But we have both Required and Preferred. We could put Required under Requirements, Preferred under Qualifications, or combine. Since we have both, we can have Requirements (required) and Qualifications (preferred). Or we could treat Requirements as required, Qualifications as preferred. We'll do that. - Then "AI Skills And Usage Expectations" could be Skills. - Then "Success Profile" maybe Skills? But we can incorporate into Skills. - Then "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" maybe Schedule? Not exactly. There's also remote work flexibility: "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/location info. So we can create Schedule section. - Pay: "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..." So we have Pay. - 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 earlier "You'll be rewarded and recognized..." We'll combine. - Skills: Could include AI Skills, Success Profile, maybe also "Experience with event-driven architecture..." etc. Those are under Preferred Qualifications. But we already used Preferred Qualifications as Qualifications. So Skills could be AI Skills and Usage Expectations + Success Profile. We'll combine. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the EEO statement, drug free workplace, mission statements, etc. Also remove "Application Deadline: ..." etc. Also remove "At UnitedHealth Group, our mission is..." etc. Also remove "We comply with all minimum wage laws". Also remove "UnitedHealth Group is an Equal Employment Opportunity employer..." etc. Also remove "UnitedHealth Group is a drug - free workplace." etc. We need to preserve all substantive information: responsibilities, required qualifications, preferred qualifications, pay, benefits, schedule, etc. Let's extract substantive content: Intro/about 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 to start Caring. Connecting. Growing together. This role supports the Identity Management rebuild initiative and ongoing support for the existing application. The Software Engineer will design, build, test, deploy, and operate scalable APIs, microservices, and data-intensive backend services. The role retains a solid foundation in Python and PySpark while expanding into API development, cloud-native application engineering, automation, observability, and secure software delivery." That's about role. Responsibilities (list): - Design, develop, test, deploy, and support backend applications, RESTful APIs, and microservices for the Identity Management rebuild and existing application - Build production-quality services using Python and modern API frameworks - Develop data-intensive application components and distributed processing workflows using PySpark and Azure Databricks and Azure Data Factory - Define clear API contracts, request and response models, error-handling standards, versioning strategies, and service documentation using OpenAPI or Swagger - Implement resilient microservice patterns, including service-to-service communication, retries, timeouts, idempotency, asynchronous processing, and graceful failure handling - Create automated unit, integration, API, regression, and performance tests; integrate quality checks into CI/CD pipelines - Implement application logging, metrics, tracing, alerting, and dashboards to improve observability, incident response, and operational reliability - Apply secure coding practices, authentication and authorization controls, secrets management, encryption, and privacy-by-design principles - Troubleshoot production issues, perform root cause analysis, improve service performance, and contribute to scalability and cost optimization - Use Git-based engineering practices, code reviews, branching strategies, automated builds, release controls, and infrastructure-aware deployment workflows - Use enterprise-approved AI tools and custom agents to accelerate coding, testing, documentation, debugging, monitoring, and operational support - Collaborate with product, data engineering, platform engineering, architecture, security, and application teams to deliver priorities and communicate risks, dependencies, and progress Rewards/recognition paragraph: "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." This could go under Benefits or maybe under a generic "Rewards". But we have Benefits section; we can include this as part of Benefits. Required Qualifications (list): - 5+ years of hands-on software engineering experience building and operating enterprise applications, backend services, APIs, or microservices - 5+ years of hands-on experience with Python, including object-oriented programming, modular design, exception handling, packaging, automation, and maintainable coding practices - 3+ years of hands-on experience developing RESTful APIs and working with API specifications, validation, authentication, versioning, and documentation - 3+ years of hands-on experience with PySpark for distributed processing, transformation, data validation, and performance tuning - 2+ years of working experience with Azure Databricks or similar distributed data platforms for data-intensive application use cases - 2+ years of working experience with relational and NoSQL databases, data modeling, SQL, transaction patterns, and application-level data access - Experience designing and building microservices, including service decomposition, interface design, scalability, resilience, and operational support - Experience with automated testing frameworks such as pytest and unit, integration, API, and regression testing practices - Git experience, including pull requests, code reviews, branching strategies, CI/CD fundamentals, release management, and production support - Experience with Docker and a working understanding of Kubernetes or managed container platforms - Experience implementing logging, monitoring, alerting, metrics, and distributed tracing for production services - Understanding of software design principles, common design patterns, clean code, code quality, and maintainable architecture - Basic working understanding of cloud security, identity and access management, data privacy, governance, and enterprise compliance concepts - Proven good problem-solving and root cause analysis skills, with the ability to troubleshoot across application, API, data, and cloud layers - Proven good communication and collaboration skills, with the ability to explain technical decisions, risks, dependencies, and delivery progress clearly Preferred Qualifications (list): - Experience with event-driven architecture and messaging technologies such as Kafka, Azure Event Hubs, Azure Service Bus, or comparable platforms - Experience supporting performance testing, capacity planning, secure software development lifecycle practices, and cloud cost optimization - Experience building identity management, identity resolution, consumer profile, member/customer identity, or entity-resolution applications - Hands-on experience with Azure Data Factory and data pipeline orchestration - Hands-on experience building or supporting custom AI agents for coding, testing, documentation, validation, monitoring, incident triage, or workflow automation - Healthcare, insurance, consumer profile, or enterprise identity data experience - Knowledge of caching, API gateways, load balancing, rate limiting, asynchronous programming, and high-availability design AI Skills And Usage Expectations (list): - Demonstrate baseline proficiency with enterprise-approved AI tools such as GitHub Copilot, Microsoft 365 Copilot, Databricks Genie, and other approved GenAI platforms, where applicable - Apply AI tools responsibly to improve coding, code review, test creation, technical documentation, debugging, analysis, monitoring, and delivery quality - Use or support custom agents for software development, automated testing, API validation, failure detection, incident triage, runbook execution, and operational reporting - Follow enterprise guidance for responsible AI use, data protection, human review, security, and software quality Success Profile (list? Actually it's a paragraph with bullet-like statements): - Balances solid software engineering discipline with practical data engineering knowledge - Builds secure, observable, maintainable services that can be supported reliably in production - Works effectively across application, data, platform, security, and business teams - Continuously improves engineering productivity through automation, reusable components, and responsible use of AI-assisted development tools We could treat Success Profile as Skills. Pay: - "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)." - "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." (maybe we can keep but it's generic; but it's substantive? It's a statement about compliance; we could keep but it's not specific. Might be considered boilerplate? It's a legal statement; but it's about pay. Might keep but it's generic. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal statement about minimum wage compliance; could be considered boilerplate. Safer to drop it. Benefits: we already have benefits paragraph. Schedule/Location: - "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." - Also "All employees working remotely will be required to adhere to UnitedHealth Group's Telecommuter Policy" (maybe schedule). We'll include that. We need to output only HTML fragment, no markdown fences. We'll structure:About the role
... (intro paragraph)
Responsibilities
- ... ...