BeyondTrust logo

BeyondTrust

Staff Software Development Engineer – Linux Endpoint

Region Restricted

Remote work allowed only within certain countries or regions.

Employer listed it 6 weeks ago · Added 5 days ago

Been open since 6 weeks ago, still being checked, but it has been live a while.

Salary

Not stated

Location

Timezone

US East

Contract

Full-time

Experience

Lead

Category

Software

This employer didn't state pay. Jobs like this usually pay around $200k–$275k a year, a typical range taken from 596 lead-level software roles on Nomaders that do state pay. It's a guide, not an offer.

Remote flexibility

Region Restricted

Remote work is allowed, but only for candidates based in Canada, United States.

What the employer says

  • Source listing states candidate location: "Remote Canada | Remote United States, Remote Canada, Remote United States"

What Nomaders makes of it

  • Applications outside the listed area are usually rejected
  • Timezone overlap with the listed area is often expected

The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.

About the role

Diversity. Inclusion. They’re more than just words for us. They are the guiding values of how we build our teams, cultivate leaders, and create a culture where people feel connected.

We take care of our employees so they can take care of our customers. Customers who come from all walks of life just like us. We hire incredible people from diverse backgrounds because when we are different together, we are stronger together.

The Role

As Staff Software Development Engineer, you'll be the Linux kernel authority for the runtime enforcement layer of our Identity Security Platform. These components decide, in-kernel, whether to permit or deny each action an identity or AI agent attempts on a Linux endpoint.

You'll set the technical direction for eBPF enforcement on Linux and own it end to end. That means hooks that make the right call in real time, across the fleet, without breaking legitimate workloads. Peer engineers own the macOS and Windows enforcement surfaces. You share one policy language, one event schema, and one userspace agent with them, but Linux kernel-space is yours.

You know this layer better than anyone. You want your code to be the thing that stops a compromised credential or a runaway AI coding agent before it impacts production.

What You’ll Do

Design, build, and own our eBPF programs and BPF LSM hooks (bprm_check_security, file_open, socket_connect). You'll enforce policy synchronously in the kernel by returning -EPERM to block, rather than logging after the fact, and you'll build the userspace agent that loads and drives them.

Own the kernel/userspace enforcement boundary: kernel-side event capture over ring buffers, policy evaluation in userspace, and deny decisions pushed back into the kernel as hash-keyed caches so subsequent hits block inline.

Drive down enforce-mode latency on the syscall hot path as we scale across large fleets. That means process enrichment, binary-hash caching and eviction under heavy fork/exec pressure, and process-ancestry resolution.

Extend enforcement into containers and namespaces: cgroup- and namespace-aware policy, container identity on kernel events, Kubernetes workloads. Most of this is greenfield, and it sits at the center of the role.

Harden portability across kernel versions and distributions so enforcement loads and behaves correctly on the kernels customers actually run. You'll work with BTF-driven struct-offset discovery, LSM availability detection, tracepoint-ABI drift, and graceful fallback.

Partner with the macOS and Windows enforcement engineers and the policy-backend team on the shared plane: policy semantics, cross-stack conformance, event schema, the common Rust agent. You'll represent Linux in cross-org architecture reviews.

Read requirements to find gaps and risks, propose simplifications, and explain tradeoffs to technical and non-technical stakeholders.

Raise the engineering bar. You'll take end-to-end ownership from design through production, and you'll carry extra weight where a kernel bug means a wrong security decision instead of just a crash.

Mentor senior and mid-level engineers on Linux systems and eBPF craft

What You’ll Bring

This is a Linux specialist role, so the depth requirements are real:

Deep Linux kernel internals - scheduling, memory management, the networking stack, syscalls, the LSM framework - backed by production systems programming in C, Rust, or both.

Hands-on eBPF for security enforcement, with real comfort at the verifier level. You can write programs that pass BPF_PROG_LOAD across kernel versions and reason about the stack limit, bounded loops, and helper-behavior differences. We write our BPF in Rust (aya / aya-ebpf, no_std). Any eBPF stack transfers - libbpf, BCC, Cilium eBPF, aya - but verifier fluency is non-negotiable.

BTF and CO-RE, plus the practical realities of portability: task_struct layout drift, LSM config availability, tracepoint ABI.

Container runtime internals - namespaces, cgroups, seccomp - and how they intersect with kernel-level security tooling.

Kernel debugging and performance tooling: perf, ftrace, bpftrace, gdb/kgdb, crash-dump analysis.

8+ years in systems-level software engineering, with real depth in Linux kernel development and eBPF.

Requirements

  • ·This is a Linux specialist role, so the depth requirements are real:
  • ·Deep Linux kernel internals - scheduling, memory management, the networking stack, syscalls, the LSM framework - backed by production systems programming in C, Rust, or both.
  • ·BTF and CO-RE, plus the practical realities of portability: task_struct layout drift, LSM config availability, tracepoint ABI.
  • ·Container runtime internals - namespaces, cgroups, seccomp - and how they intersect with kernel-level security tooling.
  • ·Kernel debugging and performance tooling: perf, ftrace, bpftrace, gdb/kgdb, crash-dump analysis.

Benefits

No benefits package published with this listing. Ask about it at first interview.

How to apply

  1. 1Check the flexibility label above, region restricted, matches where you plan to live and work.
  2. 2Tailor your CV to the role at BeyondTrust, mentioning your remote working experience and working hours (US East).
  3. 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.

Found 5d ago. Last checked 23 Sept. Always confirm the details on the original posting, salary and location can change after publication.

Listing sourced from Company boards.

Similar roles

Other open software roles with comparable remote rules.

Browse all open roles

Free to apply, no account needed.

Typically $200k to $275k per year · You'll be taken to the employer's careers page.