Most Linux roles are about adding features.
This one is about stopping systems from failing.

If you’ve ever been the person called in after an embedded Linux device starts misbehaving in the field. Random reboots. Broken drivers. Library conflicts no one can explain. You already know what this role is.

This is not application development.
This is owning the operating system layer that decides whether the product survives.

You’ll own the Linux foundation of a production IoT device. This is engine-room work. Drivers, system libraries, boot behavior, and the boundaries where things actually break.

If you want surface-level application work, this isn’t it.
If you want ownership of the OS stack everything depends on, read on.

What You’ll Do

Platform and OS Engineering

• Build, customize, and maintain Linux-based systems for embedded and IoT devices.

• Debug driver-level issues, kernel interactions, and system-level library conflicts.

• Optimize boot time, memory usage, and overall system reliability.

• Integrate and harden system services for real-world deployment.

Security matters, but this is not a theory role. You’ll work with encryption and hardware security where required, not argue about it on a whiteboard.

Firmware and System Integration

• Own the boundary between firmware, kernel, drivers, and userspace.

• Integrate first- and third-party libraries into packaged deployments.

• Debug issues that cross firmware, OS, and application layers.

• Ensure changes in one layer do not destabilize the rest of the system.

Application and Cloud Interfaces

• Support system-level interfaces between devices and AWS services.

• Enable reliable data flow between edge devices and the cloud.

• Contribute to embedded application work when deep system knowledge is required.

What You Bring

This role is for engineers who have built Linux systems, not just used them.

You bring:

• Deep, hands-on Linux systems experience.

• Comfort working close to drivers and low-level components.

• Strong C/C++ skills. Java experience is useful where it touches native interfaces.

• The ability to debug problems that do not have clean stack traces.

• A bias toward correctness, stability, and control.

What This Role Demands

You will operate with ownership.

That means solving problems at the root, making decisions with incomplete information, and accepting that edge devices fail unless every layer is engineered properly.

If you need constant direction, this isn’t your role.
If you want control over the technical foundation of a real IoT product, it is.

Ready to own the core?

If you are the engineer people call when Linux systems misbehave, this is your seat.

You will own the platform decisions that determine whether the product survives in the field or quietly fails. Your work will be felt in every boot and every failure that never happens.

This is not a role for tourists or feature chasers.
It is for engineers who want control, accountability, and authority.

Step in if you want real ownership.

Apply Now

📧 lance@runtimerec.com
☎️ 03 9005 2123