intive_People: 5 Questions to Lukas Schmargendorf

intive is us. We come from different backgrounds, specialize in multiple fields and use various tools and languages. In this series of short interviews we introduce intive’s professionals by revealing how they work, what they do in their free time, and what drives them in life.

  • Name: Lukas Schmargendorf

  • Location: Regensburg

  • Role: QA engineer

  • Expert at: testing in automotive environment

  • Favorite app: --

  • Currently watching: The Mentalist

  • Currently reading:  Hölleluja! by Stefan Kretzschmar and Nils Weber

How would you describe a QA job to someone from another planet?

A QA specialist is responsible for ensuring the desired functions in the software supplied. Our task is to analyze the requirements for the software and develop and automate the corresponding tests. With these implemented tests, we can then determine deviations from the requirements and report them back to the developers.

Is the relationship between QA and programmers antagonistic in any way? What are your experiences?

In a way, yes, since our tasks are at opposite ends of the spectrum. Programmers try to create a product that is as perfect as possible, which in the end is usually perfect in the eyes of the developer. And then QA testers come into play. They put the software through its paces and try to find and uncover every little error or weak point. This makes it easier for a QA tester to assume the role of the user and thus more easily foresee problems that may arise.

This certainly might feel negative to the developer at first, especially since the developer and the tester often only have contact when the tester has found a bug. Of course, this is never intended as personal criticism and, in general, most developers accept the QA test results in order to create a better product for the customer.

What do you like the most about your job?

First of all, the great team, with whom I feel privileged to work every day. It’s thanks to my colleagues that sometimes difficult and challenging tasks can be tackled and mastered. I also enjoy looking at the software from different perspectives, which helps me find all possible bugs in the software.

If you had to replace the word "bug", what would you name a software glitch? And why?

From the tester's point of view, I would replace the phrase "a bug was found" with a more positive "quality has improved" kind of statement.

What is the best place in the world you’ve ever been to?

I really like Asia, and especially Myanmar. The culture there is just so different from ours and that's what makes it so interesting.

Jak możemy Ci pomóc?

Skontaktuj się

Widzisz się wśród nas?

Dołącz do nas