Have you ever wondered who the faces are behind our expertise? In our new series, we will reveal and introduce our teams working on customer projects in various industry domains. Today, we start with Ruben Rodriguez from ERNI Spain and will talk about his insights from MedTech.

Whether you are a young professional unsure which path to take in your career, a recruiter trying to better understand the role of a GUI (Graphical User Interface) test automation engineer or a project manager trying to get a better picture of the challenges faced in this role, this article is for you.

When we look at the evolution of technology in the diagnostics area, we can differentiate three main phases in the evolution of its intended use.

At the beginning, diagnostics companies were focused on improving analytic instruments in terms of accuracy, velocity and usage. In this first phase, the need appeared to centralise and manage the information provided by the instruments to improve medical decisions.

The second phase was focused in the automation of laboratories. Instruments were not isolated anymore. Step by step, the whole laboratory became a big interconnected system, and the sample workflows were centralised and controlled automatically. The focus was put on maximising performance and minimising human interaction.

Nowadays, we are finding ourselves in the first steps of the third phase in the area of diagnostics automation: use the technology for moving from sickness care to health care or, in other words, from being reactive to being proactive.

Intelligent apps are the core of smart businesses. They are, just as their name suggests, AI-enabled apps that use machine learning. The intelligence of the apps is derived from processing vast amounts of data and it has the ability to come to conclusions that are otherwise hidden to a human mind.

In the last year and a half, Stefan was assigned a project leadership mandate in the Med Tech Industry. We have met him for an interview, and he shares his lessons with us.

It has become obvious that being ready for a digital change has become one of the biggest challenges tech companies face nowadays and we will certainly all be a part of it.

This Techletter provides you with a brief overview of Apache Kafka, its concepts and its use and benefit in context of various architectural approaches and use cases.

The next PI planning is around the corner and your Product Management has already planned to bring a lot of new features for the customers. At the same time, your System Architects have planned to migrate some components to new services in order to be compliant with the company guidelines and the development teams are struggling with some technical debt that was always deprioritized in favor of new business features. How can you explain why we have to work on some enablers first?