Expert/Lead C#/.NET Developer
⚲ Krakow, Warsaw, Wroclaw
Do uzgodnienia
Wymagania
- C#
- .NET
- RabbitMQ
- MassTransit
- Splunk
Opis stanowiska
Client's application is a modern distributed application platform built on .NET and Windows, structured as a monorepo and operated across nine environments. It integrates a 30-year-old core financial system with modern consumers by providing event-driven processing, saga orchestration, API gateway, and observability infrastructure. The platform is maintained by a small, senior team. Engineers here own the full stack from architecture through production operations.
The problems the candidate will work on are fundamentally distributed systems and platform engineering problems. A representative sample of current and near-term workstreams:
- Blue/green deployment topology: zero-downtime service cutover using RabbitMQ exchange binding management, slot affinity middleware, and a topology reconciler. Stateless, eventually consistent, and operationally simple by design.
- Release and deployment pipeline: GitOps-style release management with strongly-typed release candidates, deployment profiles, and CalVer artifact versioning across a nine-environment promotion pipeline.
- Structured observability: Splunk Cloud log aggregation, structured log properties, distributed tracing via MassTransit/OpenTelemetry, and RabbitMQ queue metrics.
- Regression framework: an event-driven, eventually consistent, embarrassingly parallel regression system that compares PROD and UAT output streams per correlation ID using developer-written reconcilers.
- Saga-driven trade processing: multi-stream correlation, idempotent booking, ordered state machine transitions, and durable state across service restarts — all via MassTransit and MongoDB.
The successful candidate will join client's team as a senior engineer working remotely from within the EU time zone. They will work autonomously on large, critical subsystems of the platform, possibly lead a small local team (also in the EU), and serve as the primary engineering contact for that team's day-to-day execution. They are not a delivery manager — they are a hands-on engineer who also leads.
Day-to-Day Responsibilities
- Design and implement backend features across Kepler's .NET/Windows services, MassTransit sagas, and infrastructure layers.
- Take technical ownership of assigned Kepler subsystems: understand their design rationale, identify improvement opportunities, and drive implementation.
- Possibly lead and mentor EU-based developers: code review, pairing, unblocking, and growing their capability over time.
- Collaborate asynchronously with the NYC-based team lead and wider client's team. Reliable written communication across a 5-6 hour time difference is essential.
- Contribute to design discussions, technical documentation, and architecture decisions as a full peer — not a ticket-taker.
- Maintain and improve observability, deployment practices, and platform reliability for the areas they own
The problems the candidate will work on are fundamentally distributed systems and platform engineering problems. A representative sample of current and near-term workstreams:
- Blue/green deployment topology: zero-downtime service cutover using RabbitMQ exchange binding management, slot affinity middleware, and a topology reconciler. Stateless, eventually consistent, and operationally simple by design.
- Release and deployment pipeline: GitOps-style release management with strongly-typed release candidates, deployment profiles, and CalVer artifact versioning across a nine-environment promotion pipeline.
- Structured observability: Splunk Cloud log aggregation, structured log properties, distributed tracing via MassTransit/OpenTelemetry, and RabbitMQ queue metrics.
- Regression framework: an event-driven, eventually consistent, embarrassingly parallel regression system that compares PROD and UAT output streams per correlation ID using developer-written reconcilers.
- Saga-driven trade processing: multi-stream correlation, idempotent booking, ordered state machine transitions, and durable state across service restarts — all via MassTransit and MongoDB.
The successful candidate will join client's team as a senior engineer working remotely from within the EU time zone. They will work autonomously on large, critical subsystems of the platform, possibly lead a small local team (also in the EU), and serve as the primary engineering contact for that team's day-to-day execution. They are not a delivery manager — they are a hands-on engineer who also leads.
Day-to-Day Responsibilities
- Design and implement backend features across Kepler's .NET/Windows services, MassTransit sagas, and infrastructure layers.
- Take technical ownership of assigned Kepler subsystems: understand their design rationale, identify improvement opportunities, and drive implementation.
- Possibly lead and mentor EU-based developers: code review, pairing, unblocking, and growing their capability over time.
- Collaborate asynchronously with the NYC-based team lead and wider client's team. Reliable written communication across a 5-6 hour time difference is essential.
- Contribute to design discussions, technical documentation, and architecture decisions as a full peer — not a ticket-taker.
- Maintain and improve observability, deployment practices, and platform reliability for the areas they own
🔍 Dekoder Ogłoszenia
🔴
small, senior team
Prawdopodobnie oznacza, że zespół jest mały i składa się z doświadczonych osób, ale może też sugerować brak możliwości rozwoju dla mniej doświadczonych kandydatów.
🔴
own the full stack from architecture through production operations
Oznacza, że będziesz odpowiedzialny za wszystko, od projektowania po utrzymanie systemu w produkcji, co może być bardzo wymagające.
🟡
fundamentally distributed systems and platform engineering problems
Wskazuje na złożoność techniczną i potencjalnie trudne wyzwania związane z budową i utrzymaniem rozproszonych systemów.
🔴
integrates a 30-year-old core financial system
Może oznaczać pracę z przestarzałą technologią i potencjalne trudności w jej modernizacji lub integracji.
🟡
event-driven processing, saga orchestration
Sugeruje zastosowanie zaawansowanych wzorców projektowych, które wymagają dobrego zrozumienia i doświadczenia w ich implementacji.