Senior Runtime Systems Engineer

About the role

This position centers on the design and execution of runtime firmware that orchestrates on-chip multi-core CPU subsystems to dictate the runtime behavior of silicon products. You will own the definition, architectural decisions, and documentation that ensure the runtime firmware aligns with D Matrix product objectives and delivery timelines. A core part of this role involves validating software against D Matrix coding and methodology guidelines while actively driving performance, reliability, and efficiency of the runtime stack. You will act as a bridge between hardware and software, collaborating closely with hardware engineers, hardware verification engineers, and software team members to dissect and resolve complex system-level issues. The position demands clear technical communication, as the ability to explain intricate runtime decisions in plain language is essential for success. You will spend part of each week on planning, code review, debugging, and refining the runtime firmware to meet evolving product requirements. Success in this role means delivering quality code on schedule and continuously improving the development practices that govern runtime software delivery.

Key facts

What you'll do

Architect, document, and develop runtime firmware executed in on-chip multi-core CPU subsystems to define the runtime behavior of the silicon product.

Determine delivery schedules and validate that software meets D Matrix coding and methodology guidelines while driving runtime performance of the silicon product.

Collaborate with hardware engineers, hardware verification engineers, and software team members to debug complex problems and deliver quality code.

Perform Linux system-level programming, including work with Linux device drivers, to ensure correct hardware interaction and stable runtime behavior.

Write proficient C/C++ code as the primary implementation language for systems components that manage AI inference workloads.

Use Python where needed to support development, testing, or automation tasks that improve verification and deployment efficiency.

Work with virtual machines and containers to manage runtime workloads and support deployment scenarios in datacenter environments.

Gain experience with containers and virtual machines to support deployment scenarios in datacenter environments, ensuring runtime flexibility.

Engage in code reviews and debugging sessions that span both hardware and software boundaries to resolve intricate issues affecting product performance.

Contribute to the Software Engineering department's goals by delivering firmware and systems software that meets D Matrix standards and timelines.

Requirements

Hold a Bachelor's in computer engineering or electrical engineering and bring a minimum of 5 years of industry experience in embedded software development.

Demonstrate strong proficiency in C/C++ as the main language for implementing runtime firmware and systems components.

Show experience with Linux system-level programming, including interaction with Linux device drivers and kernel interfaces.

Prove ability to work with virtual machines and containers to support deployment scenarios in datacenter environments.

Exhibit at least 5 years of industry experience, with a solid background in embedded software development and runtime systems.

Maintain a Bachelor's degree in computer engineering or electrical engineering from an accredited institution as a baseline educational requirement.

Display capability to debug complex problems that cross hardware and software domains while working within datrix methodology constraints.

Communicate effectively in plain language to explain technical decisions and runtime behavior to both technical and non-technical stakeholders.

Nice to have

Roles in runtime systems engineering often combine firmware, drivers, and systems software to control hardware behavior. Proficiency in C/C++ and Linux system-level programming is common for infrastructure-level positions. Experience with containers and virtual machines supports modern deployment flows. Debugging complex problems across hardware and software boundaries requires close collaboration. This role targets infrastructure software for AI inference platforms.

Practical notes

Work is hybrid, with 3 days per week onsite at the Sydney office.

The role resides within the Software Engineering department.

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Roles in runtime systems engineering often combine firmware, drivers, and systems software to control hardware behavior. Proficiency in C/C++ and Linux system-level programming is common for infrastructure-level positions. Experience with containers and virtual machines supports modern deployment flows. Debugging complex problems across hardware and software boundaries requires close collaboration. This role targets infrastructure software for AI inference platforms.

Questions to ask

Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made. Asking about growth paths and the review process is also well received. Employers expect questions, and good ones show preparation.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.