In-Person Interview || Full Stack .NET Developer || Des Moines, IA 50309

We need to output HTML fragment with sections: About the role (maybe from Position Overview), Responsibilities, Requirements (maybe combine Required Qualifications and Required / Desired Skills), Skills (maybe Preferred Qualifications), Benefits (none), Pay (none), Schedule (none). We must only include sections that have real specific content. No Pay/Schedule/Benefits unless present. The posting includes location, duration, interview type, interview dates. Those are metadata; we can fold into a short

maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

with location, duration, interview type, interview dates. We must not repeat the job title as a heading. The page already shows it, so we don't add

Senior .NET/SQL Full-Stack Developer. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections to include based on content. We have Position Overview (About the role). We have Key Responsibilities. We have Required Qualifications (maybe Requirements). We have Preferred Qualifications (maybe Skills). Also there is "Required / Desired Skills" list with many items; that could be Skills. Also "Vendor Submission Guidance Required Experience" etc. But we need to preserve all substantive info. We must not create sections with filler like "commensurate with experience". Not relevant. We need to output only HTML fragment, no markdown fences. Let's craft:

Location: 200 E Grand Avenue, Des Moines, IA 50309. Estimated duration: 10/19/2026 – 06/30/2027 (possible extension). Interview type: Web Cam or In‑Person. Interview dates: September 21‑25.

Then

About the role

with paragraph(s) from Position Overview. Then

Responsibilities

with

• each responsibility. Then

  Requirements

  maybe combine Required Qualifications and Required / Desired Skills? But we might separate Requirements (hard requirements) and Skills (preferred). The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one section? But we have headings for Requirements and Qualifications separate. We could use Requirements for mandatory qualifications, and Skills for preferred qualifications. Let's do that. Requirements: list bullet points from Required Qualifications (Bachelor's degree, 5+ years experience with listed items). Also include the "Required / Desired Skills" list which seems to repeat many required items; but we can incorporate them as part of Requirements (they are required). However to avoid duplication, we can just list the required qualifications; the Required / Desired Skills list is largely same but we can note it's redundant; but we must preserve ALL substantive information; we cannot drop details unless they are duplicate. The list includes many items like "Bachelor s degree in Computer Science, Information Technology, or related field." (duplicate), "Required Experience with C#, .NET, and ASP.NET." (duplicate), "Required 5 Years Expert-level proficiency in SQL Server and performance optimization" (duplicate), etc. We could include them but risk duplication. The instruction: remove duplicated lines. So we should deduplicate. So we can combine the required qualifications and the required/desired skills into a single list without duplicates. Thus Requirements section bullet list: Bachelor's degree in Computer Science, Information Technology, or related field (or equivalent professional experience). 5+ years of experience developing applications using C#.NET Framework, ASP.NET / ASP.NET Core. Advanced SQL Server experience including database design, stored procedures, query optimization, performance tuning. Experience creating and supporting SSRS reports. Experience developing and consuming REST and/or SOAP services. Experience working with Azure DevOps. Experience supporting enterprise production applications. Experience working across multiple layers of an application (front end, middleware, backend). Knowledge of accessibility standards and accessibility remediation practices. (Also maybe "Strong knowledge of WCAG 2.1 AA accessibility standards.") Also "Experience working within HHS or a comparable state or federal health agency." (from Required / Desired Skills). Also "Experience with DOM processes and state IT frameworks." (Highly desired but maybe not required). But we need to separate required vs preferred. The Required / Desired Skills list includes both required and highly desired items. It says "Required 5 Years ..." for many, then "Highly desired ..." for others. We need to parse. Let's extract Required items from that list: - Bachelor s degree in Computer Science, Information Technology, or related field. (Required) - Required Experience with C#, .NET, and ASP.NET. (Required) - Required 5 Years Expert-level proficiency in SQL Server and performance optimization (Required) - Required 5 Years Experience developing and consuming RESTful or SOAP APIs. (Required) - Required 5 Years Demonstrated experience with Azure DevOps for project management and pipelines. (Required) - Required 5 Years Strong knowledge of WCAG 2.1 AA accessibility standards. (Required) - Required 5 Years Experience working within HHS or a comparable state or federal health agency. (Required) - Required 5 Years Advanced knowledge of the .NET ecosystem. (Required) - Required 5 Years Familiarity with USWDS design standards (Required? It says "Required 5 Years Familiarity with USWDS design standards" Actually the line: "Required 5 Years Familiarity with USWDS design standards" appears under Required / Desired Skills? Let's check: In the text: "Required 5 Years Familiarity with USWDS design standards Highly desired Experience With GitHub Or Angular. Required 5 Years". Actually the snippet: "Required 5 Years Familiarity with USWDS design standards Highly desired Experience With GitHub Or Angular. Required 5 Years". It seems "Required 5 Years Familiarity with USWDS design standards" is required, then "Highly desired Experience With GitHub Or Angular." So we treat USWDS as required. Thus required items also include: Familiarity with USWDS design standards. Now highly desired items from that list: Experience with DOM processes and state IT frameworks. Proficiency with HTML, CSS, SASS. Experience Using AWS Services. Experience With GitHub Or Angular. Also from Preferred Qualifications: Experience supporting government, healthcare, or HHS systems (already covered as required? Actually required includes HHS experience). Experience maintaining and modernizing legacy applications. Experience with HTML, CSS, and JavaScript. Experience with Angular. Experience with GitHub. Experience with AWS services. Accessibility certification or formal accessibility training. Thus we can create Skills section for preferred qualifications (nice to have). We'll include those. Now Responsibilities: list from Key Responsibilities. Now About the role: from Position Overview paragraph. Now we need to ensure we don't create sections with filler. We'll have About the role, Responsibilities, Requirements, Skills. No Benefits, Pay, Schedule. Now output HTML fragment. Let's craft:

  Location: 200 E Grand Avenue, Des Moines, IA 50309. Estimated duration: 10/19/2026 – 06/30/2027 (possible extension). Interview type: Web Cam or In‑Person. Interview dates: September 21‑25.

  About the role

  This is a hands-on development role responsible for supporting applications across the full technology stack, including front-end components, middleware integrations, backend services, SQL Server databases, and SSRS reporting. The ideal candidate will be comfortable working in existing enterprise applications, troubleshooting production issues, implementing enhancements, and modernizing legacy solutions. Candidates should have strong .NET development experience, advanced SQL Server skills, and the ability to work across multiple layers of an application.

  Responsibilities

  • Develop, enhance, and support enterprise applications using C# and ASP.NET/.NET technologies.
  • Design, build, and maintain backend services, APIs, and middleware integrations.
  • Create, modify, and troubleshoot SSRS reports supporting business operations.
  • Design, optimize, and maintain SQL Server databases, stored procedures, and queries.
  • Analyze and resolve complex production issues across multiple applications and environments.
  • Support front-end application updates and enhancements as needed.
  • Modernize legacy applications and reduce technical debt.
  • Manage source control, deployments, and CI/CD processes using Azure DevOps.
  • Ensure applications meet established accessibility requirements and compliance standards.
  • Collaborate with business stakeholders, analysts, QA teams, and technical staff to deliver reliable and secure solutions.

  Requirements

  • Bachelor's degree in Computer Science, Information Technology, or related field (or equivalent professional experience).
  • 5+ years of experience developing applications using C#.NET Framework, ASP.NET / ASP.NET Core.
  • Advanced SQL Server experience including database design, stored procedures, query optimization, and performance tuning.
  • Experience creating and supporting SSRS reports.
  • Experience developing and consuming REST and/or SOAP services.
  • Experience working with Azure DevOps.
  • Experience supporting enterprise production applications.
  • Experience working across multiple layers of an application (front end, middleware, backend).
  • Strong knowledge of WCAG 2.1 AA accessibility standards and accessibility remediation practices.
  • Experience working within HHS or a comparable state or federal health agency.
  • Advanced knowledge of the .NET ecosystem.
  • Familiarity with USWDS design standards.

  Skills

  • Experience supporting government, healthcare, or HHS systems.
  • Experience maintaining and modernizing legacy applications.
  • Proficiency with HTML, CSS, and JavaScript.
  • Experience with Angular.
  • Experience with GitHub.
  • Experience with AWS services.
  • Accessibility certification or formal accessibility training.
  • Experience with DOM processes and state IT frameworks.
  • Proficiency with HTML, CSS, SASS.
  Check for duplication: "Experience supporting government, healthcare, or HHS systems" appears also in Requirements? Actually we have HHS experience as required; but it's okay to have overlap? Might be considered duplicate. The instruction: remove duplicated lines. So we should avoid duplicating the same exact line. In Requirements we have "Experience working within HHS or a comparable state or federal health agency." In Skills we have "Experience supporting government, healthcare, or HHS systems." They are similar but not identical; still could be considered duplicate content. To be safe, we could remove that from Skills, as it's already covered as required. But the Preferred Qualifications includes "Experience supporting government, healthcare, or HHS systems." Since we already have HHS experience as required, we could keep it but note it's redundant. The instruction says remove duplicated lines. So better to remove that line from Skills. Also "Experience maintaining and modernizing legacy applications" appears in Preferred Qualifications; not in Requirements, so keep. "Proficiency with HTML, CSS, and JavaScript" appears in Preferred Qualifications; not in Requirements (though we have knowledge of accessibility standards, not HTML/CSS/JS). Keep. "Experience with Angular" appears in Preferred Qualifications; not in Requirements. "Experience with GitHub" appears in Preferred Qualifications; not in Requirements. "Experience with AWS services" appears in Preferred Qualifications; not in Requirements. "Accessibility certification or formal accessibility training." appears in Preferred Qualifications; not in Requirements (we have knowledge of WCAG). Keep. "Experience with DOM processes and state IT frameworks." appears in Required / Desired Skills