Understand the tech.Reach the people.

I am a work-study computer science student at T-Systems and will finish my bachelor's degree in October 2026. What draws me most is the step before implementation: understanding what someone actually needs, before the first line of code is written. That is exactly what my bachelor's thesis was about.

For an internal booking system I elicited, categorised and prioritised the requirements of three user groups, using the MoSCoW method, drawing on a full survey of the department and nine guided interviews. The result is a requirements catalogue that serves as the specification for further development.

What I took away from it above all is how far user groups drift apart. What one group calls indispensable does not even come up in the next, and two of the most important requirements only surfaced in the interviews. A survey alone would never have caught them.

Technically I am not standing on the sidelines while that happens. I can judge what a requirement means in practice: frontend development with React, machine learning and data analysis. On top of that comes the side that a degree rarely trains. I run our department's streaming studio, build new exhibits and present them at trade fairs, to specialist audiences and to visitors without a technical background alike.

After graduating I am looking to start in consulting, in a role where I translate between business and engineering and accompany projects from the first requirement through to delivery.