# Rust Skills Test and Verified Rust Score > A Rust skills test on ownership, lifetimes and traits, plus live sessions with practitioners and connected GitHub crates. See what proves Rust skills. Source: https://getlemma.io/skills/rust Rust experience is hard to judge from a CV because so much of the skill is invisible: knowing why the compiler objects and what to change. Lemma records that reasoning in live sessions and adaptive assessments. How Rust is assessed ## What Rust competence looks like A competent Rust developer reads compiler errors as design feedback. When the borrow checker objects, they restructure ownership instead of cloning everything or reaching for unsafe. They model state with enums so invalid states cannot be represented, and they use Result and the question mark operator to keep error paths explicit. They know the cost of their abstractions. They choose between Box, Rc and Arc deliberately, understand when trait objects or generics fit, and can explain what an async runtime is doing. Unsafe code, when it appears, is small, documented and wrapped in a safe interface with tests around it. ### Ownership and borrowing Moving, borrowing and lifetimes, and restructuring code when the borrow checker rejects it. ### Traits and generics Defining traits, using trait bounds and choosing between static dispatch and trait objects. ### Error handling Result, Option, custom error types and propagating errors without hiding their cause. ### Enums and pattern matching Modelling state so invalid combinations do not compile, with exhaustive matches. ### Async Rust Futures, async runtimes, Send and Sync bounds, and avoiding blocking inside async tasks. ### Unsafe and FFI Keeping unsafe blocks minimal, upholding invariants and wrapping them in safe APIs. ## What counts as evidence of Rust skills? A line on a CV saying Rust is a claim. A reviewed session, an assessed level or a repository linked from your account is evidence. These are the kinds Lemma records against your Rust skill, each with where it came from. See the [evidence methodology](https://getlemma.io/methodology#evidence-types) for how each source is weighed. [Live session](https://getlemma.io/product/sessions) ### Resolving a borrow checker error live A practitioner hands you code that will not compile and watches you restructure it. Your explanation of why the compiler objected matters as much as the fix, and they rate both. [Adaptive assessment](https://getlemma.io/product/assessments) ### Rust scenario questions Adaptive multiple-choice questions cover ownership, lifetimes and trait behaviour. Some show code the compiler rejects and ask you to pick the correct fix. Harder questions count for more. [GitHub connector](https://getlemma.io/product/passport) ### A crate or project on GitHub Connect a repository or commit for a crate, a CLI or a service you wrote in Rust. Lemma confirms the repository exists and your account has access to it. [AI tutor practice](https://getlemma.io/product/ai-tutor) ### Ownership practice drills Short AI tutor exercises on moves, borrows and lifetimes build fluency. They are practice evidence, so they add a small, capped amount rather than standing in for proof. ## How is a Rust skills test run on Lemma? The Rust test runs 15 to 25 questions and adjusts difficulty to your answers, with scenarios from services under real load. The result counts alongside sessions and linked repositories toward your Rust SCI, which favours recent evidence over old. [How the SCI score is calculated](https://getlemma.io/product/sci)[How adaptive skills assessments work](https://getlemma.io/product/assessments)[Practise Rust in live skill swap sessions](https://getlemma.io/product/sessions)[Which evidence types count](https://getlemma.io/methodology#evidence-types)[What your Skills Passport shows](https://getlemma.io/product/passport) 1. ### Build fluency with drills The AI tutor gives you ownership, trait and error-handling exercises that get harder as you improve. It rejects repeated answers and rushed submissions, and its results stay a small, capped part of your score. 2. ### Work through code with a peer In a live session, refactor or review Rust with a practitioner. They see how you respond to compiler errors and rate the session, which is recorded as evidence for Rust. 3. ### Take the Rust assessment Answer adaptive scenario questions, some asking why a snippet will not compile. Harder ones count for more. You cannot go back to change answers, and each question has its own time limit. ## Rust skills: common questions ### How do I show I can write production Rust and not just pass tutorials? Production Rust shows up in decisions: how you model errors, structure ownership across modules and handle async. Discuss a real project in a live session so a practitioner can probe those decisions, connect the repository, and pass the adaptive assessment. That combination says more than a list of finished tutorials. ### What Rust concepts do assessments focus on? Ownership, borrowing and lifetimes come first, because most Rust bugs and compile errors trace back to them. Questions also cover traits and generics, error handling with Result, pattern matching and async behaviour. Some questions show a snippet and ask you to choose the change that makes it compile and behave correctly. ### Is Rust evidence useful if most jobs ask for another language? Yes. Rust evidence signals that you think carefully about memory, concurrency and correctness, which transfers to systems work in Go, C++ or backend services. On your Passport it sits alongside your other skills, so a hiring team sees it as depth rather than a replacement. ### Can I use open source Rust contributions as proof? You can connect a specific GitHub commit as well as a whole repository, so a merged contribution to someone else's crate counts. Lemma checks the commit exists and your account has access. External proofs are capped, so pair them with sessions and an assessment for a complete record. ## Skills related to Rust [Browse the skills directory](https://getlemma.io/skills) [### System design Show how you reason about scale, failure and trade-offs, in live design sessions reviewed by practitioners. Evidence for system design](https://getlemma.io/skills/system-design)[### Go Prove you write clear, concurrent Go services, with evidence from live code and connected repositories. Evidence for Go](https://getlemma.io/skills/golang)[### Cybersecurity Evidence of how you find, prioritise and fix real security risks in systems and code. Evidence for cybersecurity](https://getlemma.io/skills/cybersecurity)[### Blockchain development Evidence of how you design, test and secure smart contracts, judged by practitioners in live sessions. Evidence for blockchain development](https://getlemma.io/skills/blockchain) ![Painting of an olive grove in soft sunlight with hills beyond](https://cdn.sanity.io/images/islu4peo/production/613eb3f93566423c9adf45246f2cf1a61437c04c-1680x1120.jpg?w=1080&fm=webp&q=68&fit=max) ## Start your Rust evidence record. Lemma is in early access. Request an invite and we will email you when your place is ready.