This Job Vacancy has Expired!

Azure Engineer (REMOTE)

Inavise Tech

Posted on Mar 31, 2021 by Inavise Tech

Brussel, Belgium
IT
Immediate Start
Annual Salary
Contract/Project


We are looking for an experienced Azure Engineer (3+ years experience) for a contract that can be fulfilled remotely. Fluent English is required.

Azure Technology Stack Requirements (3+ years):

  • Azure subscription

  • Active Directory

  • Infra as code, ie terraform with Azure provider via git

  • Container registry

  • SQL server (paas) and SQL server (no paas) for test environment

  • Storage blob

  • Service bus (AMQP)

  • Kubernetes service (AKS) and define metrics to scale out/in

  • Monitoring/metrics

  • Key vault

  • Load balancer and waf

  • Log analytics

  • Devops (git/build/release) with pipelines (alternative is jenkins)

  • Other technologies: Linux, Jira, Keycloak as idp, Prometheus

Job Description:

Objective 1: Efforts saving in Operations (for the RUN mode/maintenance after the project)

Automating all aspects from Application (and Platform) Management that can be automated. Without proper automation, the efforts for application and platform maintenance would be bigger than estimated. Example of automations:

  • Release new version of software to an environment by a press of a button (by the customer)

  • Automated rollback of a release to the previous version in case of unexpected issues in Prod not detected in Test

  • Automated backups, and restore scripts

  • Kill/restart services that are not behaving as they should (when service does not respond to health-check and/or triggered by a pattern of events in the logs)

  • Scripts to Clean-up/archive old data, wipe temp data

Objective 2: Effort saving during the project phase:

  • Help with setting up the CI/CD pipeline (together with architect and lead developer)

  • Setup of monitoring, help create the related dashboards

  • Give guidance to the other developers on what/how to log (not too much, not to little) and check with them how to check health' of the microservices

Objective 3: Minimize the Azure costing/sizing dynamically whilst staying in the SLA's for performance

  • One of the characteristics of Azure is pay per use. If we use too much, we pay too much. Each and every dollar we can save in usage is 100% extra profit; vice versa when we use more than planned we have immediate loss in the Operating Margin.

  • Some cost drivers are straightforward (eg #vCpu's used in containers), but there can be also costs related to amount of storage or amount of network traffic between datacenters

  • Duty of automation engineer is to work with the architect and lead developer to create the appropriate automation to not only scale-up when performance is needed, but also scale down ASAP




Reference: 1146305766

Set up alerts to get notified of new vacancies.