DevOps & Performance Engineer

Job Description: DevOps & Performance Engineer (Azure) —    About the role We are hiring a mid-level DevOps & Performance Engineer to own the environments, delivery pipeline, reliability and performance of ULS, a multi-tenant SaaS platform for enterprise shipping and logistics. ULS handles parcel, LTL and FTL execution, carrier integrations, shipping documents and deep ERP integration. It runs on Azure and is built in .NET Core and React. This is a mid-level role. You will be trusted with production systems early and expected to make the way we operate them better. What you will own Environments and delivery Development, Staging and Production environments on Azure: App Service, Azure SQL, Key Vault, Blob Storage, Front Door / WAF, VNet integration, private endpoints, Application Insights CI/CD pipelines in Azure DevOps for .NET Core backend and React frontend, including database migrations Release promotion Dev to Staging to Production, with rollback that has been tested, not just written Provisioning of new customer tenants and dedicated environments as the deployment model requires Reliability and operations Monitoring, alerting and on-call response for production incidents Backup, restore and disaster-recovery procedures, exercised on a schedule Runbooks for every routine operation: deploy, rollback, secret rotation, environment refresh, common failures Azure cost visibility and right-sizing Performance Load and soak testing of shipment-processing paths (order intake, rating, dispatch, label and BOL generation, ERP write-back) SQL query and index performance analysis on Azure SQL Application Insights dashboards for latency, error rate and throughput per tenant Capacity planning for the shared production environment as tenants are added Security Least-privilege access, managed identities and Key Vault for all secrets; no credentials in code or config Network isolation between environments and controlled egress Evidence collection for SOC 2 readiness: access reviews, change logs, deployment records Tenant isolation checks as part of release verification Documentation and enablement Runbooks written as you go and kept current as procedures change Enabling other engineers to run deployments from your runbooks First 90 days You are measured on whether Production runs on documented, repeatable procedures by day 90. By You have Day 30 Read and corrected the existing runbook. Executed every Staging deployment since your start. Shadowed one Production deployment. Access, monitoring and alerting reviewed and gaps listed. Day 60 Executed a Production deployment with a senior engineer observing. Backup and restore exercised once end to end. First load-test baseline of the core shipment path recorded. Day 90 Primary owner of Production operations. Rollback tested in Staging. Cost and performance dashboards live. One further internal engineer has deployed to Staging using your runbook. What we need 2 to 5 years running production workloads on Microsoft Azure . Not a certification alone; you have been paged for something you own. Hands-on with App Service, Azure SQL, Key Vault, Application Insights, VNet and private networking Azure DevOps pipelines (YAML) for build, test, release and database migration Infrastructure as code: Bicep or Terraform, with the discipline to keep it the source of truth SQL Server performance fundamentals: execution plans, indexing, blocking, query tuning Scripting in PowerShell or Bash; comfortable reading C# and understanding how a .NET Core service is configured and deployed Experience with at least one load-testing tool (k6, JMeter, Azure Load Testing) and the judgment to know what to test Security habits: least privilege, managed identities, secret rotation, no shared accounts. You can explain why each of these matters. Clear written English. Runbooks and incident notes are a core output of this role. Willing to overlap with US Eastern working hours for deployments and the daily standup (roughly 15:30 to 19:30 Addis Ababa) Nice to have AZ-104 or AZ-400 certification Multi-tenant SaaS experience, especially tenant isolation and per-tenant observability Azure Front Door or Application Gateway with WAF Message queues: Azure Service Bus or RabbitMQ Containers: Docker, Azure Container Apps or AKS Exposure to SOC 2 or ISO 27001 evidence collection Familiarity with logistics or ERP systems (JD Edwards, SAP, Oracle) so shipment-processing performance means something to you Who this is not for Someone whose Azure experience is coursework or a certification with no production ownership behind it Someone who wants to build platform frameworks rather than run and harden what exists Someone uncomfortable being the person responsible when production is down Someone who treats documentation as a task for later Location and how to apply Location: Addis Ababa, Ethiopia. On site, full time. Compensation: Based on experience. Start: As soon as possible. To apply: Send a CV and a short note (ten lines is enough) describing one production system you were responsible for: what ran on it, what broke, and what you changed afterward. We read the note first.