.Net Software Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "A Little About Us", "A Little About You", "Position Overview", "What You Will Do", "What You Will Bring To Zelis", "What Success Looks Like", "Location and Workplace Flexibility", "Base Salary Range", "Benefits". Also "Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future." That's a note but maybe we can include as a short paragraph? It's not a heading; we can include as a paragraph after location maybe. Also "Equal Employment Opportunity", "Accessibility Support", "Disclaimer" are boilerplate to remove. Also "At Zelis we Get Stuff Done..." is intro but we can include as a paragraph under maybe "About the role"? Actually we need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The instructions: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should map content to those headings. However we need to decide which sections are present. We have: - About the role: could be Position Overview + maybe A Little About Us? But "About the role" likely corresponds to Position Overview. We'll put Position Overview content under

About the role

. - Responsibilities: "What You Will Do" is responsibilities. - Requirements: "What You Will Bring To Zelis" includes required qualifications (3-5 years experience, etc). That's requirements. - Qualifications: maybe "Preferred Qualifications" separate? Could be Qualifications section for required? But we already used Requirements for required. Qualifications could be preferred qualifications. We'll put Preferred Qualifications under

Qualifications

. - Skills: maybe we can extract skills from responsibilities? But we could also put a Skills section summarizing technical skills? However we should only include if posting has real specific content. The posting lists many skills in responsibilities and requirements. Could create a Skills section but might be redundant. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine skills into Responsibilities/Requirements. But we need to follow the heading list: they gave examples but not mandatory to use all. We should include sections only when posting has real specific content. So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule not present (no schedule specifics). So we omit Schedule. Benefits: posting mentions benefits package: 401k, flexible PTO, holidays, parental leaves, life/disability insurance, health benefits medical dental vision prescription. So we can include Benefits. Pay: Base Salary Range $101,600 - $139,700. So include Pay. We also have Location and Workplace Flexibility: could be included as a paragraph maybe under About the role? Or we could add a separate section like "Location" but not in list. Since not in allowed headings, we could just include as a paragraph after About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. So we can incorporate location info into About the role paragraph or as a separate

after About the role but before Responsibilities. That's fine. Also note about visa sponsorship: we can include as a short paragraph maybe after Pay or Benefits. It's substantive info. We'll include as a

after Benefits maybe. We must remove boilerplate: EEO, Accessibility Support, Disclaimer, also the introductory "At Zelis, we Get Stuff Done. So, let’s get to it!" maybe we can keep as part of About the role? It's fluff but maybe we keep as part of About the role? It's not boilerplate; it's introductory marketing. Could keep as a paragraph. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details from each section. Let's extract content: **About the role (Position Overview)**: "The .Net Software Engineer is responsible for designing, developing, testing, and maintaining high-quality software solutions that support business and customer needs. This role works across the application stack, contributing to backend development using C#/.NET and modern web experiences using technologies such as Blazor, JavaScript, HTML, jQuery. The ideal candidate has 3–5 years of professional software development experience, strong problem-solving skills, and experience working within collaborative Agile development teams. The engineer will participate throughout the software development lifecycle, including solution design, development, code reviews, testing, deployment, troubleshooting, and continuous improvement. Experience with Azure or AWS cloud technologies is preferred, and knowledge of the healthcare industry is a plus." We should keep that as prose under About the role. **Responsibilities (What You Will Do)** list many bullet-like sentences. We need to convert to

• . Each sentence is a duty. Let's list them: - Design, develop, test, deploy, and maintain scalable, reliable, and secure software applications using C# and .NET. - Develop and maintain RESTful APIs, backend services and other enterprise systems - Develop responsive web applications and user interfaces using Blazor, JavaScript, HTML, jQuery. - Develop efficient and maintainable SQL queries, stored procedures, and database solutions. - Translate business and technical requirements into well-designed, maintainable software solutions. - Write clean, efficient, reusable, and well-tested code following established engineering standards and development practices. - Develop and maintain unit and integration tests to ensure application quality and reliability. - Participate in application design and technical discussions, contributing ideas and evaluating potential solutions and tradeoffs. - Troubleshoot application issues, identify root causes, and implement effective solutions. - Participate in peer code reviews and provide constructive feedback that improves code quality, maintainability, and team knowledge. - Use Git and established source-control practices to manage code changes and collaborate effectively with other engineers. - Contribute to applications and services deployed in cloud environments such as Microsoft Azure or AWS. - Leverage AI-assisted development tools responsibly to improve software development, problem-solving, testing, documentation, and engineering productivity. - Collaborate with software engineers, product owners, quality engineers, architects, and other cross-functional partners to deliver solutions. - Participate in Agile development activities, including backlog refinement, estimation, sprint planning, daily stand-ups, and retrospectives. - Support continuous improvement by identifying opportunities to simplify development processes, improve application performance, reduce technical debt, and strengthen software quality. - Stay current with evolving development technologies and apply new approaches when they improve engineering effectiveness or customer outcomes. - Take ownership of assigned work, communicate progress and risks proactively, and consistently deliver high-quality results. We'll put each as
• . **Requirements (What You Will Bring To Zelis)** list: - 3–5 years of professional software development experience. - Hands-on development experience with C# and .NET. - Experience developing and consuming APIs and integrating applications with backend services. - Experience developing web applications using Blazor, JavaScript, HTML, and jQuery. - Strong knowledge of SQL and relational databases. - Experience using Git for source control and collaborative software development. - Experience with unit testing and integration testing as part of the software development lifecycle. - Strong understanding of object-oriented programming, software design principles, debugging, and application development practices. - Familiarity with AI-assisted software development tools and an understanding of how AI can be used responsibly to improve development workflows and productivity. - Strong analytical, troubleshooting, and problem-solving skills. - Ability to work effectively within a collaborative, cross-functional software development team. - Strong written and verbal communication skills. We'll put as
  • . **Qualifications (Preferred Qualifications)** list: - Experience developing or supporting applications in Microsoft Azure or AWS. - Experience with cloud services such as Azure App Services, Azure Functions, Azure Storage, AWS Lambda, Amazon S3, or similar technologies. - Experience with a modern JavaScript frontend framework or library such as Angular or React. - Knowledge of healthcare technology, healthcare data, healthcare operations, or the broader healthcare industry. - Experience working in Agile/Scrum software development environments. - Experience with automated testing, CI/CD practices, and modern software delivery approaches. - Experience working with enterprise-scale applications and distributed systems. - Experience applying AI capabilities or AI-assisted tools within software engineering workflows is a plus. We'll put as
    • . **Benefits**: The posting says: "Zelis’ full-time associates are eligible for a highly competitive benefits package as well, which demonstrates our commitment to our employees’ health, well-being, and financial protection. The US-based benefits include a 401k plan with employer match, flexible paid time off, holidays, parental leaves, life and disability insurance, and health benefits including medical, dental, vision, and prescription drug coverage." We'll put as
      • items. **Pay**: Base Salary Range $101,600.00 - $139,700.00. Also note about base pay being part of Total Rewards etc. We'll include that prose. We also have note about visa sponsorship: "Please note at this time we are unable to proceed with candidates who require visa sponsorship now or in the future." We'll include as a

        after Benefits maybe. Location and Workplace Flexibility: we can incorporate into About the role paragraph or as a separate

        after About the role. Let's add a short paragraph after About the role: "Zelis is headquartered in the U.S., with multiple locations across the country and in Hyderabad, India. All employee work locations are based on the needs of the position and are determined by the Leadership team. In-office work and activities vary based on work and team objectives in accordance with Company policies. While location expectations vary by role, candidates within approximately 50 miles of a U.S. office are generally preferred to support collaboration when needed. Our hybrid approach is flexible, and in-office presence is guided by team and business needs rather than a fixed weekly schedule." We'll keep that as a

        . Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

        About the role

        ... (position overview + location paragraph? maybe separate)

        But we have two paragraphs: position overview and location. Could combine into one

        with two sentences? Better to keep separate

        for each. Thus:

        About the role

        The .Net Software Engineer is responsible for designing, developing, testing, and maintaining high-quality software solutions that support business and customer needs. This role works across the application stack, contributing to backend development using C#/.NET and modern web experiences using technologies such as Blazor, JavaScript, HTML, jQuery. The ideal candidate has 3–5 years of professional software development experience, strong problem-solving skills, and experience working within collaborative Agile development teams. The engineer will participate throughout the software development lifecycle, including solution design, development, code reviews, testing, deployment, troubleshooting, and continuous improvement. Experience with Azure or AWS cloud technologies is preferred, and knowledge of the healthcare industry is a plus.

        Zelis is headquartered in the U.S., with multiple locations across the country and in Hyderabad, India. All employee work locations are based on the needs of the position and are determined by the Leadership team. In-office work and activities vary based on work and team objectives in accordance with Company policies. While location expectations vary by role, candidates within approximately 50 miles of a U.S. office are generally preferred to support collaboration when needed. Our hybrid approach is flexible, and in-office presence is guided by team and business needs rather than a fixed weekly schedule.

        Then Responsibilities:

        Responsibilities

        • Design, develop, test, deploy, and