Senior Rust Developer – Qt Bridge for Rust

This is a fully remote position, open to applicants in Poland.

📋 Description

• Contribute production-quality Rust code and, when necessary, C++ code, tests, and documentation to the QtBridge Rust repository.

• Address issues related to object-model, memory safety, type systems, and macros.

• Assist in the design and stabilization of a public library API, including semantic versioning, management of breaking changes, and deprecation policies.

• Engage in structured threat analysis and security reviews of the Rust/C++ foreign function interface (FFI) surface.

• Ensure the workspace remains operational across Linux, MSVC, and macOS platforms.

• Participate in Gerrit code reviews for the development branch in collaboration with a Qt maintainer.

• Maintain up-to-date Jira issues.

• Communicate regularly with the team via chat and email, and attend a weekly synchronization call.

• Focus on the Qt Bridge for Rust library, facilitating pure-Rust backends for Qt Quick/QML applications.

• No involvement in changes to Qt itself, product management, roadmap or release ownership, end-user support, or community management.

⛳️ Requirements

• Extensive senior-level experience with Rust in production, including knowledge of ownership/borrowing, Rc/RefCell/Weak, unsafe and aliasing rules, Pin, and lifetime-parameterized APIs.

• Familiarity with Rust ↔ C++ foreign function interface (FFI), preferably with the cxx library.

• Experience in designing safe Rust wrappers around C++ object lifetimes.

• Proficiency in procedural macro development using syn, quote, and proc-macro2.

• Experience in designing and stabilizing public library APIs, including semantic versioning and deprecation practices.

• Knowledge of cross-platform Rust build engineering using build.rs and linking native libraries on Linux, MSVC, and macOS.

• Strong practices in testing and quality assurance, including testing with every change, utilizing cargo fmt, clippy, documented safety arguments for unsafe code, and rustdoc for public APIs.

• Comfort with threat modeling and conducting security reviews for systems-level, memory-unsafe-adjacent code.

• Working understanding of Qt 6, encompassing QObject, properties, signals/slots, QVariant/QMetaType, and QML object ownership.

• Sufficient knowledge of C++17 to read and modify the bridge's C++ layer.

• Familiarity with Gerrit-style workflows that involve small commits and heavy reviews.

• Proficient in written and spoken English.

• Completion of a technical interview lasting approximately 90 minutes.

• Nice to have: prior contributions to Qt, CXX-Qt, qmetaobject-rs, or similar binding projects.

• Nice to have: experience in QML / Qt Quick application development.

• Nice to have: published crates on crates.io.

• Nice to have: familiarity with rcc, Qt resource management, or QML debug/preview protocols.

• Nice to have: experience with Async Rust using tokio integrated with a native event loop.

• Nice to have: an existing Qt Account / signed Qt Contributor Licence Agreement.

🏝️ Benefits

• B2B project-based cooperation.

• Contract duration of at least 6 months, with the possibility of extending for another 6 months.