Senior.NET Developer
Il y a 9 heures
, Belgique
Atlas Copco
Temps plein
Gratuit avec email ou Google
Enregistrez cette offre et organisez votre recherche
Créez un compte gratuit pour enregistrer des offres d'emploi, créer des alertes et revenir à cette liste depuis votre tableau de bord.
Gratuit avec email ou Google
Functional area: Information TechnologyLocation: BelgiumCity: AntwerpCompany name: Atlas Copco Airpower N.
V.
Date of posting: Sep 14, 2026REST API design and implementation: designing and consuming well-structured, versioned APIs, and thinking about the contract before the code.
SQL databases: data modelling, query performance, and integrating relational data into cloud applications.
Testing as part of development: unit and integration testing as a habit, not a separate phase handed to someone else.
Apache Kafka: consuming event streams from systems you do not control, and living with what they send you.
Graph databases: Neo4j or equivalent, and the modelling instinct for when a relationship belongs in a graph rather than a join table.
Secure-by-default cloud development: managed identity, private endpoints, RBAC and secret management as normal practice.
Observability: structured logging, tracing, alerting, and being on the hook for a system you built.
Domain-driven design: bounded contexts and aggregates applied to a real domain rather than a textbook one.
Microservice architecture: service boundaries, inter-service contracts, and the operational cost of getting them wrong.
CI/CD with Azure DevOps: YAML pipelines, release management, and infrastructure as code (Bicep, Terraform or ARM).
Your roleWe are looking for a passionate and committed Senior Backend .
NET Developer.
You will be part of our internal software development team working in the Aftermarket domain. This surrounds applications for providing technical support, processing warranty, tools for our Field Service Engineer, our back office (planning and order processing), spare part list applications and Serialized Information Management.
As such you will be responsible for technical application ownership and developments. Next to this you will be involved in the full redesign of our existing applications and creation of new applications as business needs arise in our Customer Centers.
You will have the opportunity to work with a highly motivated international business and software developer team in a challenging and very dynamic environment.
You build the back-end behind our operational applications, not the screens in front of it. Your initial focus is the system that links as-built documentation, bills of material and product definitions to serialized equipment and the installed base which is used by internal teams, by Customer Centers and by dealers, with a growing number of applications depending on its APIs. From there you work across the rest of our backend landscape: warranty automation and order evaluation, engineering change bulletins, maintenance engines and the shared services the whole portfolio runs on.
Your working level is domain models, APIs, events and data: what a service owns, what its contract promises, which events it publishes, and how its data is shaped so that it still answers the questions we will ask of it in three years. You work in an agile team with developers, architects and a product owner, shaping design decisions rather than only implementing them.
The work here is engineering, not configuration. We build on C# and .
NET (8 or later) on Azure: Function Apps and App Services for compute, Kafka and Azure Service Bus for the event streams that feed us, and a deliberately mixed data layer SQL for the queryable subset, a graph store for the relationships between equipment, components and product definitions. Services run behind private endpoints with managed identity and RBAC, ship through Azure DevOps pipelines with infrastructure as code, and are instrumented with Application Insights.
To succeed, you will needYou have built back-end systems that other teams and other applications depend on, ideally in an operational or business-critical context where downtime is measured in stopped work rather than a slow page. You think in trade-offs rather than absolutes, and you keep digging until you know why something failed, not just that it did. You work comfortably in an agile team, have the confidence to say in refinement that something cannot be built the way it is specified, and use AI tooling with the judgement to verify what it produces. This is a senior role: we expect you to own a domain end to end and make decisions the rest of the team builds on.
You will not have every item on the list below. Cover most of the must-haves and be genuinely curious about the rest.
Must-haveC# / .
NET (8 or later, moving to .
NET 10): recent, hands-on experience building production-grade applications, not prototypes, at a level where you own a service end to end.
Azure: practical experience with several of: Function Apps, App Services, Service Bus, Event Hubs, Blob Storage, Azure SQL, Key Vault, API Management, Application Insights.
REST API design and implementation: designing and consuming well-structured, versioned APIs, and thinking about the contract before the code.
SQL databases: data modelling, query performance, and integrating relational data into cloud
V.
Date of posting: Sep 14, 2026REST API design and implementation: designing and consuming well-structured, versioned APIs, and thinking about the contract before the code.
SQL databases: data modelling, query performance, and integrating relational data into cloud applications.
Testing as part of development: unit and integration testing as a habit, not a separate phase handed to someone else.
Apache Kafka: consuming event streams from systems you do not control, and living with what they send you.
Graph databases: Neo4j or equivalent, and the modelling instinct for when a relationship belongs in a graph rather than a join table.
Secure-by-default cloud development: managed identity, private endpoints, RBAC and secret management as normal practice.
Observability: structured logging, tracing, alerting, and being on the hook for a system you built.
Domain-driven design: bounded contexts and aggregates applied to a real domain rather than a textbook one.
Microservice architecture: service boundaries, inter-service contracts, and the operational cost of getting them wrong.
CI/CD with Azure DevOps: YAML pipelines, release management, and infrastructure as code (Bicep, Terraform or ARM).
Your roleWe are looking for a passionate and committed Senior Backend .
NET Developer.
You will be part of our internal software development team working in the Aftermarket domain. This surrounds applications for providing technical support, processing warranty, tools for our Field Service Engineer, our back office (planning and order processing), spare part list applications and Serialized Information Management.
As such you will be responsible for technical application ownership and developments. Next to this you will be involved in the full redesign of our existing applications and creation of new applications as business needs arise in our Customer Centers.
You will have the opportunity to work with a highly motivated international business and software developer team in a challenging and very dynamic environment.
You build the back-end behind our operational applications, not the screens in front of it. Your initial focus is the system that links as-built documentation, bills of material and product definitions to serialized equipment and the installed base which is used by internal teams, by Customer Centers and by dealers, with a growing number of applications depending on its APIs. From there you work across the rest of our backend landscape: warranty automation and order evaluation, engineering change bulletins, maintenance engines and the shared services the whole portfolio runs on.
Your working level is domain models, APIs, events and data: what a service owns, what its contract promises, which events it publishes, and how its data is shaped so that it still answers the questions we will ask of it in three years. You work in an agile team with developers, architects and a product owner, shaping design decisions rather than only implementing them.
The work here is engineering, not configuration. We build on C# and .
NET (8 or later) on Azure: Function Apps and App Services for compute, Kafka and Azure Service Bus for the event streams that feed us, and a deliberately mixed data layer SQL for the queryable subset, a graph store for the relationships between equipment, components and product definitions. Services run behind private endpoints with managed identity and RBAC, ship through Azure DevOps pipelines with infrastructure as code, and are instrumented with Application Insights.
To succeed, you will needYou have built back-end systems that other teams and other applications depend on, ideally in an operational or business-critical context where downtime is measured in stopped work rather than a slow page. You think in trade-offs rather than absolutes, and you keep digging until you know why something failed, not just that it did. You work comfortably in an agile team, have the confidence to say in refinement that something cannot be built the way it is specified, and use AI tooling with the judgement to verify what it produces. This is a senior role: we expect you to own a domain end to end and make decisions the rest of the team builds on.
You will not have every item on the list below. Cover most of the must-haves and be genuinely curious about the rest.
Must-haveC# / .
NET (8 or later, moving to .
NET 10): recent, hands-on experience building production-grade applications, not prototypes, at a level where you own a service end to end.
Azure: practical experience with several of: Function Apps, App Services, Service Bus, Event Hubs, Blob Storage, Azure SQL, Key Vault, API Management, Application Insights.
REST API design and implementation: designing and consuming well-structured, versioned APIs, and thinking about the contract before the code.
SQL databases: data modelling, query performance, and integrating relational data into cloud
