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 – JoinOur 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. --- ### WhyThis Role Exists NowOur 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 & Technologies (Our Everyday Toolbox) - AWS, Azure, GCP – Primary public‑cloud providers. - Terraform 1.5+ – IaC engine for all provisioning. - Kubernetes (EKS/AKS/GKE) – Container orchestration platform. - Helm 3 – Package manager for Kubernetes charts. - Docker – Build and run container images. - Ansible & Packer – Configuration management and image building. - GitHub Actions – CI/CD pipelines for IaC and application code. - Prometheus + Grafana – Monitoring stack. - PagerDuty & Opsgenie – Incident response.- CloudHealth, Cost Explorer – Cloud cost management. - Jira & Confluence – Project tracking and documentation. You won’t be expected to master every tool on day one, but we do expect you to have hands‑on experience with at least six of the above in a production environment. --- ### What Success Looks Like (The Metrics We Care About) - Mean Time to Recover (MTTR) drops from 4.2 hours to ≤ 2.5 hours within the first 90 days. - Infrastructure drift incidents reduced by 80 % through automated drift detection in Terraform Cloud.- Cloud spend efficiency improves by 12 % YoY thanks to rightsizing and spot‑instance adoption. - Deployment frequency climbs from 2 per week to at least 5 per week without increasing change‑failure rate. - Team satisfaction scores rise (measured via quarterly Pulse surveys) as junior engineers report a 30 % increase in confidence after mentorship sessions. --- ### Who You Are - 5‑8 years of experience designing, building, and operating production‑grade cloud infrastructure (AWS, Azure, or GCP). - Deep familiarity with Terraform (modules, workspaces, remote state backends) and Kubernetes (network policies, custom controllers).- Strong scripting chops—Bash, Python, or PowerShell—to automate repetitive tasks. - Security‑mindset: experience with IAM, service‑mesh security (Linkerd, Istio) and compliance frameworks (SOC 2, ISO 27001). - Analytical eye for cost‑optimization; you’ve shopped around Reserved Instances, Savings Plans, and spot markets. - Collaborative communicator: you can explain “why we need a VPC peering” to a product manager in plain English and get them on board. - Mentor at heart: you enjoy pair‑programming and have a track record of lifting junior engineers, especially those remote‑working from Indian Trail town, North Carolina or nearby regions.Nice‑to‑have: experience with GitOps (ArgoCD, Flux), service‑mesh technologies, or data‑lake pipelines in Spark or Flink. --- ###The Human Moment > “I first met Maya from our Indian Trail town office on a Slack call while she was troubleshooting a Terraform apply that kept failing on a Windows laptop. We ended up talking about her kids’ science fair project for two hours before we finally solved the issue. That’s the kind of connection we value—people, not just code.” – Jordan Patel,Senior SRE Lead --- ### What We Offer (BeyondSalary) - Base salary: $130k‑$165k, commensurate with experience, plus annual performance bonus.- Remote‑first flexibility: Choose any coworking space or home office in Indian Trail town, North Carolina; we’ll cover a $1,200 yearly stipend for internet or desk‑setup. - Health & wellness: Full medical, dental, vision coverage for you and immediate family, plus mental‑health resources (Talkspace subscription). -Professional growth: $2,000 yearly education budget, certifications paid (AWS Certified Solutions Architect – Professional, CKA, etc.). - Paid time off: 20 days PTO + 10 public holidays (including a “Remote Work Day” where the entire team logs off for a digital detox).- Equity: Stock options that vest over four years, aligning your success with the company’s. We understand that remote work can blur the line between “on” and “off.” That’s why we encourage you to set clear boundaries, and we respect your evenings, weekends, and holidays—unless there’s a real fire, in which case you’ll be the one we call because you own the solution, not because we expect you to be “always available.” --- ### 1. Resume & cover letter – Highlight a project where you reduced MTTR or cloud spend, preferably with numbers.2. Technical questionnaire – A short 5‑question form about Terraform state management and Kubernetes networking. 3. Live coding interview – We’ll share a real Terraform snippet (no whiteboard) and ask you to refactor it for modularity. 4. Culture chat – A 30‑minute conversation with our hiring manager, Jordan, and a senior engineer from Indian Trail town, North Carolina to see if the team vibe feels right. We aim to move quickly—most candidates hear back within 48 hours of submitting their materials. --- ### Final Thought If you’ve ever felt the thrill of watching a Terraform plan go from “planned” to “applied” and instantly seeing a new subnet appear in the AWS console, you’ll understand why this role feels almost magical.It’s not about the buzzwords; it’s about building a platform that lets small businesses run their finances without worrying about downtime, security breaches, or exploding cloud bills. Our team in Indian Trail town, North Carolina is small enough that your ideas will land on the road‑map within days, yet large enough to give you the depth of challenge you crave. We’re not looking for a “cloud engineer” who can just push buttons—we need a partner who can think strategically, act tactically, and mentor constantly.Ready to shape the next generation of remote cloud infrastructure? Click Apply and let’s start the conversation. --- * We are an equal‑opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or veteran status.* Apply tot his job