Remote Systems Engineer jobs – Full‑Time Senior Server Engineer (Remote) – AWS, Terraform, Linux – $110k‑$150k – Georgetown, Texas

TITLE:Remote Systems Engineer jobs – Full‑TimeSenior Server Engineer (Remote) – AWS, Terraform, Linux – $110k‑$150k – Georgetown, Texas --- Who we are We’re a 120‑person software platform that started in a cramped coworking space in Georgetown, Texas eight years ago. Today, most of our code lives in the cloud, but we still remember the day we pulled the first rack of servers out of a storage unit and wired them together with duct tape. That scrappy spirit still guides us, even though 70 % of the engineering team now works from home across the U.S.and Europe. Our product – a SaaS analytics suite for mid‑size retailers – processes an average of 2.5 billion events per month. That volume translates to roughly 5,000 virtual machines, 200 TB of daily data ingestion, and a 99.9 % uptime SLA that our customers have come to expect. As we push into new verticals and double our ARR each year, the complexity of the underlying infrastructure has exploded, and that’s where you come in. Why this role exists now Two weeks ago we closed a $50 million Series C round that’s earmarked for a massive hybrid‑cloud migration.We’re moving 40 % of our legacy workloads from on‑prem datacenters in Georgetown, Texas to a mix of AWS and Azure, and we need a seasoned systems engineer to own the end‑to‑end journey. This isn’t a “build‑and‑forget” position: you’ll be responsible for designing, automating, and continuously improving the pipelines that keep our services running, scaling, and secure. If you love figuring out how a change in a Terraform module impacts a Kubernetes node pool, or how a tweak in our Prometheus alerting rules reduces noise for the on‑call rotation, you’ll feel right at home.What you’ll do (day‑to‑day) - Architect & automate: Design Terraform configurations for multi‑cloud VPCs, security groups, and IAM roles. Translate those designs into reusable Ansible playbooks that provision Linux (Ubuntu 20.04, RHEL 8) servers in both public clouds and our remaining on‑prem racks in Georgetown, Texas. - Maintain reliability: Own the 99.9 % uptime SLA for our core services. You’ll monitor health with Prometheus, visualize trends in Grafana, and fine‑tune alert thresholds in PagerDuty to keep on‑call fatigue under 15 minutes of unnecessary noise per week.- Capacity planning: Run quarterly forecasts based on product demand, ensuring we have at least 20 % headroom for traffic spikes. Last year we oversaw a 200 % YoY growth; this year’s goal is 250 %. - Security & compliance: Work with our InfoSec lead to enforce CIS Benchmarks, rotate AWS KMS keys, and patch 300+ Linux hosts within the 48‑hour window mandated by our PCI‑DSS audit. - Incident response: Lead post‑mortems for any breach of SLA, documenting root cause, remediation steps, and actionable improvements.You’ll mentor junior engineers on incident triage and run blameless retrospectives. - Collaboration: Pair with product managers to understand new feature roll‑outs, and translate those requirements into infrastructure changes. You’ll also contribute to the #infra‑ops channel on Slack, where we discuss everything from “why is my pod stuck in CrashLoopBackOff?” to the best coffee maker for home offices. Our current stack (the tools you’ll be using) 1. Terraform – IaC for AWS, Azure, and on‑prem VMware.2. Ansible – Configuration management for Linux and Windows. 3. Docker & Kubernetes (EKS & AKS) – Container orchestration for microservices. 4. Prometheus & Grafana – Metrics collection and dashboarding. 5. Splunk – Log aggregation and search. 6. GitLab CI/CD – Pipelines for building, testing, and deploying. 7. AWS CloudWatch & Azure Monitor – Cloud‑native observability. 8. Jira & Confluence – Project tracking and documentation. 9. Python & Bash – Scripting for automation tasks. 10. HashiCorp Vault – Secrets management.If you’ve spent even a fraction of your career with three or more of these, you’ll fit right in. Who you are (the checklist) -Experience: 5+ years in a systems engineering or server‑engineering role, with at least 3 years of hands‑on Terraform and Ansible. Experience with both AWS and Azure is a plus, but deep expertise in one cloud plus a solid grasp of the other’s APIs will do. - Mindset: You treat infrastructure as code, not as a collection of “servers”. You love version‑controlling everything, reviewing pull requests, and leaving clear commit messages.- Metrics‑driven: You can read a latency histogram and explain why the 99th percentile matters to a business stakeholder. You’ve built SLAs and can defend them with data. - Communication: You can explain a complex networking diagram to a product designer without jargon. The ability to write clear Runbooks is just as important as speaking on a Zoom call with a remote on‑call partner. - Team spirit: You’ll be part of a distributed crew that runs daily stand‑ups across six time zones. Flexibility and respect for each other’s working hours are essential.- Security awareness: Familiarity with CIS Benchmarks, PCI‑DSS, or ISO‑27001 controls. You understand why rotating a root password daily is a bad idea and why using Vault is better. Your impact – numbers that matter - Reduce mean time to recovery (MTTR) from the current 45 minutes to under 30 minutes within the first six months. - Cut the number of manual server patches by 80 % by expanding Ansible coverage from 150 to 1,200 hosts. - Increase infrastructure cost visibility, delivering quarterly reports that identify at least 10 % of spend that can be optimized.A human moment > “I still remember the first time I walked into the data center in Georgetown, Texas and saw the humming rows of servers. It felt like stepping into a cathedral. When we finally migrated that workload to Kubernetes, the whole team celebrated with a virtual pizza party, and I realized that the real reward isn’t the tech—it’s the shared sigh of relief when a deployment finally lands cleanly.” – * Maya Patel,Senior DevOps Engineer* Why we’re a good fit for you - Remote‑first, but with a home base: Even though the role is 100 % remote, we maintain a small “hub” office in Georgetown, Texas for quarterly meet‑ups, in‑person retrospectives, and occasional hackathons.Travel expenses are covered, and we provide a stipend for a coworking desk if you ever want to work outside your home. -Career growth: We have a clear ladder from Junior Systems Engineer → Systems Engineer →Senior Systems Engineer → Staff Engineer → Infrastructure Lead. Over the past year, 40 % of our engineers have moved up at least one level. -Compensation: $110,000 – $150,000 base, depending on experience, plus a 10 % annual performance bonus, equity grant that vests over four years, and a $2,500 yearly stipend for home‑office upgrades.- Benefits that matter: 100 % employer‑paid health, dental, and vision; 4‑week paid parental leave; flexible PTO (unlimited for full‑time employees); quarterly wellness allowance; and a $500 annual contribution toward a professional development course or conference. Team size & structureOur Infrastructure org currently consists of 30 engineers, split 60 % into a Platform team (automating cloud resources) and 40 % into an Operations team (on‑call, incident response, capacity planning). You’ll report to the Infrastructure Manager, who also serves as a mentor and runs a bi‑weekly “Ask Me Anything” session with the entire infra group.The hiring process (what to expect) 1. Resume & cover letter review – We’ll look for concrete achievements, not just buzzwords. 2. Phone screen (30 min) – A quick chat with our recruiter to confirm logistics, remote work setup, and salary expectations. 3. Technical deep‑dive (90 min) – Conducted via Zoom with two senior engineers. Expect a mix of architecture discussion, a live coding exercise in Terraform/Ansible, and a short whiteboard scenario on incident response. 4. Team interview (45 min) – Meet your future peers; we’ll ask you to walk through a recent post‑mortem you authored.5. Culture & leadership conversation (30 min) – A conversation with the Infrastructure Manager focusing on collaboration style, remote‑work habits, and career aspirations. 6. Offer – If everything aligns, you’ll receive a formal offer within 5 business days of the final interview. Send your résumé, a brief note about a project you’re proud of (no more than 300 words), and a link to any public GitHub repos or blog posts that showcase your infrastructure work to [email protected] with the subject line “Remote Systems Engineer – Georgetown, Texas”.We’ll acknowledge receipt within 24 hours and schedule the initial phone screen as soon as possible. A final thought Building systems that keep thousands of retailers’ data flowing reliably isn’t just about code; it’s about people trusting us with their business every day. If you enjoy turning chaos into orderly, repeatable processes, and you thrive in a remote environment that still values occasional face‑to‑face connection in Georgetown, Texas, we’d love to meet you. --- * 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, veteran status, or disability.* Apply tot his job