1

Rust Linux Kernel Jobs in League City, TX (NOW HIRING)

Rust Linux Kernel information

See League City, TX salary details

$86.5K

$127.7K

$150.8K

How much do rust linux kernel jobs pay per year?

As of Aug 30, 2026, the average yearly pay for rust linux kernel in League City, TX is $127,685.00, according to ZipRecruiter salary data. Most workers in this role earn between $116,900.00 and $141,300.00 per year, depending on experience, location, and employer.

What is a Rust Linux Kernel developer?

Rust Linux Kernel developers are software engineers who contribute to the Linux kernel using the Rust programming language. They focus on writing new kernel modules or components in Rust, aiming to improve safety, security, and maintainability compared to traditional C code. These developers typically have a deep understanding of both systems programming and the Linux kernel architecture. Their work is part of an ongoing effort to gradually integrate Rust into the kernel alongside existing C code.

What are the key skills and qualifications needed to thrive as a Rust Linux Kernel developer?

To thrive as a Rust Linux Kernel Developer, you need deep knowledge of systems programming, strong proficiency in Rust and C, and experience with Linux kernel internals. Familiarity with build systems (e.g., Make), version control (Git), and relevant certifications such as Linux Foundation Certified Engineer are typically valuable. Excellent problem-solving skills, attention to detail, and effective collaboration are essential soft skills in this role. These abilities ensure robust, secure, and maintainable kernel contributions while facilitating smooth teamwork in complex open-source environments.

What are some common challenges faced when working on Rust integration within the Linux kernel, and how do teams typically address them?

A frequent challenge in this role is bridging the gap between Rust and the existing C-based Linux kernel codebase. This includes ensuring memory safety, managing interoperability between the two languages, and adhering to strict kernel coding standards. Teams often address these challenges through extensive code reviews, collaborative discussions on kernel mailing lists, and by actively participating in the upstream kernel and Rust-for-Linux communities. Continuous learning and communication are essential, as both the Rust integration and kernel development methodologies are rapidly evolving.

What is the difference between Rust Linux Kernel vs C Linux Kernel Developer?

AspectRust Linux KernelC Linux Kernel Developer
Required CredentialsKnowledge of Rust programming, Linux kernel basicsProficiency in C, Linux kernel development experience
Work EnvironmentContributing to Linux kernel modules using Rust, Linux environmentDeveloping and maintaining Linux kernel code in C
Industry UsageEmerging in kernel development, experimental projectsStandard in Linux kernel development
Common Search/ComparisonOften compared for language choice in kernel modulesTraditional role, baseline for kernel development

The main difference between a Rust Linux Kernel developer and a C Linux Kernel Developer lies in the programming language used. Rust developers focus on leveraging Rust's safety features for kernel modules, while C developers work with the traditional C language. Both roles require Linux kernel knowledge, but Rust is newer and less widespread in kernel development, making it an emerging area compared to the well-established C role.

What are popular job titles related to Rust Linux Kernel jobs in League City, TX?

For Rust Linux Kernel jobs in League City, TX, the most frequently searched job titles are:

What cities near League City, TX are hiring for Rust Linux Kernel jobs?

Cities near League City, TX with the most Rust Linux Kernel job openings:

Staff Platform Engineer - Developer Infrastructure

Houston, TX • On-site

$140 - $190/hr

Other

Medical, PTO

Posted 6 days ago


Job description

Job Title: Staff Platform Engineer - Developer Infrastructure

Department: Software

Employment Type: Full-Time

Location: Houston, TX

Travel: 10%

Who We Are

Persona AI is building humanoid robots for the most demanding environments in heavy industry — shipyards, steel mills, fabrication facilities, and offshore platforms — performing welding, grinding, maintenance, inspection, and material‑handling work that is dangerous, physically demanding, and increasingly difficult to staff.

We are backed by leading strategic and financial investors and engaged with global industrial leaders across Korea, Japan, the United States, and Singapore. Korea is the center of gravity for our early commercial strategy, anchored by relationships with the world’s leading shipbuilders and steelmakers. Our work spans both the robot platform itself and the systems, partners, and playbooks required to deploy it at scale.

