Software Engineer (.NET) — Enterprise/Government Systems Offline

The role

We’re building an internal engineering team to take ownership of a large, mission-critical public sector / enterprise platform currently operated by an external vendor. The system is live and has real operational constraints: reliability, auditability, controlled releases, and security gates are part of day-to-day work.

Technically, it’s a hybrid:

• Legacy areas: ASP.NET Framework 4.8 / WCF
  
   
• Modern services: .NET 8 (LTS)
  
   
• Releases: still partly manual today (with approvals), moving toward CI/CD
  
   

We’re also transitioning to a CIS-based team, so documentation isn’t perfect everywhere. We’re looking for developers who can still move fast safely: read code, trace behavior, validate assumptions, and leave clear notes for the next person.

This role is for a developer first—but someone who also cares about how software ships and runs.

What you’ll do

• Build and maintain backend services in C# / .NET 8 (LTS).
  
   
• Work in legacy code where needed (ASP.NET 4.8 / WCF) and help carve out cleaner services over time.
  
   
• Contribute to safer delivery:
  
   
  • help replace manual release steps with repeatable CI/CD
    
     
  • improve deployment traceability (logs, approvals, rollbacks)
    
     
  • tighten “definition of done” around testing and release readiness
    
     
• Build or integrate with supporting services (some are in Python) and internal tooling/scripts.
  
   
• Work with modern UI codebases (React and/or Angular)—you don’t have to be a UI specialist, but you should be comfortable contributing when needed.
  
   
• Write and tune queries across SQL Server and MySQL.
  
   
• Operate in a strict SDLC:
  
   
  • PR-based workflow, branch protection
    
     
  • peer reviews
    
     
  • mandatory security scanning (SAST) before release
    
     

What we’re looking for

• 3–6 years of professional software engineering experience (or equivalent impact).
  
   
• Strong C# / .NET fundamentals and comfort working in large codebases.
  
   
• Experience in enterprise or government-style environments: regulated systems, high-availability, “no surprises” releases, audit trails, change control, etc.
  
   
• Practical exposure to CI/CD and environments (you’ve worked with pipelines, not necessarily built everything from scratch).
  
   
• Comfort working across a broader stack:
  
   
  • Python (reading/writing scripts, small services, integrations)
    
     
  • React/Angular (basic-to-solid contributions)
    
     
• Strong debugging instincts: you can investigate issues without perfect documentation and still deliver clean fixes.
  
   

Nice to have

• Azure experience (any of: App Services, AKS, Functions, Key Vault, networking basics).
  
   
• Observability experience (App Insights, ELK, Grafana/Prometheus, etc.).
  
   
• Experience modernizing legacy systems (WCF → APIs, monolith → services, etc.).
  
   
• Security-minded habits (secrets handling, least privilege, thinking in blast radius).
  
   

The honest part

• Some documentation is incomplete due to the vendor → internal transition and CIS team migration.
  
   
• You’ll see legacy code.
  
   
• The upside: you’ll be part of the group that improves the system’s clarity, delivery quality, and long-term maintainability.
  
   

Apply with: 2–3 bullets on (1) enterprise/public sector systems you worked on, (2) what you shipped in .NET, and (3) one example where you improved delivery (pipeline, release process, monitoring, or operational stability).