/ TEAMS · Linux Kernel Engineering
Is the requirement a kernel module, eBPF/XDP program, memory-management defect or networking path? Specify supported kernel versions, hardware and upstream constraints.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
SoC · PCIe · USB · NIC
Subsystems · Scheduling · Memory
Kernel modules · Device Tree
eBPF · XDP · TCP/IP
ftrace · perf · BPF tooling
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior Linux Kernel Engineer — Drivers & eBPF
Inquire availability10+ years of experience · Serbia
Linux Kernel Engineer — Drivers & eBPF with 10 years in production systems, focused on Linux kernel and C.
Languages: Serbian, English C1
Mid-level Linux Kernel Engineer — Drivers & eBPF
Inquire availability3+ years of experience · Lithuania
Linux Kernel Engineer — Drivers & eBPF with 3 years in production systems, focused on C and Debugging.
Languages: Lithuanian, English B2+
Mid+ Linux Kernel Engineer — Drivers & eBPF
Inquire availability6+ years of experience · Slovakia
Linux Kernel Engineer — Drivers & eBPF with 6 years in production systems, focused on Debugging and Linux kernel.
Languages: Slovak, English B2+
Senior Linux Kernel Engineer — Drivers & eBPF
Available11+ years of experience · Croatia
Linux Kernel Engineer — Drivers & eBPF with 11 years in production systems, focused on Linux kernel and C.
Languages: Croatian, English B2+
/ Specialist sourcing
Is the requirement a kernel module, eBPF/XDP program, memory-management defect or networking path? Specify supported kernel versions, hardware and upstream constraints.
Ask how the specialist isolated a race, regression or kernel crash using tracing, perf, sanitizers, bisecting and reproducible tests.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Our embedded and USB-related recruiting context supports technically focused searches at the hardware/software boundary. A Linux kernel engagement is assessed separately for the subsystem, upstream versions, test hardware and security/operational constraints. Kernel expertise is assessed for the exact subsystem, kernel version, device and debugging work you require.
/ Technical specializations
Kernel work is diverse: platform drivers, networking, observability and internals require different evidence and interview approaches.
Processes, scheduling, memory management, synchronization primitives and resource ownership.
Character/block/network drivers, PCIe/USB, IRQs, DMA, kernel modules and driver lifecycle.
BPF programs, verifier constraints, XDP/TC attachment, maps, perf events and network observability.
Sockets, netfilter, TCP/IP, packet processing, performance bottlenecks and driver data paths.
ftrace, perf, bpftrace, crash dumps, kernel logs and reproducible latency investigations.
Device Tree, Kconfig, patch/backport workflows, CI tests, compatibility and secure release discipline.
/ Project scenarios
Own interfaces, DMA/interrupt behavior, test rigs and compatibility across kernel versions.
Use tracing to isolate scheduler, lock, memory or networking behavior.
Design safe probes with correct verifier constraints and minimal runtime overhead.
Plan kernel versions, patches, Device Tree integration and regression coverage.
/ Practical evaluation
Kernel seniority comes from real failure analysis, code review and understanding the consequences of changes in privileged execution paths.
What driver, memory, scheduler or network subsystem has the engineer personally changed?
Can they explain a trace, reproducer, kernel oops, lockdep report or regression?
Do they understand verifier limits, hook choice, XDP/TC costs and measurement bias?
How do they test/backport patches, handle API changes and prevent regressions?
/ Sourcing process
Kernel version, hardware, drivers, eBPF hooks, real-time needs and test infrastructure.
Search systems engineers and specialized Linux recruiting networks.
Assess debugging, tracing, patching, tests and actual subsystem ownership.
Confirm device access, upstream requirements, security clearance and working model.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Specify whether the work involves observability, packet filtering, data-plane acceleration, a driver or kernel TCP/IP behavior.
Yes. Share the chipset, bus (USB/PCIe/I²C/SPI), kernel baseline, hardware access and expected responsibilities.
Some kernel debugging and device-driver work requires hardware or lab access; trace analysis and software integration may be remote.
Kernel developers write and debug privileged code and subsystems, whereas operations engineers focus on deployment and runtime management. We screen to the actual role.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
