Rust developer job description

About the role
We are looking for a Mid Rust Engineer to build and maintain production services, CLIs, and internal libraries. You will work with current stable Rust, the 2024 edition, Tokio, Postgres, and common tooling such as clippy, rustfmt, tracing, and cargo-nextest. This role suits someone who can deliver well-scoped features independently and ask good questions when trade-offs are unclear.

What you'll do
Implement service endpoints, background workers, and integrations with clear tests and observability. Improve existing Rust code by simplifying ownership, tightening error handling, and removing avoidable panics. Participate in code reviews, write small design notes, and help keep CI reliable. Debug production issues using logs, traces, metrics, and focused reproduction tests.

What you'll bring
Professional Rust experience or strong systems experience with recent Rust work. Good understanding of ownership, borrowing, Result-based errors, async basics, and Cargo workspaces. Ability to write maintainable code without overusing unsafe, macros, or complex lifetimes. Clear written communication in a remote team.

Nice to have
Experience with axum, sqlx, Kafka or NATS, Docker, OpenTelemetry, or performance profiling. Familiarity with cargo-deny, Miri, fuzzing, or maintaining shared crates.

About the role
We are looking for a Senior Rust Engineer to own critical service and library design across a remote engineering team. You will make technical decisions that balance safety, performance, operability, and long-term maintainability. The work includes async services, data pipelines, internal crates, and production debugging in Rust 2024 edition codebases.

What you'll do
Design and implement reliable Rust components with clear APIs, failure modes, and observability. Lead technical reviews for concurrency, error handling, dependency choices, and unsafe boundaries. Diagnose latency, memory growth, runtime blocking, and flaky tests using tools such as tracing, tokio-console, cargo-nextest, profilers, and targeted load tests. Mentor mid-level engineers through reviews and pairing while keeping delivery practical.

What you'll bring
Deep Rust experience in production, including ownership design, async Rust with Tokio, typed error strategies, workspace management, and dependency governance. Strong judgment around when to use channels, locks, tasks, threads, or message passing. Ability to evolve public APIs carefully and communicate trade-offs clearly.

Nice to have
Experience with axum or tonic, sqlx, high-throughput messaging, WASM, embedded Rust, fuzzing, Miri, cargo-deny, OpenTelemetry, or operating Rust services on Kubernetes.

About the role
We are looking for a Lead Rust Engineer to set technical direction for a team building production Rust systems. This role combines hands-on engineering with architecture, delivery leadership, and mentoring. You will help define how the team uses Rust safely and effectively across services, libraries, CI, observability, and operational practices.

What you'll do
Own architecture for Rust services and shared crates, including boundaries, failure handling, concurrency models, and rollout plans. Lead design reviews, guide dependency and unsafe-code policy, and establish practical standards for errors, tracing, testing, and API evolution. Break large technical goals into deliverable work, unblock engineers, and coordinate with product, security, infrastructure, and data teams. Stay close to the code through critical implementations, reviews, and production incident follow-up.

What you'll bring
Extensive production Rust experience and a track record of leading technical decisions across multiple engineers or teams. Strong understanding of async Rust, Cargo workspaces, semver, performance investigation, reliability patterns, and secure dependency management. Clear communication, calm incident leadership, and the ability to grow engineers without becoming a bottleneck.

Nice to have
Experience designing platforms, SDKs, or high-throughput systems; OpenTelemetry; Kafka or NATS; Postgres; Kubernetes; fuzzing; Miri; cargo-deny; WASM sandboxing; or multi-language migration to Rust.