Why Join Persona AI?
  • We offer competitive compensation, a performance‑based bonus, 99% employer covered medical benefits, early‑stage equity, competitive PTO, and a company‑wide paid winter break between December 24th and January 2nd.

  • You’ll shape technology that’s redefining the possibilities of robotics and human interaction.

  • Work alongside passionate teammates who value creativity, and continuous learning.

About the Role

Our robots are built by a small team that ships fast and deploys onto hardware in customer facilities. Between a laptop and a running humanoid there are: a C++/Python/Rust monorepo, an ARM64 cross‑compile matrix, kernel modules and a real‑time patch set, container images that have to land on Jetson devices, and a rollout process that cannot brick a robot several timezones away.
Today that path is held together by the engineers who also write control code. Your job is to own it so they don’t have to. Success is measured in build times, time‑to‑first‑commit for a new engineer, deployment frequency, and the number of infrastructure problems the rest of the team stops thinking about.

This is not a cloud‑only role. Roughly half the surface area is physical: lab networks, robot dev boxes, bench and HIL fixtures, on‑site LAN infrastructure, and the mirrors that let a deployment site work with no internet at all.

What You Will Be Doing

Build and CI

  • The build graph for a mixed C++/Python/Rust/CUDA monorepo: involving incremental correctness, remote caching, and cross‑compilation for AMD64 dev boxes and ARM64 targets.

  • Our CI capacity: self‑hosted runners, GPU and hardware‑attached runners, and the queue discipline that keeps PR feedback under ten minutes.

  • Reproducibility: A build from a tagged commit six months from now should produce a bit‑identical artifact.

Release and fleet delivery

  • Versioning, artifact promotion, and the container registry / package mirrors that back it.

  • Safe, resumable, bandwidth‑aware rollout to robots - staged channels, canary robots, and rollback that works over a bad link.

  • Signing and provenance for anything that lands on a robot.

Developer platform

  • Reproducible dev environments across laptops, shared dev machines, and robots.

  • Self‑service tooling so an autonomy engineer can get a branch onto a robot without filing a ticket or learning Kubernetes.

  • Onboarding path: a new engineer builds, tests in sim, and deploys to a bench robot on day one.

Infrastructure and observability

  • Cloud and on‑prem compute, storage for multi‑TB robot logs, and the training/simulation cluster's operational layer.

  • Fleet observability: metrics, logs, and traces from robot to dashboard.

  • Site infrastructure for deployments: VPN/overlay networking, local mirrors, offline‑capable registry authorization.

What We Are Looking For
  • 8+ years operating production infrastructure for a software engineering org, with direct ownership of CI/CD or developer platform work.

  • Deep Linux systems fluency including networking, storage, systemd, kernel and driver debugging.

  • Hands‑on ownership of a major CI system (GitHub Actions, GitLab CI, Buildkite, Jenkins) and an understanding of the build and cache layers underneath it.

  • Real experience with a C/C++ build system at scale e.g., Bazel, CMake, or equivalent. Should include cross‑compilation and dependency pinning.

  • Infrastructure as code (Ansible, Terraform) and a GitOps mindset: reviewable, reproducible, version‑controlled change.

  • Fluent Python and Bash. You automate rather than document a manual procedure.

  • Strong written communication. You leave behind decisions that outlast the conversation.

Bonus Skills
  • Shipping software to embedded or edge Linux targets - ARM64, Jetson, Yocto/custom images, A/B partitions, OTA update systems.

  • Hybrid on‑prem plus cloud, and clear judgment about which belongs where.

  • Open‑source observability stack (Prometheus, Grafana, OpenTelemetry) and self‑hosted services (registries, artifact stores, object storage).

  • Robotics, autonomous vehicles, aerospace, or another hardware‑heavy environment where a bad release has physical consequences.

  • Nix, Bazel remote execution, or other tools for reproducible builds at scale.

Persona AI is an Equal Opportunity Employer.

All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, age, disability, veteran status, or any other characteristic protected by applicable federal, state, or local law.

#J-18808-Ljbffr