Four kinds of engineer list Azure on a CV. Which one you need depends on the job, and a wrong pick usually shows within the first few weeks.
Azure developer
When your product runs on Azure and the job is to build it, an Azure developer is the hire. They write the application itself, such as APIs on App Service, serverless backends on Azure Functions or services in containers. They also know what each of those choices exposes and what it costs to run. Ours write C#/.NET, Python, Node.js or Java. They are the wrong hire when the application is finished and the problem is how it gets released.
DevOps engineer
Slow builds, manual deploys or a pipeline nobody wants to touch make the pipeline itself the job. Our DevOps engineers own builds, tests and releases in Azure DevOps or GitHub Actions, and treat the application as the thing passing through.
Data engineer
If the work is mostly moving and shaping data, such as pipelines in Azure Data Factory or a warehouse on Synapse or Microsoft Fabric, a data engineer will get further than an application developer. We staff both. The line between them is usually clear once you list what the person will build in their first month.
AI or ML engineer
If the job is putting a model into the product, such as an assistant that answers from your documents or a forecast trained on your data, look at an AI or ML engineer. Their assessment and live coding interview cover production scenarios: designing a RAG pipeline or an evaluation set, latency and cost trade-offs, and handling model drift. On Azure, that model can run in an Azure OpenAI account of your own. An Azure developer still builds the application around the model.
If you run a second cloud next to Azure, we also staff AWS engineers for multi-cloud work, where we have certified engineers too, and on Google Cloud our engineers work hands-on.