Search

Azure AI Application Platform & DevSecOps Engineer

PublishedPublished: 6/14/2022
Technology

Job Description

Azure AI Application Platform & DevSecOps Engineer

\n

Senior Individual Contributor | Azure | Full Stack | Platform Engineering | DevSecOps | ALM | Fully Remote Contract Position | C2C | 1099 | 70-85 USD/hr

\n


\n


\n

Position Summary

\n

Osborn & Holloway is seeking a senior Azure Application Platform & DevSecOps Engineer to help design and build a governed internal AI application incubation platform that allows non-technical and semi-technical business users to create custom web applications safely within the Microsoft Azure ecosystem.

\n


\n

The user experience should be deceptively simple.

\n

A business user may know what application they want to build without knowing how to create an Azure Resource Group, register an application, configure an identity, provision a Key Vault, select a hosting model, create a deployment pipeline, secure a database, configure monitoring, or manage environment promotion.

\n


\n

This role is responsible for helping turn RedSail’s architectural, security, infrastructure, and SDLC expectations into automated platform behavior and enforceable guardrails.

\n

We are not trying to eliminate SDLC. We are trying to encode SDLC into the platform so the business user does not have to perform it manually.

\n


\n

This engineer will work closely with a complementary AI Application Platform Engineer responsible for the conversational, AI-assisted, and application-generation layers of the platform.

\n

Together, these engineers will build a “system that builds systems.”

\n


\n

What Makes This Role Different

\n

This is not a traditional Azure administrator or DevOps position.

\n

The successful candidate will design the infrastructure and governance abstraction layer that allows users who know very little about Azure to safely create applications inside it.

\n


\n

The platform—not the citizen developer—should understand how applications are provisioned, secured, monitored, promoted, governed, and eventually retired.

\n


\n

The goal is not merely automation. The goal is to make the correct enterprise engineering path the easiest—and whenever appropriate, the only—path available.

\n


\n

Key ResponsibilitiesAzure Platform Engineering

\n

· Design the Azure architecture supporting the application incubation environment.

\n

· Develop approved deployment patterns for common categories of internally generated web applications.

\n

· Automate provisioning and configuration of Azure resources required by generated applications.

\n

· Establish appropriate patterns for Resource Groups, application hosting, storage, databases, APIs, identities, networking, monitoring, and supporting services.

\n

· Develop reusable infrastructure components using Infrastructure as Code.

\n

· Use Bicep, Terraform, or other approved technologies to make infrastructure provisioning repeatable and auditable.

\n

· Establish naming, tagging, ownership, lifecycle, and cost-management standards for generated resources.

\n


\n

Identity, Security and Governance

\n

· Design secure authentication and authorization patterns using Microsoft Entra ID.

\n

· Automate appropriate use of managed identities, app registrations, service principals, and RBAC.

\n

· Establish automated Key Vault and secrets-management patterns.

\n

· Prevent generated applications from adopting unsafe credential, secret-storage, or access-control practices.

\n

· Incorporate Azure Policy and other governance mechanisms into the incubation environment.

\n

· Establish appropriate security scanning, package/dependency validation, and code-quality controls.

\n

· Collaborate with security and infrastructure stakeholders to define boundaries within which citizen-generated applications may operate.

\n

· Design technical controls that prevent generated applications from bypassing required governance.

\n


\n

DevSecOps and Application Lifecycle Management

\n

· Design automated source-control and CI/CD patterns for generated applications.

\n

· Integrate the platform with Azure DevOps repositories, work items, pipelines, and release processes.

\n

· Establish standardized DEV, test/UAT, and production deployment patterns.

\n

· Build automated quality, security, and approval gates into application promotion.

\n

· Ensure generated applications remain traceable, supportable, and recoverable.

\n

· Develop rollback, backup, monitoring, logging, and operational-support patterns.

\n

· Automate creation of appropriate deployment and operational documentation.

\n

