Rust: market
Data as of November 19, 2026: 80 open Rust jobs, 55% remote among jobs that state a work format; median advertised salary $8,016/mo (from 7 postings that state a salary). Source: Zorky, updated daily.
Rust Backend — low-level server-side development in Rust: performance-critical systems, low-latency APIs, system-level tooling, blockchain (Solana/Substrate). The fastest-growing low-level backend segment 2024–2026 thanks to memory safety without GC + zero-cost abstractions. Role family: Rust Backend Engineer (general — REST/gRPC API + Tokio async), Rust Systems Engineer (CLI tools, databases, OS tooling), Rust Blockchain Engineer (Solana smart contracts + Substrate — separate niche with canonical /research/blockchain), Rust Embedded Engineer (IoT, firmware — separate branch). Stack: Rust edition 2021 (must) or 2024, Tokio (async runtime — dominator), web: Axum (modern, Tokio-native) or Actix-web (mature performance), SQLx (async + compile-time SQL checks) or SeaORM, PostgreSQL, Redis, gRPC (tonic), Kafka (rdkafka), Cargo (must), cargo-watch + cargo-nextest + cargo-tarpaulin (testing/coverage), Docker+Kubernetes. Top stack: rust, python, c++, go, cloud. Among jobs with a stated work format, 55% are remote.
Data as of:
Key numbers for the Rust market: open jobs, median salary, observed talent pool and remote share.
The Rust market currently has 80 open roles, 70 of them freshly observed. Median salary $8,016/mo.
Among jobs with a stated work format, 55% are remote. The Rust community is very remote-friendly. Tinkoff — remote-friendly.
⚠ salary known for 7 of 80 jobs; remote share from 66 with a stated format; 70 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Rust postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 6 |
| 2026-06-08 | 1 |
| 2026-06-15 | 8 |
| 2026-06-22 | 12 |
| 2026-06-29 | 10 |
| 2026-07-06 | 13 |
| 2026-07-13 | 12 |
| 2026-07-20 | 6 |
| 2026-07-27 | 9 |
| 2026-08-03 | 4 |
| 2026-08-10 | 8 |
| 2026-08-17 | 9 |
| 2026-08-24 | 1 |
| 2026-08-31 | 7 |
| 2026-09-07 | 6 |
| 2026-09-14 | 5 |
| 2026-09-21 | 18 |
| 2026-09-28 | 11 |
| 2026-10-05 | 15 |
| 2026-10-12 | 48 |
| 2026-10-19 | 11 |
| 2026-10-26 | 12 |
| 2026-11-02 | 17 |
| 2026-11-09 | 15 |
Active sources per week
Sources over the period: 73. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 4 |
| 2026-06-08 | 1 |
| 2026-06-15 | 7 |
| 2026-06-22 | 5 |
| 2026-06-29 | 8 |
| 2026-07-06 | 9 |
| 2026-07-13 | 12 |
| 2026-07-20 | 6 |
| 2026-07-27 | 9 |
| 2026-08-03 | 4 |
| 2026-08-10 | 6 |
| 2026-08-17 | 7 |
| 2026-08-24 | 1 |
| 2026-08-31 | 6 |
| 2026-09-07 | 3 |
| 2026-09-14 | 4 |
| 2026-09-21 | 9 |
| 2026-09-28 | 6 |
| 2026-10-05 | 7 |
| 2026-10-12 | 20 |
| 2026-10-19 | 9 |
| 2026-10-26 | 7 |
| 2026-11-02 | 8 |
| 2026-11-09 | 13 |
New sources connected: Jun 29 +6 · Jul 6 +7 · Jul 27 +6 · Oct 12 +8 · all weeks (20) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 1 |
| Jun 15 | +5 | 8 |
| Jun 22 | +3 | 12 |
| Jun 29 | +6 | 10 |
| Jul 6 | +7 | 13 |
| Jul 13 | +5 | 12 |
| Jul 20 | +4 | 6 |
| Jul 27 | +6 | 9 |
| Aug 3 | +1 | 4 |
| Aug 10 | +2 | 8 |
| Aug 17 | +2 | 9 |
| Aug 31 | +1 | 7 |
| Sep 14 | +1 | 5 |
| Sep 21 | +2 | 18 |
| Sep 28 | +2 | 11 |
| Oct 12 | +8 | 48 |
| Oct 19 | +4 | 11 |
| Oct 26 | +4 | 12 |
| Nov 2 | +3 | 17 |
| Nov 9 | +2 | 15 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 6 | 4 |
| 2026-06-08 | 1 | 1 |
| 2026-06-15 | 8 | 7 |
| 2026-06-22 | 12 | 5 |
| 2026-06-29 | 10 | 8 |
| 2026-07-06 | 13 | 9 |
| 2026-07-13 | 12 | 12 |
| 2026-07-20 | 6 | 6 |
| 2026-07-27 | 9 | 9 |
| 2026-08-03 | 4 | 4 |
| 2026-08-10 | 8 | 6 |
| 2026-08-17 | 9 | 7 |
| 2026-08-24 | 1 | 1 |
| 2026-08-31 | 7 | 6 |
| 2026-09-07 | 6 | 3 |
| 2026-09-14 | 5 | 4 |
| 2026-09-21 | 18 | 9 |
| 2026-09-28 | 11 | 6 |
| 2026-10-05 | 15 | 7 |
| 2026-10-12 | 48 | 20 |
| 2026-10-19 | 11 | 9 |
| 2026-10-26 | 12 | 7 |
| 2026-11-02 | 17 | 8 |
| 2026-11-09 | 15 | 13 |
Remote work over time
Share of Rust postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-22 | 80 |
| 2026-06-29 | — |
| 2026-07-06 | 63.6 |
| 2026-07-13 | 60 |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | 47.1 |
| 2026-09-28 | 90.9 |
| 2026-10-05 | 66.7 |
| 2026-10-12 | 70.6 |
| 2026-10-19 | — |
| 2026-10-26 | — |
| 2026-11-02 | 73.3 |
| 2026-11-09 | 36.4 |
The series starts on Jun 22: there is no data before that.
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | 80 |
| 2026-06-29 | — |
| 2026-07-06 | 63.6 |
| 2026-07-13 | 60 |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | 47.1 |
| 2026-09-28 | 90.9 |
| 2026-10-05 | 66.7 |
| 2026-10-12 | 70.6 |
| 2026-10-19 | — |
| 2026-10-26 | — |
| 2026-11-02 | 73.3 |
| 2026-11-09 | 36.4 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Rust.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Rust jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 80 |
| Open demand | 80 |
| Observed supply | — not published |
Rust forms the fastest-growing low-level backend segment 2024–2026. Drivers: memory safety without GC + zero-cost abstractions, cloud-native infra (Linkerd/Stalwart/SurrealDB), blockchain volume (Solana/Substrate). Trend: migration of critical paths from C++/Go to Rust.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Rust jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 1 |
| $3–4k | 0 |
| $4–5k | 0 |
| $5–6k | 1 |
| $6–7k | 1 |
| $7–8k | 0 |
| $8–9k | 1 |
| $9–10k | 0 |
| $10–12k | 1 |
| $12–15k | 1 |
| $15–20k | 0 |
| $20k+ | 1 |
- usable for the calculation: 7 (8.8%)
- stated but not converted to USD/month: 9 (11.3%)
- not stated: 64 (80%)
One in ten postings offers under $2,336, one in ten over $20,489. Half of the postings offer between $5,000 and $14,583. Sample: 7.
⚠ percentiles from 7 salaries out of 80 jobs — a guide on a small sample
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 1 |
| $3–4k | 3,000 | 4,000 | 0 |
| $4–5k | 4,000 | 5,000 | 0 |
| $5–6k | 5,000 | 6,000 | 1 |
| $6–7k | 6,000 | 7,000 | 1 |
| $7–8k | 7,000 | 8,000 | 0 |
| $8–9k | 8,000 | 9,000 | 1 |
| $9–10k | 9,000 | 10,000 | 0 |
| $10–12k | 10,000 | 12,000 | 1 |
| $12–15k | 12,000 | 15,000 | 1 |
| $15–20k | 15,000 | 20,000 | 0 |
| $20k+ | 20,000 | — | 1 |
Which countries have the most open Rust jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 18 | 28.6% |
| United Kingdom | 6 | 9.5% |
| India | 5 | 7.9% |
| Germany | 4 | 6.3% |
| Russia | 4 | 6.3% |
| Hong Kong | 3 | 4.8% |
| Hungary | 3 | 4.8% |
| Poland | 2 | 3.2% |
| Portugal | 2 | 3.2% |
| Switzerland | 2 | 3.2% |
| Other countries | 14 | 22.2% |
The leader by Rust job count is the US (18 positions). Large international remote via Cloudflare/Discord/AWS. Germany — Rust-friendly EU.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 18 |
| GB | 6 |
| IN | 5 |
| DE | 4 |
| RU | 4 |
| HK | 3 |
| HU | 3 |
| PL | 2 |
| PT | 2 |
| CH | 2 |
Which technologies are most often required in the same job as Rust.
Used together with
Share — how many of the 80 jobs in the Rust market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Rust stack 2026: Rust edition 2021/2024 (must), Tokio (async runtime dominator), Axum (modern Tokio-native web) or Actix-web (mature performance), SQLx (async + compile-time SQL checks) or SeaORM, PostgreSQL, gRPC (tonic), Kafka (rdkafka), Cargo + cargo-nextest + cargo-tarpaulin, tracing + OpenTelemetry, Docker + Kubernetes.
Common pairs: Rust + Tokio, Rust + Axum, Rust + SQLx + PostgreSQL, Rust + gRPC + tonic, Rust + Kafka. Learning roadmap: Rust syntax → ownership/borrow → async + Tokio → Axum + SQLx → gRPC + tonic.
Chart data
| Name | Count |
|---|---|
| rust | 69 |
| python | 18 |
| cloud | 16 |
| tokio | 12 |
| c++ | 11 |
| docker | 10 |
| aws | 9 |
| blockchain | 8 |
| go | 7 |
| terraform | 6 |
| defi | 6 |
| azure | 5 |
How many Rust jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 23 |
| principal | 8 |
| lead | 4 |
| junior | 3 |
| middle | 1 |
Junior almost none — the market expects systems-level experience. Career flow: C++/Go/Java Senior → Rust Middle in 6-12 months → Senior → Tech Lead / Systems Architect / Blockchain Engineer.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 23 |
| principal | 8 |
| lead | 4 |
| junior | 3 |
| middle | 1 |
Who hires the most for Rust and how concentrated demand is among the largest companies.
Employers
Demand is spread across 61 employers. The largest accounts for 6.8%, the top ten for 31.1%; the remaining 68.9% is long tail.
| share | value |
|---|---|
| top-1 | 6.8% |
| top-3 | 13.5% |
| top-10 | 31.1% |
| long tail | 68.9% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Rust jobs from.
Where Zorky sees this market
Observed across 30 sources; the largest accounts for 13.8% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 54 | 0.675 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 19 | 0.2375 |
| telegram | Telegram | Telegram | 6 | 0.075 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0125 |
The newest Rust jobs from company career sites.
Recent openings
- Principal Rust Engineer · GB · $20,489
- Senior Python/Rust Engineer – Core Dev
- Zero Trust Engineer | St. Louis, MO (Onsite or Weekly Travel Required) · US
- Manager Identity & Trust Engineering · US
- Python / Rust Developer · PL
- Senior Python/Rust Engineer - Core Dev- Global Quant Firm · GB
- DevSecOps Rust Engineer · GB
- AWS RUST Developer (P0) · IN
Latest open Rust Backend jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Rust — the seventh-largest backend segment, niche but the fastest-growing + premium. Comparison — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Backend
Related specializations
Inside Rust Backend: Rust Backend Engineer (general — REST/gRPC + Tokio), Rust Systems Engineer (CLI tools/databases/OS-level), Rust Blockchain Engineer (Solana + Substrate — cross-link to /research/blockchain), Rust Embedded Engineer (IoT/firmware — cross-link to embedded). Comparison — in the bar below.
Frequently asked questions
The most common questions about Rust Backend: pay, when Rust vs Go vs C++, Axum vs Actix-web, differences from Blockchain/Embedded, remote, how to start (6-12 months after Backend Senior), Senior skills. Answers recompute automatically.
What does a Rust Junior, Middle, Senior, or Lead earn?
Junior Rust jobs are ALMOST NONE — the market expects systems-level experience in another language (C++/Go/Java) + a ready Rust pet. Junior → Middle jump — ownership/borrow checker mastery + async Tokio + lifetimes deep. Senior owns Rust service architecture. Career flow: C++/Go Senior → Rust Middle in 6-12 months → Senior → Tech Lead at a Rust shop / Systems Architect.
What stack does Rust most often need?
Top 5: rust, python, c++, go, cloud. Rust edition 2021 (must) or 2024 (modern). Web: Axum (modern, Tokio-native, growing 2024–2026) or Actix-web (mature, performance leader, but higher complexity). SQLx (async + compile-time SQL checks — modern dominator) or SeaORM (async ORM). PostgreSQL. Redis (redis-rs). gRPC via tonic. Kafka via rdkafka. Cargo (must — build system + package manager). Testing: cargo test + cargo-nextest (faster) + cargo-tarpaulin (coverage). tracing crate + OpenTelemetry Rust SDK. Docker + Kubernetes. Knowledge of ownership/borrow checker + lifetimes + async/await fundamentals — Senior must. Profiling via cargo-flamegraph or perf.
When to pick Rust over Go or C++?
Rust wins: (1) memory safety without GC + zero-cost abstractions — the best combination for performance-critical + safety-critical. (2) System-level tooling (CLI tools, databases, OS tooling — Linkerd, Stalwart, SurrealDB). (3) Blockchain (Solana, Substrate, Move) — premium niche. (4) Embedded/IoT with no_std (firmware). Go: cloud-native + k8s, faster compile, easier hiring. C++: legacy, game engines, ultra-performance HFT (microseconds). Rust is replacing C++ in new system projects. Strategy: Go first for a cloud-native career (market size), then Rust for the premium niche. C++ → Rust — a natural transition (~3-6 months).
Axum vs Actix-web vs Rocket — what to learn in Rust?
Axum — modern Tokio-native framework (from tokio-rs maintainers), dominates 2024–2026. Tower-based middleware, excellent type safety via extractors, integrates the whole Tokio ecosystem. Growing trend. Actix-web — performance leader in benchmarks (TechEmpower), mature ecosystem since 2017. Actor-model influence. Higher complexity due to actors. Rocket — Spring-like declarative. Downsides: not Tokio-native (own runtime), slower adoption. Strategy: Axum first (modern + Tokio dominator 2024–2026), Actix-web for legacy + performance-critical, Rocket only if the declarative style suits.
What share of jobs are remote?
Among jobs with a stated work format, 55% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Rust Backend different from Blockchain / Embedded?
Rust Backend — server-side development: REST/gRPC API, business logic, DB, async I/O. Stack: Tokio + Axum + SQLx + PostgreSQL. Rust Blockchain — smart contracts on Solana (Anchor framework), Substrate-based chains (Polkadot, Kusama). Different paradigm: deterministic execution, gas optimisation, security mindset. See /research/blockchain. Rust Embedded — IoT/firmware on no_std (without the standard library), microcontrollers. Stack: embedded-hal + RTIC framework. Niche, separate career. Career switch Rust Backend → Blockchain in 6-12 months. Rust Backend → Embedded requires re-learning systems mindset (no heap allocation).
Where to start in Rust in 2026?
Backend Middle+ experience assumed (Go/Java/C++/Python). Roadmap: 1) Rust syntax — "The Rust Programming Language" (official Rust book — free), "Programming Rust" Blandy/Orendorff. 2) Ownership + borrow checker + lifetimes — the hardest part, will take 2-3 months of practice. "Rust by Example", Rustlings exercises. 3) Async Rust — "Asynchronous Programming in Rust" + Tokio Tutorial. 4) Cargo + package management. 5) SQLx — async DB access + compile-time SQL checks. 6) Axum — official tutorial + one pet (REST API with auth + SQLx + PostgreSQL + Docker). 7) gRPC via tonic. 8) tracing + observability. 9) End-to-end pet project: Axum REST API + SQLx + PostgreSQL + Redis + Kafka producer + Docker + GitHub Actions. Courses: Karpov.Courses, OTUS "Rust Developer", Rust Bootcamp (Letsgetrusty YouTube — best free), Zero to Production in Rust (Pollak) — must-read book. Backend Middle (Go/Java/C++) → Rust Middle — 6-12 months due to a crucial ownership shift in thinking.
How many open jobs are in this sample?
The published sample contains 80 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Rust need?
A Senior Rust Backend owns the full cycle + systems mindset. Rust core: ownership/borrow checker mastery, lifetimes (including HRTB), advanced traits (associated types, trait objects vs generics, sealed traits), unsafe Rust + UCG rules, error handling patterns (thiserror/anyhow/snafu). Async Rust: deep Tokio internals (executor model, work-stealing scheduler), pin/unpin for self-referential futures, AsyncRead/AsyncWrite traits, cancellation safety. Architecture: services on Axum + tower middleware, gRPC microservices via tonic, event sourcing via Kafka. Performance: profiling via cargo-flamegraph/perf, no-allocation hot paths, async fairness. PostgreSQL: advanced SQL, SQLx compile-time checks, connection pool tuning. Cargo: workspaces, custom build scripts, conditional compilation via features. Testing: cargo-nextest, property-based via proptest. DevOps: Docker multi-stage builds (Rust binaries often 5-20MB), Kubernetes basics. Soft: code review, mentoring (Rust learning curve is steep). English for Senior+ MUST — the Rust community is predominantly English-speaking.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.