Rust Engineer
⚲ Warszawa, Kraków, Wrocław, Gdańsk, Poznań
30 000 - 54 000 PLN brutto (UoP) | 28 000 - 42 000 PLN netto (B2B)
Wymagania
- PostgreSQL
- AWS or GCP or Azure
- Rust
- Prometeus or Grafana
- SQL
Opis stanowiska
Rust Engineer
Backend / Systems / Infrastructure
Location: Remote or hybrid: Warsaw / Kraków / Wrocław / Gdańsk
Seniority: Mid+ / Senior / Lead
Tech stack: Rust, Tokio, Axum, gRPC, PostgreSQL, Kafka, Kubernetes, OpenTelemetry
About the role
For our client, we are looking for a Rust Engineer who wants to work on a product where Rust is not used as a buzzword, but because it actually makes sense. This is not another CRUD backend rewritten in Rust just to sound modern. The team is building a performance-critical platform layer where reliability, low latency, memory safety and clean architecture really matter.
You will work on core backend and infrastructure components used in production, with real traffic, real technical constraints and real ownership. The project is especially interesting for people who enjoy problems around distributed systems, high-performance backend, event-driven architecture, observability, API design and system reliability. If you like Rust because it gives you control, safety and elegance at the same time, this role should be worth a conversation!
What you will work on
You will help design and build production-grade systems in Rust, mainly around backend, platform and infrastructure engineering.
Your work may include:
• 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 who has strong engineering fundamentals and wants to build reliable software.
You may be a good fit if you have:
• 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 from the stack. We care more about strong fundamentals, curiosity and good engineering judgment than checking every box.
Backend / Systems / Infrastructure
Location: Remote or hybrid: Warsaw / Kraków / Wrocław / Gdańsk
Seniority: Mid+ / Senior / Lead
Tech stack: Rust, Tokio, Axum, gRPC, PostgreSQL, Kafka, Kubernetes, OpenTelemetry
About the role
For our client, we are looking for a Rust Engineer who wants to work on a product where Rust is not used as a buzzword, but because it actually makes sense. This is not another CRUD backend rewritten in Rust just to sound modern. The team is building a performance-critical platform layer where reliability, low latency, memory safety and clean architecture really matter.
You will work on core backend and infrastructure components used in production, with real traffic, real technical constraints and real ownership. The project is especially interesting for people who enjoy problems around distributed systems, high-performance backend, event-driven architecture, observability, API design and system reliability. If you like Rust because it gives you control, safety and elegance at the same time, this role should be worth a conversation!
What you will work on
You will help design and build production-grade systems in Rust, mainly around backend, platform and infrastructure engineering.
Your work may include:
• 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 who has strong engineering fundamentals and wants to build reliable software.
You may be a good fit if you have:
• 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 from the stack. We care more about strong fundamentals, curiosity and good engineering judgment than checking every box.
🔍 Dekoder Ogłoszenia
🟢
Rust is not used as a buzzword, but because it actually makes sense.
Firma faktycznie wykorzystuje Rust do rozwiązywania konkretnych problemów technicznych, a nie tylko dla mody.
🟢
This is not another CRUD backend rewritten in Rust just to sound modern.
Projekt nie polega na prostym przepisywaniu istniejących aplikacji CRUD na Rust, ale na budowaniu czegoś bardziej złożonego.
🟢
The team is building a performance-critical platform layer where reliability, low latency, memory safety and clean architecture really matter.
Oczekuje się pracy nad kluczowymi, wymagającymi technicznymi komponentami systemu, gdzie optymalizacja i stabilność są priorytetem.
🟢
You will work on core backend and infrastructure components used in production, with real traffic, real technical constraints and real ownership.
Będziesz odpowiedzialny za krytyczne elementy systemu, które są już w użyciu i mają realny wpływ na działanie produktu.
🟢
The project is especially interesting for people who enjoy problems around distributed systems, high-performance backend, event-driven architecture, observability, API design and system reliability.
Stanowisko wymaga pasji i doświadczenia w rozwiązywaniu złożonych problemów technicznych, a nie tylko podstawowej znajomości technologii.