· Establish lifecycle processes for application ownership transfer, retirement, and resource decommissioning.

\n


\n

Application Incubator Guardrails

\n

· Work with the AI Application Platform Engineer to translate enterprise engineering standards into automated platform rules.

\n

· Define which architectural decisions may safely be made automatically and which require human review.

\n

· Establish thresholds that determine when a self-service application must “graduate” into formal architecture, security, engineering, or governance review.

\n

· Consider factors including data sensitivity, regulatory implications, external exposure, integration complexity, transaction volume, business criticality, and user population.

\n

· Build mechanisms that prevent an application from progressing when required controls have not been satisfied.

\n

· Ensure the platform can explain why an application has been stopped, escalated, or routed for additional review.

\n


\n

Full-Stack and Integration Engineering

\n

· Maintain sufficient full-stack development capability to understand and troubleshoot applications produced by the incubation platform.

\n

· Develop APIs and platform services required to connect AI orchestration, application generation, Azure provisioning, and DevOps automation.

\n

· Collaborate on reusable application components and architectural templates.

\n

· Support integrations with approved Microsoft enterprise services and business systems.

\n

· Participate directly in troubleshooting generated applications when failures span application, infrastructure, identity, security, or deployment boundaries.

\n


\n

Required Qualifications

\n

· Significant professional experience with Microsoft Azure architecture and engineering.

\n

· Strong understanding of Azure identity, security, networking, compute, storage, application hosting, and data services.

\n

· Hands-on experience with Microsoft Entra ID, RBAC, managed identities, app registrations, and enterprise authentication patterns.

\n

· Experience with Azure Key Vault and secure secrets-management practices.

\n

· Strong Infrastructure-as-Code experience using Bicep, Terraform, or comparable technologies.

\n

· Strong Azure DevOps experience, including repositories, pipelines, and application lifecycle management.

\n

· Practical experience designing CI/CD and DevSecOps processes.

\n

· Working full-stack development knowledge sufficient to understand modern web applications, APIs, databases, and application architecture.

\n

· Strong understanding of SDLC, environment management, testing, release management, and production-support principles.

\n

· Familiarity with Agile development methodologies.

\n

· Strong written and verbal English communication skills.

\n

· Ability to work independently while collaborating closely with another senior engineer across overlapping areas of responsibility.

\n


\n

Preferred Qualifications

\n

· Relevant Microsoft Azure certifications.

\n

· Experience with Azure OpenAI or AI-enabled application platforms.

\n

· Experience developing internal developer platforms, application factories, self-service provisioning systems, or Platform Engineering capabilities.

\n

· Experience with Azure Policy and enterprise cloud governance.

\n

· Experience with Microsoft Power Platform, Dataverse, Power Automate, or other low-code/no-code technologies.

\n

· Experience with application observability, Application Insights, Log Analytics, and automated operational monitoring.

\n

· Experience designing systems in regulated, healthcare, financial, or other security-conscious environments.

\n

· Experience with secure software supply-chain practices and automated vulnerability management.

\n

· Familiarity with FinOps and cloud cost-governance principles.

\n


\n

The Person We Are Looking For

\n

You should be an engineer who believes automation is most valuable when it eliminates opportunities for people to make avoidable mistakes.

\n

You understand that hiding Azure complexity from a business user does not eliminate that complexity—it transfers responsibility for handling it correctly to the platform.

\n

You should be comfortable working in the space between software engineering, cloud architecture, security, DevOps, and platform engineering.

\n

You should also be pragmatic. Not every departmental application needs an architecture review board. Conversely, a prototype that suddenly begins storing sensitive data or supporting a critical business process cannot remain an uncontrolled experiment simply because that is how it started.

\n

The successful candidate will help us find—and automate—that boundary.

\n

    \n
  • Ultimately, your job is to make it possible for someone who knows almost nothing about enterprise software engineering to create useful applications without requiring the organization to accept the risks that would normally accompany that lack of knowledge.
  • \n

Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...