Stefan V.
Senior QNX / RTOS Engineer
Inquire availability13+ years of experience · Bulgaria
QNX / RTOS Engineer with 13 years in production systems, focused on QNX Neutrino processes and priority scheduling.
Languages: Bulgarian, English B2+
/ TEAMS · Specialist engineering · QNX / RTOS
Specify QNX Neutrino version, process priorities, message-passing IPC, device drivers, watchdog and required real-time deadlines.
2,000+ engineers in our active talent network · Regional recruiters
/ SYSTEM STACK
QNX Neutrino processes
priority scheduling
message passing IPC
POSIX drivers
watchdog reliability
/ AVAILABLE TO HIRE
Profiles show the experience we can source. Individual candidate availability is confirmed after enquiry.
Senior QNX / RTOS Engineer
Inquire availability13+ years of experience · Bulgaria
QNX / RTOS Engineer with 13 years in production systems, focused on QNX Neutrino processes and priority scheduling.
Languages: Bulgarian, English B2+
Senior QNX / RTOS Engineer
Inquire availability8+ years of experience · Serbia
QNX / RTOS Engineer with 8 years in production systems, focused on priority scheduling and message passing IPC.
Languages: Serbian, English C1
Mid-level QNX / RTOS Engineer
Available3+ years of experience · Montenegro
QNX / RTOS Engineer with 3 years in production systems, focused on message passing IPC and POSIX drivers.
Languages: Montenegrin, English B2+
Mid+ QNX / RTOS Engineer
Inquire availability5+ years of experience · Serbia
QNX / RTOS Engineer with 5 years in production systems, focused on POSIX drivers and watchdog reliability.
Languages: Serbian, English B2+
/ Specialist sourcing
Specify QNX Neutrino version, process priorities, message-passing IPC, device drivers, watchdog and required real-time deadlines.
Ask for timing traces, an actual missed-deadline incident or a driver failure, including how recovery behavior was verified.
Role-specific sourcing, not a promise of current candidate availability.
/ Engineering teams
Onectus uses its active engineering network and regional recruiting partners to search against concrete systems, environments and responsibilities. We evaluate practical experience rather than treating a framework mention or certification as proof of delivery. Particular availability and engagement terms are confirmed after an enquiry. For this role, practical knowledge of QNX Neutrino processes, priority scheduling, message passing IPC helps define the engineering search.
/ Technical specializations
The right profile depends on your actual architecture, performance constraints, integration boundaries and operational responsibilities.
QNX / RTOS responsibilities include qnx neutrino processes, related priority scheduling, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
QNX / RTOS responsibilities include priority scheduling, related message passing ipc, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
QNX / RTOS responsibilities include message passing ipc, related posix drivers, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
QNX / RTOS responsibilities include posix drivers, related watchdog reliability, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
QNX / RTOS responsibilities include watchdog reliability, related real-time tracing, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
QNX / RTOS responsibilities include real-time tracing, related qnx neutrino processes, clear test coverage and a reliable production handover. Examine the actual tooling and deployment environment.
/ Project scenarios
Diagnose missed real-time deadlines. Define constraints around qnx neutrino processes, map dependencies and test how the proposed implementation behaves under real operating conditions.
Integrate a device service on QNX. Define constraints around priority scheduling, map dependencies and test how the proposed implementation behaves under real operating conditions.
Improve watchdog recovery. Define constraints around message passing ipc, map dependencies and test how the proposed implementation behaves under real operating conditions.
Port a component to a supported RTOS. Define constraints around posix drivers, map dependencies and test how the proposed implementation behaves under real operating conditions.
/ Practical evaluation
A senior engineering interview should surface directly relevant implementation details, debugging history and operational judgment.
Describe a production issue involving QNX Neutrino processes and what evidence led to a fix.
Which decisions around priority scheduling and message passing IPC were you personally accountable for?
Describe a production issue involving message passing IPC and what evidence led to a fix.
Which decisions around POSIX drivers and watchdog reliability were you personally accountable for?
/ Sourcing process
Define platform versions, deployment constraints, traffic patterns, required integrations and ownership.
Search the active network and partner channels for platform-specific engineering experience.
Discuss real systems, code or configuration decisions, troubleshooting and change control.
Confirm role boundaries, location or remote access, availability, security and interviews.
Profiles, availability and engagement terms are confirmed for each request.
/ Questions
Yes. Tell us the relevant versions, operational environment and the responsibilities connected to QNX Neutrino processes. We qualify hands-on experience during each search.
These can be included when central to the project. We distinguish practical implementation work from general familiarity and ask about failure scenarios and testing.
We look at production decisions, trade-offs, incident diagnosis, code or infrastructure ownership and the ability to explain decisions without relying on a technology checklist.
Share your architecture, technical constraints, collaboration model and priorities. We can then discuss relevant sourcing channels, evaluation criteria and next steps.
/ Onectus · TEAMS
Tell us the technology, production responsibilities, experience level and working model. We'll activate the appropriate engineering sourcing channels.