An Azure specialist
A Microsoft Azure engineer for .NET applications: App Service, databases, CI/CD and access rights.
The problem
.NET applications often live in Azure, but a developer set them up "on the side". As a result, deployments are manual and the settings are known to one person.
Who it is for
- A company on the Microsoft stack: .NET, SQL Server, Azure
- An application being moved from its own server to Azure
- A team that has nobody for the cloud infrastructure
What you get
- A candidate vetted on your Azure configuration
- It is clear whether you need full-time or part-time work
- You hold the interview — and the decision is yours too
How the work goes
- 01
You send the requirements — through the form or on WhatsApp
- 02
A short conversation: I clarify the task, the team and the constraints
- 03
I find and personally vet a candidate for your task
- 04
You hold the interview and make the decision
- 05
We agree on the format and terms, and the specialist starts work
What you will need
- Stack and versions: language, frameworks, database, cloud
- The task for the first 2–4 weeks
- Workload: full time, part time or hourly
- Desired start date and expected duration
- Team communication language and time zone
Limits — honestly
- I give the start date and the availability of a specialist after the conversation — I do not promise them in advance
- The cost depends on the format and the task — I give it after the conversation
- The decision about the candidate is always yours
- Access to the Azure subscription — only after we agree, and with limited rights
Example
A manufacturing company is moving an internal .NET system from its own server to Azure. It needs a specialist for the move and then for support.
Terms
- Format
- Monthly, hourly, hiring into your staff or a dedicated team
- Price
- From 50 USD per hour; hiring into your staff — one month's salary of the employee
We settle the other terms in the first message — write to me and I will answer specifically.
Updated: