Test Engineer for SmartLink IoT Platform

.fit_to_content{width:%;height:auto}Your role

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 , connected machines and , 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 Test Engineer who owns the quality of that backbone.

You are the quality owner of the platform itself, not of the screens in front of it. Your working level is services, APIs, messages and data: does a domain service behave as its contract promises, does a telemetry value survive ingestion, aggregation and retrieval unchanged, and does any of it still hold at the scale of a global fleet. You work in an agile team of developers, architects and product owners, following and sharpening our platform testing standard so that quality is a property of how we build, not a phase at the end. The total platform team is 14 people.

Test automation here is real engineering. Our suites are written in C# on .
NET by the same standards as the product code: xUnit, Testcontainers to spin up Kafka, PostgreSQL, Redis and ClickHouse per run, .
NET Aspire to bring up the distributed application, and a shared helper library published as a NuGet package so every service team tests against the same building blocks. Suites run in Azure DevOps pipelines per component and per environment, reporting into Xray.

Your first months land in the middle of a platform generation change, with two generations running side by side while we migrate. It is a demanding start and the fastest way to learn the platform inside out, but it is not the whole job: the migration will finish, the platform will keep growing, and so will your scope.

In this role, you will:

• Test the platform where it lives: contract, schema and integration testing of domain services and APIs, message and event flows, and the persistence behind them.
• Validate the data, not just the code: event streams, time-series and aggregated telemetry, from the message a device sends to the value the platform serves to its consumers.
• Extend the shared test framework the other service teams build on, and keep those suites running as quality gates in CI/CD rather than by hand.
• Solve testability as a design problem. Where a service cannot be validated on its own, work out what is needed (governed test data, stubs, simulators, contract tests, observability) and get it into the backlog before the feature is built, instead of testing on production machines.
• Hold the platform to what it promises its consumers. The portal, the mobile apps and internal consumers depend on your services, so you own those contracts and work with those teams on the flows that cross the boundary.
• Cover performance and load at fleet scale, through harnesses that drive the real processing pipeline rather than a simplified copy of it.
• Prove migrations and domain transitions: dual-source comparison between old and new, backward compatibility per domain, and confidence at cutover.
• Shape quality upstream and after the fact: turn requirements into test cases during refinement, challenge anything that cannot be verified, and triage defects across service boundaries.
• Leverage AI in your daily work, and help the team keep raising the bar on how we use it.

To succeed, you will need

At Atlas Copco Group, our slogan for various positions is "hire for attitude & train for skill". We train you for these positions through on-the-job-training. Do you only partly meet the profile as outlined below? No problem We still encourage you to apply and take this opportunity. Who knows, on-the-job-training may be available for you for this position.

Solid grounding in testing methodology, QA practice and defect analysis: functional, regression and risk-based testing.
You test services and APIs directly, not through a user interface. REST and messaging, schemas and contracts are your natural working level.
You write test code, and you write it properly: readable, reviewed, running in a CI/CD pipeline. We work in C# on .
NET with xUnit; another statically typed language is fine, and we give you the room to switch.
Hands-on with SQL and comfortable judging whether data and aggregations are actually correct.
A working understanding of distributed, service-based architectures: asynchronous messaging, eventual consistency, retries and idempotency, and the ways they fail in practice.
Strong troubleshooting and root cause analysis. You keep digging until you know why,