Full Stack Engineer

About the job

About the Full Stack Engineer role

The Full Stack Engineer is responsible for designing, developing, and maintaining scalable web applications across both frontend and backend environments. This role builds backend services using .NET and C#, develops responsive user interfaces with modern frameworks such as React or Angular, and supports cloud deployment and containerised environments. Working within an AI-assisted development workflow, the engineer collaborates with cross-functional teams to deliver secure, high-quality solutions while implementing CI/CD pipelines, managing cloud infrastructure on Azure, and applying secure development practices to ensure reliable and maintainable systems.

Key Responsibilities:

  • Develop and implement new subsystems using AI-assisted development tools (e.g., GitHub Copilot)
  • Design and maintain end-to-end workflows incorporating AI-assisted recommendations with human-in-the-loop review
  • Build scalable backend services using .NET and C# with SQL databases
  • Develop responsive front-end applications using React or Angular
  • Containerise applications and manage containers using Docker (file, Compose, debugging)
  • Deploy and manage applications on Azure GCC (App Service, Container Apps/AKS)
  • Implement secure identity and access management using EntraID, Managed Identity, and Key Vault
  • Build and maintain CI/CD pipelines using GitHub Actions or Azure DevOps
  • Follow secure development best practices (OWASP, secrets management, dependency hygiene)

Requirements:

  • Experience with AI-assisted development tools (e.g., GitHub Copilot)
  • Strong backend skills: .NET, C#
  • Database expertise: SQL
  • Frontend frameworks: React or Angular
  • Containerisation: Docker, Docker Compose, container debugging (optional)
  • Cloud experience: Azure GCC, App Service, Container Apps/AKS
  • Security: EntraID, Managed Identity, Key Vault
  • CI/CD: GitHub Actions or Azure DevOps
  • Knowledge of AI-assisted workflow processes (prompting, testing, review, governance)
  • Secure development practices: OWASP, secrets hygiene, dependency hygiene

Search Popup

Help me find…

This will close in 0 seconds