.NET Azure Full Stack Developer

We need to output HTML fragment with sections: headings

for sections present: About the role? The job description includes "Job Summary" etc. We need to map sections: maybe "About the role" (Job Summary), "Responsibilities", "Requirements" (Technical/Functional Skills, Mandatory Skills, Preferred Skills), "Benefits", "Pay". Also maybe "Skills" but we can combine. Must not repeat job title. Must not include boilerplate. Must preserve all substantive info. Must not include sections with placeholder text. We have Salary Range: $80,000 - $100,000 a year -> Pay section. Benefits: TCS Employee Benefits Summary list. Responsibilities: Key Responsibilities with subpoints. Requirements: Technical/Functional Skills list, Mandatory Skills, Preferred Skills. Also maybe "Qualifications" but we can treat as Requirements. We need to use

• for any list of duties/requirements/benefits. For prose use

  . We must not include duplicated lines. Remove cookie/navigation/legal/EEO etc. Not present. We need to ensure we include all substantive info: Job Summary paragraph, Responsibilities bullet points, Technical/Functional Skills list, Mandatory Skills list, Preferred Skills list, Salary Range, Benefits list. We must not invent or summarize away detail. Keep details. Let's extract content. Job Summary paragraph: "We are seeking a highly skilled Application & Infrastructure Support Engineer to support and maintain critical enterprise applications and infrastructure within a secure Department of Defense environment. The ideal candidate will possess strong expertise in Windows Server administration, vulnerability management, IIS, SQL Server, and application support, along with automation and development skills using PowerShell, .NET, and C#. This role requires hands-on experience managing secure production environments, applying system updates, troubleshooting complex technical issues, and supporting vulnerability remediation initiatives using Nessus Manager." That's prose. Key Responsibilities: list with headings: Vulnerability Management & Security, Infrastructure Administration & Support, Web & Application Support, Database Administration & Support, Automation & Development, Generic Managerial Skills, If any (maybe ignore as no content). Actually "Generic Managerial Skills, If any" seems placeholder; we should not include if no specific content. There's no bullet under it. So skip. We need to preserve each bullet under each heading. Let's extract bullets: Vulnerability Management & Security: - Administer and support Nessus Manager On-Premises subscriptions and vulnerability scanning activities. - Review vulnerability assessment results and coordinate remediation activities. - Work closely with security teams to ensure compliance with DoD security requirements. - Monitor system security posture and support audit and compliance initiatives. - Perform vulnerability validation and reporting. Infrastructure Administration & Support: - Install, configure, maintain, and troubleshoot Windows Server 2012 R2 and newer versions. - Apply security patches, OS updates, and system hardening configurations. - Monitor server health, performance, and availability. - Troubleshoot infrastructure-related incidents and perform root cause analysis. - Support backup, recovery, and disaster recovery processes. Web & Application Support: - Administer and troubleshoot Microsoft IIS (Internet Information Services). - Support enterprise applications deployed on Windows environments. - Investigate application failures, performance bottlenecks, and connectivity issues. - Perform application deployments, upgrades, and maintenance activities. - Ensure high availability and reliability of business-critical systems. Database Administration & Support: - Support and troubleshoot Microsoft SQL Server environments. - Execute SQL queries, stored procedures, and database maintenance activities. - Analyze database-related issues and optimize performance where required. - Participate in database patching and upgrade activities. Automation & Development: - Develop automation scripts using PowerShell to streamline operational processes. - Build and maintain tools/utilities using .NET and C#. - Support application enhancements and bug fixes. - Create monitoring and reporting solutions to improve operational efficiency. - Participate in scripting and automation initiatives for vulnerability remediation and system administration tasks. Technical/Functional Skills (Must Have): list: - ASP.NET 4.5 - C# - Windows Powershell - Microsoft SQL Server 2019 - Nessus Manager But also later Mandatory Skills list includes many items: Nessus Manager (On-Premises Subscription), Windows Server 2012 R2 and later versions, Microsoft IIS, Microsoft SQL Server, PowerShell Scripting, .NET Framework / .NET, C# Programming, Application Support & Troubleshooting, Security Patch Management, Incident Management & Root Cause Analysis. Preferred Skills list: Active or previously held Security Clearance, DISA STIG compliance knowledge, Windows Server Hardening, Active Directory Administration, Azure DevOps, ITIL Processes, Performance Monitoring Tools, Automation Framework Development (note duplicate DISA STIG compliance knowledge appears twice but we keep once). We need to preserve all substantive info; we should not duplicate. We'll combine Mandatory and Preferred under Requirements maybe separate subheadings? But spec says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (Job Summary), Responsibilities, Requirements (maybe combine Technical/Functional Skills, Mandatory Skills, Preferred Skills), Benefits, Pay. We must not create sections with filler. All have content. We need to output only HTML fragment. Let's craft:

  About the role

  We are seeking a highly skilled Application & Infrastructure Support Engineer to support and maintain critical enterprise applications and infrastructure within a secure Department of Defense environment. The ideal candidate will possess strong expertise in Windows Server administration, vulnerability management, IIS, SQL Server, and application support, along with automation and development skills using PowerShell, .NET, and C#. This role requires hands-on experience managing secure production environments, applying system updates, troubleshooting complex technical issues, and supporting vulnerability remediation initiatives using Nessus Manager.

  Responsibilities

  • Vulnerability Management & Security
    • Administer and support Nessus Manager On-Premises subscriptions and vulnerability scanning activities.
    • Review vulnerability assessment results and coordinate remediation activities.
    • Work closely with security teams to ensure compliance with DoD security requirements.
    • Monitor system security posture and support audit and compliance initiatives.
    • Perform vulnerability validation and reporting.
  • Infrastructure Administration & Support
    • Install, configure, maintain, and troubleshoot Windows Server 2012 R2 and newer versions.
    • Apply security patches, OS updates, and system hardening configurations.
    • Monitor server health, performance, and availability.
    • Troubleshoot infrastructure-related incidents and perform root cause analysis.
    • Support backup, recovery, and disaster recovery processes.
  • Web & Application Support
    • Administer and troubleshoot Microsoft IIS (Internet Information Services).
    • Support enterprise applications deployed on Windows environments.
    • Investigate application failures, performance bottlenecks, and connectivity issues.
    • Perform application deployments, upgrades, and maintenance activities.
    • Ensure high availability and reliability of business-critical systems.
  • Database Administration & Support
    • Support and troubleshoot Microsoft SQL Server environments.
    • Execute SQL queries, stored procedures, and database maintenance activities.
    • Analyze database-related issues and optimize performance where required.
    • Participate in database patching and upgrade activities.
  • Automation & Development
    • Develop automation scripts using PowerShell to streamline operational processes.
    • Build and maintain tools/utilities using .NET and C#.
    • Support application enhancements and bug fixes.
    • Create monitoring and reporting solutions to improve operational efficiency.
    • Participate in scripting and automation initiatives for vulnerability remediation and system administration tasks.
  But note spec: Use
  • for any list of duties/requirements/benefits, and

    for prose. It didn't forbid nested lists? Probably okay but we could flatten. However we have headings inside li; maybe better to keep sections for each responsibility area as

    ? But spec only mentions h3 for section headings. Could use

    for each responsibility area? But that would be many sections. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those specific headings. So we should not use other headings. So we need to represent responsibilities as a flat list without subheadings? But we need to preserve the grouping info. Could we keep the grouping as part of the li text? Eg: "Vulnerability Management & Security: Administer and support Nessus Manager..." That preserves info. That seems acceptable. Thus we can produce a single

    with each responsibility as a li, each li containing the heading bolded then the bullet points? But we need to keep each bullet as separate li? The spec says use
    • for any list of duties/requirements/benefits. So each duty should be a li. If we combine multiple duties into one li, we lose list granularity. Better to keep each duty as separate li, but we need to preserve the category label. Could embed the category as part of the li text: e.g., "
    • Vulnerability Management & Security: Administer and support Nessus Manager On-Premises subscriptions and vulnerability scanning activities.
    " Then next li for next bullet under same category. That repeats the category label each time, but that's okay. Alternatively we could have a
    for each category with a preceding

    describing category, but that adds extra elements not prohibited. The spec didn't forbid extra elements, just said use

    • for any list and

      for prose. So we could have a

      for category heading (though not h3) and then a

      for its bullets. That seems fine. Thus we can do:

      Responsibilities

      Vulnerability Management & Security

      • Administer and support Nessus Manager On-Premises subscriptions and vulnerability scanning activities.
      • Review vulnerability assessment results and coordinate remediation activities.
      • Work closely with security teams to ensure compliance with DoD security requirements.
      • Monitor system security posture and support audit and compliance initiatives.
      • Perform vulnerability validation and reporting.

      Infrastructure Administration & Support

      ...
      ... etc. That respects using

      for prose (category headings) and

      • for list. Similarly for Requirements: we can have subheadings as

        then lists. Let's extract Mandatory Skills list: - Nessus Manager (On-Premises Subscription) - Windows Server 2012 R2 and later versions - Microsoft IIS - Microsoft SQL Server - PowerShell Scripting - .NET Framework / .NET - C# Programming - Application Support & Troubleshooting - Security Patch Management - Incident Management & Root Cause Analysis Preferred Skills list: - Active or previously held Security Clearance - DISA STIG compliance knowledge - Windows Server Hardening - Active Directory Administration - Azure DevOps - ITIL Processes - Performance Monitoring Tools - Automation Framework Development Also Technical/Functional Skills (Must Have) list: ASP.NET 4.5; C#; Windows Powershell; Microsoft SQL Server 2019; Nessus Manager We could combine all into Requirements section with subheadings: Technical/Functional Skills, Mandatory Skills, Preferred Skills. We'll output: