Senior Rust Developer — Qt Bridge for Rust

Qt Bridge for Rust lets developers build Qt Quick / QML user interfaces with a pure-Rust backend — no C++ required. Rust types are exposed to the QML engine through attribute macros that generate the QMetaObject-level plumbing at compile time. The library is built on CXX and CXX-Qt for the C++/Qt interop layer. You'll join the in-house Qt Bridge for Rust team to help design, implement and harden this library. The team already owns deep Qt platform expertise — the meta-object system, C++/QML engine internals, code generation. The backlog is public, so you can see exactly what you'd be working on before you apply.

• Senior-level Rust experience in production: ownership/borrowing, Rc/RefCell/Weak, unsafe and aliasing rules, Pin, lifetime-parameterised APIs
• Rust ↔ C++ FFI experience, ideally with cxx for designing safe Rust wrappers over C++ object lifetimes
• Procedural macro development experience using syn, quote, proc-macro2, with focus on compile-error diagnostics
• Experience designing and stabilizing public library APIs with idiomatic Rust, semver, and deprecation practices
• Cross-platform Rust build engineering including build.rs and linking native libraries on Linux, MSVC, and macOS
• Strong testing and quality habits: tests with every change, clean cargo fmt / clippy, documented safety arguments for any unsafe, rustdoc on public API
• Comfortable with threat modelling and security review for systems-level, memory-unsafe-adjacent code
• Working knowledge of Qt 6 (QObject, properties, signals/slots, QVariant/QMetaType, QML object ownership) and proficiency in C++17 to read/modify the bridge's C++ layer
• Comfortable with Gerrit-style, small-commit, review-heavy workflows
• Professional written and spoken English

Nice to have:

• Prior contributions to Qt, CXX-Qt, qmetaobject-rs, or similar binding projects
• Experience in QML / Qt Quick application development
• Published crates on crates.io
• Familiarity with rcc, Qt resource handling, or QML debug/preview protocols
• Async Rust experience (e.g., tokio) integrated with a native event loop
• Existing Qt Account / Qt Contributor Licence Agreement already signed

• 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 including semver, breaking-change management, and deprecation policy
• Contribute to structured threat analysis and security review of the Rust/C++ FFI surface
• Maintain the workspace across Linux, MSVC, and macOS platforms
• Participate in code review via Gerrit and collaborate closely with a Qt maintainer
• Keep Jira issues current and communicate daily with the team through chat and email with weekly sync calls

What's NOT part of this role:

• Changes to Qt itself (qtbase, qtdeclarative) — owned by Qt's module teams
• Product management, roadmap or release ownership
• End-user support or community management