Sr. Azure DevOps Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading with filler placeholder text. Prefer few substantive sections.
We need to extract content: Position Description CGI is seeking a hands-on Azure Developer & DevOps Engineer... The role combines... This role can be performed near any CGI office - Eastern Time Zone.
Then "Your future duties and responsibilities" with subsections: Azure Application Development, Integration & Data Services, CI/CD & Release Engineering, Infrastructure as Code & Automation, Containers & Kubernetes, DevSecOps, Identity & Security, Monitoring, Reliability & Operations, Environment & Cloud Operations, Agile Delivery & Continuous Improvement.
Then "Required Qualifications To Be Successful In This Role": bullet list of qualifications.
Then "Certifications (Highly Valued)" list.
Then "Core Skills" list.
Then "Other Information:" includes compensation range and benefits description.
We need to produce sections: maybe "About the role" (intro paragraph), "Responsibilities" (list of duties), "Requirements" (qualifications), "Skills" (core skills), "Benefits" (benefits description), "Pay" (compensation range). Possibly "Qualifications" separate from "Requirements"? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications? Might be redundant. We can combine qualifications into Requirements and maybe Qualifications for certifications? But we need to avoid filler. Let's decide: Use "About the role" for intro paragraph. Use "Responsibilities" for duties (list). Use "Requirements" for required qualifications (experience, hands-on experience). Use "Skills" for core skills list. Use "Benefits" for benefits description. Use "Pay" for compensation range. Possibly also "Certifications" could be part of Qualifications or Skills, but we can include under Qualifications as a sublist? But we must not create extra headings unless content. Could include Certifications under Qualifications as a list.
We must not include Schedule (no info). So omit.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific technologies, etc. For responsibilities we need to list each bullet under subheadings? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten duties into a list, but we might lose subheadings. However we could keep subheadings as
? Not allowed; only headings listed are for section headings. We could embed subheadings as inside - maybe. But better to keep each duty as a list item, preserving details. Could also keep subheadings as plain text before list? Might be considered heading but not
. The instruction only says use for section headings; doesn't forbid other headings like or . But to be safe, we can just produce list items with the duty descriptions.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from responsibilities sections. That is a lot. We'll need to produce a long with many - items covering each bullet.
Similarly for qualifications: list items.
For skills: list items.
For benefits: list items (maybe bullet list from description). The benefits paragraph includes multiple items: Competitive compensation, Comprehensive insurance options, Matching contributions through the 401(k) plan and the share purchase plan, Paid time off for vacation, holidays, and sick time, Paid parental leave, Learning opportunities and tuition assistance, Wellness and Wellbeing programs. We'll list each.
Pay: include the compensation range: $113,400.00 $198,400.00 (note there is a space between numbers). We'll output as "$113,400.00 – $198,400.00" maybe keep as given.
We must not include boilerplate like EEO etc. So we cut after benefits and pay.
Now produce HTML fragment:
About the role
CGI is seeking a hands-on Azure Developer & DevOps Engineer to design, build, automate, deploy, and support cloud native applications, APIs, integrations, and platform components in Microsoft Azure. The role combines application development with DevOps engineering and focuses on secure coding, CI/CD, Infrastructure as Code, containers, identity and secrets management, observability, reliability, and production support. The engineer will work across Azure App Service, Functions, AKS, API Management, Service Bus/Event Grid, Azure SQL/Storage, Azure DevOps or GitHub, Terraform/Bicep, Key Vault, and Azure Monitor while supporting the client's broader data and analytics ecosystem. This role can be performed near any CGI office - Eastern Time Zone.
Responsibilities
- Azure Application Development: Design, develop, test, and support cloud native applications, REST APIs, microservices, and background services using C#/.NET and/or Python. Build solutions on Azure App Service, Azure Functions, and AKS, with integrations to Azure SQL, Cosmos DB, Storage Accounts, and Key Vault. Apply secure coding standards, dependency management, unit/integration testing, code review, and reusable development patterns. Use API Management for secure API exposure, versioning, throttling, authentication, and lifecycle management.
- Integration & Data Services: Build event driven and asynchronous integrations using Azure Service Bus, Event Grid, and Logic Apps. Develop data access and integration components for Azure SQL, Storage/ADLS, Databricks, and Microsoft Fabric as required by the solution. Create reliable interfaces with validation, retry, idempotency, error handling, and operational logging.
- CI/CD & Release Engineering: Create multistage YAML pipelines in Azure DevOps Pipelines and/or GitHub Actions for build, test, security scan, package, and deployment. Manage Git workflows in Azure Repos/GitHub using branching strategies, pull request policies, code reviews, versioning, and Azure Artifacts. Implement environment promotion, approvals, release gates, configuration management, deployment strategies, and rollback procedures.
- Infrastructure as Code & Automation: Provision Azure infrastructure with Terraform and Bicep/ARM using reusable modules and environment specific configuration. Automate deployments and operational tasks with Azure CLI, PowerShell, and scripting; minimize manual environment changes. Manage remote state, service connections, managed identities, variables, and Key Vault backed secrets securely.
- Containers & Kubernetes: Containerize applications with Docker and publish versioned images to Azure Container Registry (ACR). Deploy and operate workloads on AKS using Helm, namespaces, health probes, configuration/secrets, autoscaling, and rolling deployments. Support container and image security scanning, patching, troubleshooting, and lifecycle management.
- DevSecOps, Identity & Security: Integrate Microsoft Entra ID, RBAC, managed identities, and Key Vault into applications and deployment pipelines. Apply least privilege, secure service connections, secret rotation, network security controls, and environment separation. Embed code, dependency, IaC, and container security checks into pipelines; support Azure Policy and Defender for Cloud controls. Work within client security, privacy, HIPAA, and SDLC requirements for regulated workloads.
- Monitoring, Reliability & Operations: Instrument applications with Application Insights and use Azure Monitor and Log Analytics for logs, metrics, traces, dashboards, and alerts. Troubleshoot application, pipeline, platform, and deployment failures across development, test, and production environments. Implement health checks, scaling, resilience, backup/recovery, incident response, root cause analysis, and operational runbooks.
- Environment & Cloud Operations: Maintain repeatable development, test, staging, and production environments through automation and configuration as code practices. Support tagging, resource standards, cost visibility, performance tuning, capacity planning, and Azure Advisor recommendations. Collaborate with platform, network, security, database, and data engineering teams to resolve environment dependencies.
- Agile Delivery & Continuous Improvement: Work from user stories and acceptance criteria; estimate tasks, document technical decisions, and deliver through Agile sprint processes. Participate in design reviews, peer code reviews, release planning, production support, and knowledge transfer. Evaluate Azure service updates and engineering practices that improve developer productivity, deployment frequency, security, and reliability.
Requirements
- 6–10+ years in software engineering, cloud application development, DevOps, or platform engineering roles.
- 4+ years of hands-on Microsoft Azure development and deployment experience.
- Proven hands-on experience with:
- C#/.NET and/or Python development; REST APIs, microservices, background services, and automated testing
- Azure App Service, Functions, AKS, API Management, Service Bus/Event Grid, Storage Accounts, Azure SQL, and Key Vault
- Azure DevOps or GitHub: Repos, Pipelines/Actions, YAML, pull requests, branch policies, artifacts, environments, approvals, and releases
- Terraform and Bicep/ARM; Azure CLI and PowerShell; Docker, ACR, AKS, and Helm
- Certifications (Highly Valued): AZ 204: Developing Solutions for Microsoft Azure; AZ 400: Designing and Implementing Microsoft DevOps Solutions; AZ 104 also valued.
Skills
- Software engineering, secure coding, design patterns, unit/integration testing, and API design
- CI/CD, Git, release engineering, environment promotion, rollback, and deployment automation
- Infrastructure as Code, configuration management, scripting, and reusable automation
- Containerization and orchestration with Docker, ACR, AKS, and Helm
- DevSecOps, Entra ID, RBAC, managed identities, Key Vault, Azure Policy, and Defender for Cloud
- Monitoring and observability with Application Insights, Azure Monitor, and Log Analytics
- Developer & DevOps Toolset: Visual Studio/VS Code, Git, Azure Repos/GitHub, Azure Boards, Azure Pipelines/GitHub Actions, YAML, Azure Artifacts, and API testing tools
- Terraform, Bicep/ARM, Azure CLI, PowerShell, Docker, ACR, AKS, Helm, and environment/configuration management
- Application Insights, Azure Monitor, Log Analytics, Key Vault, Microsoft Entra ID, Defender for Cloud, Azure Policy, and security scanning tools
Benefits
- Competitive compensation
- Comprehensive insurance options
- Matching contributions through the 401(k) plan and the share purchase plan
- Paid time off for vacation, holidays, and sick time
- Paid parental leave
- Learning opportunities and tuition assistance
- Wellness and Wellbeing programs
Pay
A reasonable estimate of the current range for this role in the U.S. is $113,400.00 $198,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading with filler placeholder text. Prefer few substantive sections. We need to extract content: Position Description CGI is seeking a hands-on Azure Developer & DevOps Engineer... The role combines... This role can be performed near any CGI office - Eastern Time Zone. Then "Your future duties and responsibilities" with subsections: Azure Application Development, Integration & Data Services, CI/CD & Release Engineering, Infrastructure as Code & Automation, Containers & Kubernetes, DevSecOps, Identity & Security, Monitoring, Reliability & Operations, Environment & Cloud Operations, Agile Delivery & Continuous Improvement. Then "Required Qualifications To Be Successful In This Role": bullet list of qualifications. Then "Certifications (Highly Valued)" list. Then "Core Skills" list. Then "Other Information:" includes compensation range and benefits description. We need to produce sections: maybe "About the role" (intro paragraph), "Responsibilities" (list of duties), "Requirements" (qualifications), "Skills" (core skills), "Benefits" (benefits description), "Pay" (compensation range). Possibly "Qualifications" separate from "Requirements"? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications? Might be redundant. We can combine qualifications into Requirements and maybe Qualifications for certifications? But we need to avoid filler. Let's decide: Use "About the role" for intro paragraph. Use "Responsibilities" for duties (list). Use "Requirements" for required qualifications (experience, hands-on experience). Use "Skills" for core skills list. Use "Benefits" for benefits description. Use "Pay" for compensation range. Possibly also "Certifications" could be part of Qualifications or Skills, but we can include under Qualifications as a sublist? But we must not create extra headings unless content. Could include Certifications under Qualifications as a list. We must not include Schedule (no info). So omit. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific technologies, etc. For responsibilities we need to list each bullet under subheadings? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten duties into a list, but we might lose subheadings. However we could keep subheadings as
? Not allowed; only headings listed are
for section headings. We could embed subheadings as inside
- maybe. But better to keep each duty as a list item, preserving details. Could also keep subheadings as plain text before list? Might be considered heading but not
. The instruction only says use
for section headings; doesn't forbid other headings like
or . But to be safe, we can just produce list items with the duty descriptions. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from responsibilities sections. That is a lot. We'll need to produce a long
- with many
- items covering each bullet.
Similarly for qualifications: list items.
For skills: list items.
For benefits: list items (maybe bullet list from description). The benefits paragraph includes multiple items: Competitive compensation, Comprehensive insurance options, Matching contributions through the 401(k) plan and the share purchase plan, Paid time off for vacation, holidays, and sick time, Paid parental leave, Learning opportunities and tuition assistance, Wellness and Wellbeing programs. We'll list each.
Pay: include the compensation range: $113,400.00 $198,400.00 (note there is a space between numbers). We'll output as "$113,400.00 – $198,400.00" maybe keep as given.
We must not include boilerplate like EEO etc. So we cut after benefits and pay.
Now produce HTML fragment:
About the role
CGI is seeking a hands-on Azure Developer & DevOps Engineer to design, build, automate, deploy, and support cloud native applications, APIs, integrations, and platform components in Microsoft Azure. The role combines application development with DevOps engineering and focuses on secure coding, CI/CD, Infrastructure as Code, containers, identity and secrets management, observability, reliability, and production support. The engineer will work across Azure App Service, Functions, AKS, API Management, Service Bus/Event Grid, Azure SQL/Storage, Azure DevOps or GitHub, Terraform/Bicep, Key Vault, and Azure Monitor while supporting the client's broader data and analytics ecosystem. This role can be performed near any CGI office - Eastern Time Zone.
Responsibilities
- Azure Application Development: Design, develop, test, and support cloud native applications, REST APIs, microservices, and background services using C#/.NET and/or Python. Build solutions on Azure App Service, Azure Functions, and AKS, with integrations to Azure SQL, Cosmos DB, Storage Accounts, and Key Vault. Apply secure coding standards, dependency management, unit/integration testing, code review, and reusable development patterns. Use API Management for secure API exposure, versioning, throttling, authentication, and lifecycle management.
- Integration & Data Services: Build event driven and asynchronous integrations using Azure Service Bus, Event Grid, and Logic Apps. Develop data access and integration components for Azure SQL, Storage/ADLS, Databricks, and Microsoft Fabric as required by the solution. Create reliable interfaces with validation, retry, idempotency, error handling, and operational logging.
- CI/CD & Release Engineering: Create multistage YAML pipelines in Azure DevOps Pipelines and/or GitHub Actions for build, test, security scan, package, and deployment. Manage Git workflows in Azure Repos/GitHub using branching strategies, pull request policies, code reviews, versioning, and Azure Artifacts. Implement environment promotion, approvals, release gates, configuration management, deployment strategies, and rollback procedures.
- Infrastructure as Code & Automation: Provision Azure infrastructure with Terraform and Bicep/ARM using reusable modules and environment specific configuration. Automate deployments and operational tasks with Azure CLI, PowerShell, and scripting; minimize manual environment changes. Manage remote state, service connections, managed identities, variables, and Key Vault backed secrets securely.
- Containers & Kubernetes: Containerize applications with Docker and publish versioned images to Azure Container Registry (ACR). Deploy and operate workloads on AKS using Helm, namespaces, health probes, configuration/secrets, autoscaling, and rolling deployments. Support container and image security scanning, patching, troubleshooting, and lifecycle management.
- DevSecOps, Identity & Security: Integrate Microsoft Entra ID, RBAC, managed identities, and Key Vault into applications and deployment pipelines. Apply least privilege, secure service connections, secret rotation, network security controls, and environment separation. Embed code, dependency, IaC, and container security checks into pipelines; support Azure Policy and Defender for Cloud controls. Work within client security, privacy, HIPAA, and SDLC requirements for regulated workloads.
- Monitoring, Reliability & Operations: Instrument applications with Application Insights and use Azure Monitor and Log Analytics for logs, metrics, traces, dashboards, and alerts. Troubleshoot application, pipeline, platform, and deployment failures across development, test, and production environments. Implement health checks, scaling, resilience, backup/recovery, incident response, root cause analysis, and operational runbooks.
- Environment & Cloud Operations: Maintain repeatable development, test, staging, and production environments through automation and configuration as code practices. Support tagging, resource standards, cost visibility, performance tuning, capacity planning, and Azure Advisor recommendations. Collaborate with platform, network, security, database, and data engineering teams to resolve environment dependencies.
- Agile Delivery & Continuous Improvement: Work from user stories and acceptance criteria; estimate tasks, document technical decisions, and deliver through Agile sprint processes. Participate in design reviews, peer code reviews, release planning, production support, and knowledge transfer. Evaluate Azure service updates and engineering practices that improve developer productivity, deployment frequency, security, and reliability.
Requirements
- 6–10+ years in software engineering, cloud application development, DevOps, or platform engineering roles.
- 4+ years of hands-on Microsoft Azure development and deployment experience.
- Proven hands-on experience with:
- C#/.NET and/or Python development; REST APIs, microservices, background services, and automated testing
- Azure App Service, Functions, AKS, API Management, Service Bus/Event Grid, Storage Accounts, Azure SQL, and Key Vault
- Azure DevOps or GitHub: Repos, Pipelines/Actions, YAML, pull requests, branch policies, artifacts, environments, approvals, and releases
- Terraform and Bicep/ARM; Azure CLI and PowerShell; Docker, ACR, AKS, and Helm
- Certifications (Highly Valued): AZ 204: Developing Solutions for Microsoft Azure; AZ 400: Designing and Implementing Microsoft DevOps Solutions; AZ 104 also valued.
Skills
- Software engineering, secure coding, design patterns, unit/integration testing, and API design
- CI/CD, Git, release engineering, environment promotion, rollback, and deployment automation
- Infrastructure as Code, configuration management, scripting, and reusable automation
- Containerization and orchestration with Docker, ACR, AKS, and Helm
- DevSecOps, Entra ID, RBAC, managed identities, Key Vault, Azure Policy, and Defender for Cloud
- Monitoring and observability with Application Insights, Azure Monitor, and Log Analytics
- Developer & DevOps Toolset: Visual Studio/VS Code, Git, Azure Repos/GitHub, Azure Boards, Azure Pipelines/GitHub Actions, YAML, Azure Artifacts, and API testing tools
- Terraform, Bicep/ARM, Azure CLI, PowerShell, Docker, ACR, AKS, Helm, and environment/configuration management
- Application Insights, Azure Monitor, Log Analytics, Key Vault, Microsoft Entra ID, Defender for Cloud, Azure Policy, and security scanning tools
Benefits
- Competitive compensation
- Comprehensive insurance options
- Matching contributions through the 401(k) plan and the share purchase plan
- Paid time off for vacation, holidays, and sick time
- Paid parental leave
- Learning opportunities and tuition assistance
- Wellness and Wellbeing programs
Pay
A reasonable estimate of the current range for this role in the U.S. is $113,400.00 $198,
- maybe. But better to keep each duty as a list item, preserving details. Could also keep subheadings as plain text before list? Might be considered heading but not