Remote Cloud Engineer jobs – Senior Full‑Time Cloud Architect & Virtualization Engineer (Remote) – $130k‑$165k – Indian Trail town, North Carolina – Join Our Distributed Team Building Scalable Multi‑Cloud Platforms

TITLE: Remote Cloud Engineer jobs – Senior Full‑Time Cloud Architect & Virtualization Engineer (Remote) – $130k‑$165k – Indian Trail town, North Carolina – Join Our Distributed Team Building Scalable Multi‑Cloud Platforms --- We’re a handful of engineers who started out building a SaaS platform for small‑business accounting back in 2016, and the product has quietly grown into a $45 million ARR service that now supports over 250,000 active users worldwide. Over the past year, three of our biggest customers asked for tighter latency guarantees in the West Coast market, so we opened a “remote‑first” hub in Indian Trail town, North Carolina. That hub isn’t a cubicle farm; it’s a collection of homes, coffee shops, and co‑working spaces where our people can code, troubleshoot, and celebrate wins together—no matter where they live. Your seat on the team will be virtual, but the impact you make will be felt in every request that flows through our API gateway, every Terraform plan that spins up a new VPC, and every alert you silence before our users even notice a glitch. We’re looking for a Cloud Engineer who can wear both the hard‑hat of a virtualization architect and the soft‑skill of a mentor. If you love digging into the nuts and bolts of AWS, Azure, or GCP, and you thrive when a single change can improve a 99.9 % SLA across a $10 M workload, keep reading. --- ### Why This Role Exists Now Our platform’s core services migrated to a container‑native architecture two years ago, but the rapid adoption of AI‑driven analytics last quarter forced us to double our compute footprint in under six months. The “remote cloud” environment we built in Indian Trail town, North Carolina is at a tipping point: we need someone who can design, automate, and optimize multi‑cloud networking, storage, and security without creating techno‑bureaucracy. In plain terms: we have 30 engineers spread across four time zones, 5 SREs on call 24 × 7, and a growing backlog of infrastructure tickets that currently sits at 150 open items with an average resolution time of 4.2 hours. We need a senior‑level engineer who can reduce that average by at least 30 % within the first quarter, while also paving the way for a new “cloud‑native data lake” that will ingest 5 TB of telemetry each day. --- ### A Day in the Life (Remote, but Grounded in Indian Trail town, North Carolina) -

Morning stand‑up (10 am Indian Trail town time):

You’ll sync with the product and security squads, flag any “red‑team” findings, and update the Kanban board that tracks our “in‑flight” Terraform modules. -

Infrastructure design session (11 am–12 pm):

Collaborate with our lead architect to sketch out a cross‑region VPC peering strategy that reduces inter‑zone latency by 15 ms. -

Hands‑on code review (1 pm–3 pm):

Dive into pull requests written in Go, Python, or Bash that implement Helm chart updates, and leave clear feedback about idempotency and observability. -

Incident post‑mortem (4 pm):

When a transient DNS outage hits one of our edge nodes, you’ll lead the RCA, document the timeline in Confluence, and propose a preventive automation. -

Mentorship hour (5 pm):

Pair up with a junior engineer from Indian Trail town, North Carolina for a live debugging session—think of it as a mini‑workshop on “debugging Terraform drift.” -

Wrap‑up (6 pm):

Push the final Terraform plan to our GitHub Actions pipeline, monitor the rollout via Grafana, and raise a quick Slack note to celebrate any successful deployment. Because we’re remote‑first, the clock is flexible; you’ll find colleagues logging in from San Diego, Austin, and even Reykjavik. What stays constant is the emphasis on measurable outcomes and transparent communication. --- ### What You’ll Own 1.

Multi‑Cloud Architecture

– Build and maintain a scalable, secure fabric across AWS (EKS, RDS), Azure (AKS, Cosmos DB), and GCP (GKE, BigQuery). 2.

Infrastructure‑as‑Code (IaC) Strategy

– Write, review, and enforce Terraform modules that version‑control our entire network stack, from subnets to IAM policies. 3.

Container Orchestration

– Optimize Helm charts, define resource quotas, and tune autoscaling policies that keep our micro‑service fleet (≈ 200 services) humming. 4.

Observability & Alerting

– Extend Prometheus exporters, fine‑tune Grafana dashboards, and shape PagerDuty schedules that maintain a 99.9 % SLA for critical endpoints. 5.

Security Hardening

– Implement Sentinel policies, conduct regular CIS‑Benchmark audits, and partner with the security team on zero‑trust network design. 6.

Cost Engineering

– Use CloudHealth and native cost‑explorer tools to track monthly spend (currently $2.3 M) and drive at least a 10 % reduction through rightsizing and reserved‑instance purchases. 7.

Team Enablement

– Run monthly brown‑bag sessions on topics like “GitOps with ArgoCD” and mentor interns or new hires, especially those joining from Indian Trail town, North Carolina. --- ### Tools & Techno