Senior Rust Developer

Quick Facts

• Role: Senior Rust Developer — Qt Bridge for Rust

• Focus: Build Qt Quick/QML UIs using a pure-Rust backend (no C++ required for app logic)

• Integration: Rust types exposed to the QML engine via attribute macros generating QMetaObject-level plumbing at compile time

• Interop layer: CXX and CXX-Qt for C++/Qt interop

Description

Contribute to the in-house Qt Bridge for Rust library by designing, implementing, and hardening the bridge. Work on object-model/memory-safety, type-system, and macro-related issues, stabilize a public library API, perform security review of the Rust/C++ FFI surface, and help keep the workspace green across Linux, MSVC, and macOS.

Responsibilities

• Contribute production-quality Rust (and, where needed, C++) code, tests and documentation to the QtBridge Rust repository

• Work on object-model, memory-safety, type-system and macro-related issues

• Help design and stabilize a public library API — semver, breaking-change management, deprecation policy

• Contribute to a structured threat analysis / security review of the Rust/C++ FFI surface

• Keep the workspace green across Linux, MSVC and macOS

• Go through code review via Gerrit against the dev branch, working closely with a Qt maintainer

• Keep Jira issues current and communicate daily with the team (chat/e-mail), plus a weekly sync call

What’s NOT part of this role

• Changes to Qt itself (qtbase, qtdeclarative)

• Product management, roadmap or release ownership

• End-user support or community management

Requirements

• Senior-level Rust experience in production: ownership/borrowing, Rc/RefCell/Weak, unsafe and the aliasing rules, Pin, lifetime-parameterised APIs

• Rust ↔ C++ FFI experience, ideally with cxx — designing safe Rust wrappers over C++ object lifetimes

• Procedural macro development (syn, quote, proc-macro2), with attention to good compile-error diagnostics

• Experience designing and stabilizing a public library API — idiomatic Rust, semver, deprecation practices

• Cross-platform Rust build engineering (build.rs, linking native libraries on Linux, MSVC, macOS)

• Strong testing and quality habits: tests with every change, clean cargo fmt/clippy, documented safety arguments for any unsafe, rustdoc on public API

• Comfort with threat modelling / security review for systems-level, memory-unsafe-adjacent code

• Working knowledge of Qt 6 (QObject, properties, signals/slots, QVariant/QMetaType, QML object ownership) and enough C++17 to read/modify the bridge’s C++ layer

• Comfortable with Gerrit-style, small-commit, review-heavy workflows

• Professional written and spoken English

Benefits

• Public backlog (see what you would work on before applying)

• Fully remote collaboration

• B2B project-based cooperation (duration: at least 6 months, option to extend by next 6 months)

• Technical interview (~90 min) covering Rust knowledge and, optionally, QtBridge-specific topics