The Company seeks a senior Azure/DevOps engineer for a high-trust, part-time maintenance role supporting a preserved internal research prototype.
This is not a feature-development or rebuild engagement. The objective is to keep the existing Azure/GitHub environment secure, documented, recoverable, and cost-conscious while we complete product and market strategy work.
Core Responsibilities:
• Conduct a monthly Azure health, cost, and resource review.
• Review Azure RBAC, privileged access, and contractor access on a least-privilege basis.
• Verify backup status and help plan or execute an approved non-production recovery drill.
• Produce a preservation-first cost-control plan identifying each resource as retain, stop/deallocate, scale down, or decommission; quantify the expected monthly savings; identify remaining residual charges; and obtain written founder approval before making any change.
• Review monitoring, alert routing, GitHub repository status, workflows, and documented deployment/recovery paths.
• Maintain a concise Faro-owned runbook and asset/access inventory.
• Deliver a brief monthly written report covering system status, changes, costs, risks, and recommended actions.
• Escalate material risks promptly; make no changes without written approval.
Requirements:
• Strong Azure App Service, VM, MySQL, Azure Monitor/Application Insights, GitHub Actions, backup/recovery, and Azure RBAC experience.
• Experience inheriting and documenting imperfectly handed-over environments.
• Excellent written communication for a non-technical founder.
• Comfortable with confidential systems, founder-owned accounts, MFA, least-privilege access, and time-bound permissions.
Engagement:
Expected duration set at 3–5 business days after access is provisioned. This is a fixed-scope assessment; an optional, separately negotiated light monthly maintenance retainer may be considered after successful completion; no ongoing engagement is guaranteed.
What to Submit with Application:
Please include: relevant Azure operations experience, availability, hourly or monthly-retainer expectation, and a brief example of how you would structure a monthly founder-facing status report.