Rust Engineer

About the role

Work on a performance-critical platform layer where reliability, low latency, memory safety, and clean architecture matter. Build core backend and infrastructure components used in production, with real traffic, technical constraints, and ownership.

The project is suited to engineers interested in distributed systems, high-performance backend development, event-driven architecture, observability, API design, and system reliability.

What you will work on

Help design and build production-grade systems in Rust, mainly around backend, platform, and infrastructure engineering.

• Building core services and APIs in Rust
• Designing async systems with Tokio
• Working on event-driven architecture and message processing
• Improving performance, latency, and reliability
• Designing clean interfaces between services
• Working with gRPC, REST, and internal APIs
• Adding observability with tracing, metrics, and logs
• Profiling, benchmarking, and optimizing critical parts of the system
• Participating in architecture decisions
• Reviewing code and shaping engineering standards
• Helping the team decide where Rust makes sense and where it does not

This is a role for someone who wants to understand the system, not just close tickets.

Tech stack

The exact stack depends on the team and product area, but you can expect work with:

• Rust
• Tokio / async Rust
• Axum / Actix / Hyper / Tower
• Tonic / gRPC
• PostgreSQL
• Kafka / NATS / event-driven systems
• Docker / Kubernetes
• AWS / GCP / cloud infrastructure
• OpenTelemetry
• Prometheus / Grafana
• CI/CD
• GitHub Actions / GitLab CI

What we are looking for

We are looking for someone with strong engineering fundamentals who wants to build reliable software.

• Commercial or strong practical experience with Rust
• Good understanding of ownership, borrowing, and lifetimes
• Experience with async Rust, preferably Tokio
• Experience building backend services or infrastructure components
• Understanding of API design, concurrency, and reliability
• Ability to write clean, maintainable, and tested code
• Interest in performance, observability, and system design
• Pragmatic engineering mindset
• Ability to discuss trade-offs, not just follow hype

You do not need to know every technology in the stack. Strong fundamentals, curiosity, and good engineering judgment are valued more than checking every box.