IT Cloud Engineer

People Inc.

1d•Remote

About The Position

People Inc. seeks an experienced IT Cloud Engineer to support, maintain, and modernize enterprise infrastructure during data‑center decommissioning and cloud migrations. You will own Windows Server operations, identity integrations (Okta–AD/Azure-AD), automation, and hybrid cloud services across on‑prem and AWS/Azure/GCP.

Requirements

5+ years in systems administration or infrastructure engineering.
Strong Windows Server and patch automation experience.
Hands‑on with AWS, Azure, or GCP (IAM, compute/storage, networking).
Deep knowledge of Okta, Active Directory, Azure AD integrations.
Scripting with PowerShell (preferred), plus Python or Bash.
Experience with Linux, Nutanix, Rubrik.
Familiarity with Docker/containers.
Monitoring/logging with Prometheus/Grafana, Loki, Splunk, or ELK.
Excellent troubleshooting and stakeholder communication.

Nice To Haves

Cloud-migration background
ITIL knowledge
Microsoft Administrator or cloud certifications.

Responsibilities

Administer 200+ Windows Servers; own patching SLAs, monitoring (Prometheus/Grafana), capacity/lifecycle plans, and vulnerability remediations.
Operate AD/Azure AD; serve as Okta–AD SSO/MFA integration owner (health, upgrades, certificates, lifecycle).
Execute NYC data‑center app migrations; assist Nutanix decommission; administer Rubrik backups and Sectigo certificates.
Build dashboards and alerts; define SLOs with app owners; deliver monthly system inventory, ownership, and compliance reports.
Manage enterprise DNS (non‑Route 53); support ClearPass and printer authentication integrations.
Manage AWS/Azure/GCP workloads (VMs, IAM, storage/compute, networking, connectivity); optimize cost, reliability, and security.
Deliver PowerShell/Python/Bash tooling for patching, configuration, and repetitive operations; champion IaC/Config‑as‑Code where feasible.
Plan & governance for Active Directory Migration: define scope/success/rollback, RFC/CAB approvals, stakeholder comms, risk register, clear ownership and SLAs.
Baseline & readiness for Active Directory Migration: full AD/GPO/OUs/trusts/DC health (dcdiag/repadmin), security posture (tiering/LAPS/NTLM), backups/DR tested.
Identity & SSO design for Active Directory Migration: source of truth + JML, AAD Connect (PHS/PTA, sourceAnchor, staging/writeback), Okta agents/MFA/policies, UPN/sAMAccountName strategy.
App/data/network prep + pilot for Active Directory Migration: catalog LDAP/Kerberos apps/SPNs, file/print ACLs, DNS/DHCP validation; run a scoped pilot with helpdesk scripts and rollback.
Execute, monitor, cutover, close for Active Directory Migration: wave-based moves with replication checks, live auth monitoring, cutover steps, post‑validation, cleanup/decommission, docs/CMDB updates, PIRs and metrics.
Follow ITIL‑aligned change process: RFC tickets with peer review, test evidence, implementation/backout plans, and maintenance windows; attend CAB as required.
Track changes in Jira; update CMDB/asset records within 7 days of change; complete PIRs within 5 business days for failed/high‑risk changes.
Enforce progressive delivery: phased rollouts, canaries, and checkpoint validation; document rollback criteria and success gates upfront.
Maintain current runbooks, architecture/network diagrams, standard operating procedures, DR playbooks, and “How We Operate” docs in a versioned repository.
Treat documentation as acceptance criteria: every change/migration updates docs before closure; keep system ownership and escalation paths explicit.
Publish weekly change summaries and quarterly service health reviews to stakeholders.
Plan migrations and decommissioning as small, testable increments with clear exit/rollback; demonstrate progress via bi‑weekly demos and burn‑up charts.
Use feature flags/guardrails where applicable; prefer automate‑then‑standardize over one‑off fixes.
Maintain a visible improvement backlog (automation debt, toil reduction, cost optimizations) with quarterly goals.