Senior .NET Developer (SMARTLINK IoT platform)

Connectivity is KEY! And within Atlas Copco, it has become one of the fastest-growing strategic domains. A decade of investment has given us an industry-leading fleet of more than 300,000 connected machines and 100,000 users, whose data powers SMARTLINK and drives our sales, service and operational processes worldwide. Behind it sits our IoT platform: the cloud-agnostic, event-driven backbone that ingests device telemetry, holds the model of every connected asset, and serves the portal, the mobile apps and a growing number of internal consumers. We are expanding our platform team with a senior .NET developer who builds that backbone.

You build the platform itself, not the screens in front of it. Your working level is domain models, APIs, messages 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 of 14 people with developers, architects, test engineers and product owner, shaping design decisions rather than only implementing them.

The work here is engineering, not configuration. We build on . NET 10 and C#, with PostgreSQL for domain data, Apache Kafka for events, Redis for caching and ClickHouse for high-volume telemetry. Services are containerised and run on Kubernetes, brought up locally with .NET Aspire and tested against real dependencies with Testcontainers, shipped through Azure DevOps pipelines and instrumented with OpenTelemetry .

We are building a new back-end, designed around domain-driven design rather than carried over from what came before. The interesting questions are still open: where the domain boundaries lie, what each service owns, which events carry the truth. You get to answer them, on a fleet that is already global and still growing.

In this role, you will:

• Design and build domain services: bounded contexts, aggregates and a language the business recognises, in cloud-native .NET services that own their own data.
• Own your API contracts: design APIs that others build on, version them deliberately, and treat breaking a consumer as a decision rather than an accident.
• Design events, not just messages: Avro schemas in a registry, schema evolution, idempotency and replay, and a clear answer for the message that cannot be processed.
• Model data for the questions it will be asked: relational design in PostgreSQL where the structure is known, JSONB where it has to stay flexible, and query patterns that still hold when the fleet doubles.
• Engineer for fleet scale: hundreds of thousands of devices reporting continuously, where an unbounded consumer or a missing index is not a slow page but an outage.
• Make your services observable and operable: OpenTelemetry traces, metrics and logs, health checks, and alerts worth being woken up for.
• Test your own work, with unit and integration tests next to the product code against containerised dependencies rather than mocks, alongside the test engineers who build our shared framework.
• Shape the design upstream and raise the bar around you: turn requirements into a workable domain model during refinement, say so when something cannot be built cleanly, and lead through review and standards people actually follow.
• Leverage AI in your daily work, and help the team keep raising the bar on how we use it.

• Several years of hands-on C# and .NET back-end development, at a level where you own a service end to end and design the APIs others build on: contracts, versioning, and the discipline of not breaking your consumers.
• A working grasp of domain-driven design: bounded contexts and aggregates applied to a real domain rather than a textbook one.
• Hands-on with PostgreSQL, including JSONB where the model has to stay flexible, and comfortable writing and reasoning about your own SQL.
• Apache Kafka as architecture, not plumbing: producers and consumers, partitions and offsets, schemas and delivery guarantees, and the distributed reality around them - asynchronous processing, eventual consistency, retries and idempotency, and the ways they fail in practice.
• Container-based, cloud-agnostic development: Kubernetes (AKS / EKS / OpenShift), with containers and pipelines as part of how you build, test and ship.
• Strong troubleshooting and root cause analysis. You keep digging until you know why, not just that it failed.Agile / Scrum experience, the confidence to say in refinement that something cannot be built the way it is specified, and fluency with AI tooling plus the judgement to verify what it produces. *

Considered a plus:

• Designing a domain model or a service landscape from the ground up.
• ClickHouse or another columnar time-series store for high-volume telemetry, and Redis at scale.

At Atlas Copco Group you will join an international and diverse environment with specialists from different disciplines. Our culture is rooted in Swedish values, which includes a family feeling, respect and diversity. We invest in our employees’ development and well-being, and we provide a flexible work-life balance. With our inclusive and caring environment, you get the support and inspiration you need to grow.

You will benefit from a comprehensive onboarding program, including guidance by a personal godmother/godfather. As part of the Atlas Copco Group, you will also have access to global career opportunities. We offer a competitive compensation and benefits package, including health insurance, paid leave and retirement benefits.