Skip to main content

Senior Linux Platform Engineer

Posted yesterday

request technologyOak Park (IL)

SENIORITY

Senior

Apply (opens in a new tab)

About the role

Senior Linux Platform Engineer
Salary: open + bonus
Location: Chicago, IL / Kansas City, MO / New York, NY
Hybrid: 4 days onsite, 1 day remote*We are unable to provide sponsorship for this role*Qualifications 5+ years of experience in Linux systems administration and infrastructure/platform engineering. Production experience managing Kubernetes, preferably in bare-metal or on-premises environments (e.g., with kubeadm, RKE, or OpenShift).Hands-on experience with cloud platforms (AWS, Azure or GCP) in production environments. Strong scripting and automation skills in Python and Bash. In-depth knowledge of Linux internals, kernel tuning, and performance diagnostics. Hands-on experience with SaltStack (preferred), Puppet, or Ansible for configuration management. Familiarity with observability tools such as Prometheus, Grafana, or Loki. Solid understanding of core infrastructure protocols and services (TCP/IP, DNS, NTP/PTP, DHCP, etc.).Experience managing CI/CD pipelines with tools such as Jenkins, GitLab, or similar.
Responsibilities: Managing and improving our Linux-based infrastructure with a focus on performance, reliability, and scalability. Designing, deploying, and maintaining on-premises Kubernetes clusters and containerized workloads. Developing and maintaining system-level software, middleware, and APIs to support internal platforms and services. Automating system workflows and infrastructure tasks using Python, Bash, and configuration management tools like SaltStack. Building and maintaining RPM packages and internal software repositories. Collaborating with Application Support (SRE), Development, and Security teams to ensure secure, automated CI/CD and platform integration. Diagnosing and resolving complex system-level issues involving the OS, network, or container runtime. Implementing hardened security configurations, including system hardening, secure communications, and identity/access integration. Participating in an on-call rotation to support critical infrastructure services. Documenting architectures, tools, and operational processes to support long-term maintainability.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this