Pomiń do treści
Logo firmy Luxoft

Expert/Lead C#/.NET Developer

Luxoft

Oferta w skrócie
Widełki nieujawnione
🏠ZdalnieTryb pracy
📄OtherKontrakt
⏱️Senior · 8+ latDoświadczenie
LokalizacjaWrocław
Źródło
Aktywna
Opublikowano13 lipca 2026
Ostatnio sprawdzono14 lipca 2026
Wygasa za29 dni
Werdykt JobHunt

Senior hands-on engineering role for a distributed platform built on .NET/Windows, integrating a 30-year-old core financial system. You will own subsystems, design and implement features, lead a small EU team, and collaborate with a US-based lead. The work involves event-driven architecture, sagas, message brokers (RabbitMQ), and deployment pipelines. This is not a typical C# developer role – it requires deep distributed systems knowledge.

Brak jawnych widełek — wynagrodzenie do ustalenia podczas rekrutacji.

Brakuje: exact team size, on-call expectations.

🛠 Wymagane technologie
Dane źródłowe
AI Insights
Czym naprawdę jest ta rola?Backend Engineer

Senior hands-on engineering role for a distributed platform built on .NET/Windows, integrating a 30-year-old core financial system. You will own subsystems, design and implement features, lead a small EU team, and collaborate with a US-based lead. The work involves event-driven architecture, sagas, message brokers (RabbitMQ), and deployment pipelines. This is not a typical C# developer role – it requires deep distributed systems knowledge.

Plusy
  • Fully remote within EU time zone
  • Small, senior team with high autonomy and ownership
  • GitOps-style release management with CalVer and promotion pipelines
  • Strong observability culture (Splunk, OpenTelemetry, distributed tracing)
  • Benefits include internal mobility, paid referrals, LuxTalent platform
Na co uważać
  • Role integrates with a 30-year-old core financial system – potential for painful legacy complexity
  • Requires comfort with Windows Server deployment; may not align with cloud-native trends
  • 5-6 hour time difference with NYC team requires strong async communication discipline
  • !No mention of on-call or after-hours expectations
  • !Leadership component described as 'possibly' – may not be guaranteed
  • !Many technologies listed but not all mandatory – unclear which are core day-to-day
  • ?Tytuł wskazuje na rolę managerską, ale poziom doświadczenia nie został oznaczony jako Lead/Manager — warto zweryfikować u źródła
  • ?Brak jawnych widełek — wynagrodzenie do ustalenia podczas rekrutacji
Codzienna praca
  • Design and implement backend features across .NET/Windows services and MassTransit sagas
  • Take technical ownership of assigned subsystems: understand design rationale, identify improvements, drive implementation
  • Lead and mentor EU-based developers: code review, pairing, unblocking
  • Collaborate asynchronously with NYC-based team lead via written communication across 5-6 hour time difference
  • Contribute to design discussions, technical documentation, and architecture decisions as a full peer
  • Maintain and improve observability, deployment practices, and platform reliability for owned areas
Więcej o ofercie
Dla kogo jest ta oferta
Profil idealny

Oferta dla doświadczonych specjalistów (Senior).

Minimum sensowne

A mid-to-senior .NET developer with at least 5-6 years experience, some practical RabbitMQ and saga pattern knowledge, and the ability to lead and mentor. Willing to dive into a complex legacy-integrated platform.

Raczej nie dla

Not for junior or mid developers without substantial distributed systems and message broker experience. Also not for those who prefer modern Linux/container environments exclusively or dislike legacy system integration.

Ocena dopasowania
Junior1/5
Mid2/5
Senior5/5
Hands-on5/5
Architekt3/5
Remote5/5
Enterprise4/5
Pytania do rekrutera
  • ?What is the current size and composition of the EU team?
  • ?Is there an on-call rotation? If so, what is the frequency and compensation?
  • ?What are the core hours for collaboration with the NYC team?
  • ?Is there a roadmap to modernize away from Windows Server?
  • ?How much involvement with the legacy financial system is expected?
  • ?What is the typical onboarding process for a new senior engineer?
Brakujące informacje
  • Exact team size
  • On-call expectations
  • Budget for training or conferences
  • Recruitment process details
Zespół

Small, senior team working autonomously on critical subsystems. Collaborative with async communication. High ownership and no micromanagement.

🔗Podobne oferty