Developer C# .NET
We are looking for someone who can participate in sparrings about best practices and way of working. It is important that you are not afraid to speak your mind. Our culture promotes free exchange of view points, and your view points are as important as ours. The Senior C# .NET BE Developer will be responsible for, but not be limited to, the following: Using .NET 8 and C# to write high quality testable code and have experience with code reviews. Must work well in teams and speak fluent articulate English. Must work well with agile iterative development processes where developers cooperate towards the best solution. Making extensive use of pub/sub patterns with services communicating with RabbitMQ (via MassTransit) in an asynchronous fashion. We use various solutions for persistence, such as MSSQL, ElasticSearch, Redis, MongoDB etc. Using a CI/CD pipeline via Github Actions and Argo, deploying to Kubernetes across three different environments. We are beginning to use feature flags to activate features in production. Testing features across services, instead of writing unit tests. Monitoring services via OpenTelemetry and various dashboards. Constantly looking to optimize workflows – for example by keeping documentation up to date on current best practices, design of features, context documentation etc Involving users to try and get their perspectives when deciding on new features/changes to the system. It is important for us that all developers understands the users’ perspectives throughout the development process.
Good at verbal and written English Equivalent of 3 - 5+ years C# backend experience (Senior level) Experience with .NET Work well in teams An attitude of “Best code wins”, not “My code wins” Mindset & Attitudes: Be a team player, work toward the common goal of the team, is willing to support other colleagues Eager to learn the new technologies Have good mindset, attitude & commitment
Experience with remote teams Experience with technologies related to our stack Experience with writing functional tests and integration tests Experience with scoping new features Experience with backend-to-frontend communication best practices (API design, thinking “what the frontend will need”