/ TEAMS · Linux Device Driver Engineering
Specify the device, PCIe or USB bus, DMA and interrupt behavior, kernel interfaces, target boards and validation hardware. Driver delivery is not interchangeable with application development.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
PCIe · USB · I²C · SPI
Device Tree · ACPI · Probe
Kernel modules · IRQs · DMA
sysfs · ioctl · char/net drivers
ftrace · dmesg · Test rigs
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Mid-level Linux Device Driver Engineer — PCIe / USB / DMA
Available3+ years of experience · Romania
Linux Device Driver Engineer — PCIe / USB / DMA with 3 years in production systems, focused on Linux Device Driver Engineer — PCIe / USB / DMA and Production systems.
Languages: Romanian, English B2+
Mid+ Linux Device Driver Engineer — PCIe / USB / DMA
Inquire availability6+ years of experience · Romania
Linux Device Driver Engineer — PCIe / USB / DMA with 6 years in production systems, focused on Production systems and Technical delivery.
Languages: Romanian, English B2+
Senior Linux Device Driver Engineer — PCIe / USB / DMA
Available9+ years of experience · Czechia
Linux Device Driver Engineer — PCIe / USB / DMA with 9 years in production systems, focused on Technical delivery and Linux Device Driver Engineer — PCIe / USB / DMA.
Languages: Czech, English B2+
Senior Linux Device Driver Engineer — PCIe / USB / DMA
Available12+ years of experience · Lithuania
Linux Device Driver Engineer — PCIe / USB / DMA with 12 years in production systems, focused on Linux Device Driver Engineer — PCIe / USB / DMA and Production systems.
Languages: Lithuanian, English C1
/ Specialist sourcing
Specify the device, PCIe or USB bus, DMA and interrupt behavior, kernel interfaces, target boards and validation hardware. Driver delivery is not interchangeable with application development.
Review evidence of a hardware-facing bug, including register traces, kernel logs, concurrency, memory mapping and tests across device revisions.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Our embedded and USB-related sourcing experience helps define the driver-to-hardware boundary. For a Linux driver assignment we validate the candidate's exact subsystem, supported devices, integration testing and debugging history rather than relying on broad kernel keywords.
/ Technical specializations
Unlike a general kernel role, this search centers on owning a particular device, bus interface or peripheral lifecycle and its upstream/downstream consumers.
Linux driver model, probe/remove, Device Tree, ACPI where relevant, sysfs and suspend/resume flows.
PCIe enumeration, USB interfaces, I²C/SPI transfers, register access and host-controller boundaries.
Interrupt handling, DMA mapping, locking, workqueues, memory barriers and race-condition diagnosis.
Character/block/network drivers, ioctl, netlink, udev and stable device application interfaces.
Runtime PM, suspend/resume, hot-plug events, reset/recovery paths and peripheral availability.
dmesg, ftrace, KASAN/lockdep, kernel selftests, lab fixtures and kernel-version compatibility.
/ Project scenarios
Implement probe, register configuration and safe userspace interfaces against a specific board.
Trace interrupts, memory mapping and concurrency under realistic workload and hardware conditions.
Recover from device resets and state transitions across boards and kernel versions.
Adapt APIs, Device Tree bindings, tests and backports without breaking the device lifecycle.
/ Practical evaluation
A specialist should be able to explain probe sequences, error handling, IRQ/DMA lifecycles and how they confirmed behavior on physical hardware.
Which devices did they support, how were probe/remove, reset and suspend/resume handled?
Can they explain PCIe or USB interactions, DMA safety, IRQ threading and synchronization?
Can they interpret a failing trace, crash report, kernel log or real hardware reproduction?
How were bindings, APIs, backports, kernel upgrades and regression rigs maintained?
/ Sourcing process
Chipset, bus, kernel baseline, board revisions, driver ownership and physical-lab access.
Search systems engineers and hardware-facing recruiting channels with relevant device history.
Assess probe/IRQ/DMA experience, debugging workflows and compatibility changes.
Coordinate hardware, security, timezone, availability, reviews and release responsibility.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Device-driver hiring concentrates on a specific peripheral, bus, binding, lifecycle and hardware test environment; general kernel work may involve scheduling, networking or memory subsystems.
Yes. Specify the hardware, transfer paths, DMA/IRQ needs, kernel version and expected userspace interface.
Yes. Distinguish protocol/enumeration ownership from Linux interface or host-controller driver work so candidate screening is precise.
Often, especially for bring-up, timing or power-state issues. We coordinate access requirements and remote/on-site feasibility per assignment.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.
