ZipRecruiter

Log In

2

Director Remote Systems Engineer Jobs in Texas (NOW HIRING)

ASCENDING LLC

RHEL Systems Engineer

Houston, TX · On-site +1

... Full Time, Direct Hire - remote but may need to travel to client locations periodically ... systems from SCADA to cloud-and everything in between. About The Position The Senior RHEL engineer ...

Fanniemae

Systems Engineer- Nexthink

Plano, TX · Remote

As a Systems Engineer - Nexthink, you will help improve the digital experience of thousands of ... Create and maintain Nexthink content including investigations, remote actions, workflows, campaigns ...

New

SpaceX

Power Systems Engineer

Bastrop, TX · On-site +1

POWER SYSTEMS ENGINEER As a member of the Construction Projects Team, you will work with engineers ... This role requires you to be onsite - hybrid or remote work will not be considered * Must be able ...

IronEdge Group

Systems Engineer III

Houston, TX · On-site +1

Systems Engineer III (This is a remote position open to applicants residing in TX, NM, AZ, CO, or KS) As a Systems Engineer III, you will serve as a senior technical resource within our MSP ...

previous page

Showing results 41-60

All JobsSystems Engineer JobsDirector Remote Systems Engineer JobsDirector Remote Systems Engineer Jobs in Texas

Director Remote Systems Engineer information

What does a director remote systems engineer do?

A Director Remote Systems Engineer is responsible for overseeing the design, implementation, and maintenance of remote IT systems within an organization. This role combines leadership responsibilities with technical expertise, ensuring that remote infrastructure such as servers, networks, and cloud platforms operate efficiently and securely. The director manages a team of engineers, develops strategies for remote system integration, and ensures compliance with security standards. They also collaborate with other departments to meet organizational goals and support remote work initiatives.

What is the difference between Director Remote Systems Engineer vs Remote Systems Engineer?

AspectDirector Remote Systems EngineerRemote Systems Engineer
CredentialsBachelor's/Master's in Computer Science or related, certifications like Cisco, MicrosoftBachelor's in Computer Science or related, certifications like Cisco, Microsoft
Work EnvironmentOversees teams, strategic planning, high-level project managementHands-on technical work, system setup, troubleshooting
Employer & Industry UsageTech companies, large enterprises, government agenciesIT service providers, tech firms, corporate IT departments
Search & Comparison IntentLeadership, management, strategic rolesTechnical, hands-on roles

The main difference is that a Director Remote Systems Engineer focuses on leadership, strategy, and managing teams, while a Remote Systems Engineer is primarily involved in technical system setup and troubleshooting. Both roles require similar technical credentials, but their responsibilities and work environments differ significantly.

How does a director remote systems engineer typically balance leadership duties with hands-on technical responsibilities?

As a Director Remote Systems Engineer, you'll often find yourself balancing strategic leadership with direct technical involvement. While a significant portion of your time is spent guiding remote engineering teams, setting technical direction, and collaborating with other department leaders, you'll also need to stay engaged with complex system architectures, troubleshooting, and high-level solution design. The role requires strong time management skills and the ability to delegate effectively, ensuring your team can operate autonomously while you focus on overarching objectives and cross-functional collaboration. Regular check-ins, clear communication, and fostering a culture of continuous improvement are key to managing both aspects successfully.

What are the key skills and qualifications needed to thrive as a director remote systems engineer, and why are they important?

To thrive as a Director Remote Systems Engineer, you need deep expertise in systems engineering, remote infrastructure management, and a relevant degree, often supported by experience in leadership roles. Familiarity with cloud platforms (such as AWS or Azure), remote monitoring tools, cybersecurity frameworks, and certifications like CISSP or AWS Certified Solutions Architect are commonly required. Strong problem-solving, leadership, and communication skills are essential to effectively manage distributed teams and coordinate complex projects. These skills and qualities are crucial for ensuring secure, reliable, and efficient operation of remote IT systems while leading teams to deliver strategic business outcomes.
What are the most commonly searched types of Remote Systems Engineer jobs in Texas? The most popular types of Remote Systems Engineer jobs in Texas are:
Director Remote Systems Engineer jobs near you

RHEL Systems Engineer

ASCENDING LLC

Houston, TX • On-site, Remote

Full-time

Posted 18 days ago

Job description

Title: Sr. RHEL Designer/Engineer (OT/SCADA)
Location: preference for Houston, TX or in Miami, FL, Houston, TX or Reston, VA
Term: Full Time, Direct Hire - remote but may need to travel to client locations periodically, especially at the start or kick off of a project.
Position Overview
Our client delivers turnkey clean energy and power infrastructure solutions across the Americas. We design, build, and operate advanced Battery Energy Storage Systems (BESS) and mission-critical networks for data centers, utilities, and industrial clients. Our technology-first mindset powers systems from SCADA to cloud-and everything in between.
About The Position
The Senior RHEL engineer will own the OS and container platform behind our on-premises energy-management deployments. You'll build and harden the tailored RHEL image and the containerized Ignition SCADA workload running on industrial PCs across U.S. data-center sites, and act as our deep RHEL authority and L3 escalation point. This is a platform-engineering and expertise role - not field installation.
You will own our OS architectures, container builds and configuration, and the runtime that hosts Ignition, while the SCADA team owns everything configured inside Ignition (tags, screens, logic). On the network side, the host firewall and OS-level networking (interfaces, routing, DNS, firewalld/nftables) are yours, while the physical and site network beyond the host NIC belongs to Operational Technology (OT).
Travel to third-party data-center sites is for troubleshooting and support only. The separate OT team commissions and deploys every machine, so you won't install systems in the field.
Responsibilities:
  • Build, version, and maintain a reproducible, turnkey RHEL image tailored to the SCADA host's needs (time sync, firewall/ports, storage, service ordering, resource tuning).
  • Own the SCADA container image end to end: Containerfile, base image, JVM, persistence, ports, hardening, scanning, and registry.
  • Run containers as systemd services via Podman and quadlets.
  • Harden the OS and images to a recognized baseline (CIS/STIG) and define a patching and lifecycle strategy for OT uptime and restricted/disconnected sites (offline/mirrored registry).
  • Troubleshoot full-stack - OS, container runtime, and application runtime behavior - remotely and on-site, handing off application-level issues to the SCADA team.
  • Own host-level networking and firewall configuration (interfaces, routing, DNS, firewalld/nftables, and port exposure for the SCADA container), and lead connectivity troubleshooting between the host and site infrastructure.
  • Document runbooks for the OT team and help define the connectivity and security posture.
  • Maintain the Windows image pipeline (Packer-based) in steady state once established: periodic patching, hardening updates, and image rebuilds.

Qualifications
  • 7+ years of senior, hands-on production RHEL/Linux engineering.
  • Container-native delivery: Podman, quadlets/systemd, building and owning container images (including packaging a JVM-based app such as Ignition), and registry management.
  • Reproducible, turnkey, versioned RHEL image building (bootc, Kickstart, Image Builder/osbuild, or Ansible-driven).
  • OS and image hardening to a recognized baseline (CIS/STIG).
  • Patch and lifecycle management for restricted/disconnected environments, including offline/mirrored content and registries.
  • Automation (Ansible) and version control.
  • Strong Linux networking and diagnostics: firewall administration (firewalld/nftables) and packet/connectivity tooling (Wireshark, tcpdump, ss, ip), plus containerized debug environments (toolbox).
  • Confidence operating as the RHEL authority, with strong documentation habits.

Apply