Back when I applied for the role after my German philology and history studies, it was called concept designer. I believe that was a bit more obvious. Really, editor for digital training would be the most helpful job description. In other words, I develop the learning concept for our clients.

That's not quite as straightforward. There have been a few misunderstandings in my family over the years. I've often been described as someone who writes operating instructions for Volkswagen, or plain and simple "Philipp works in advertising".

Today I say: I create professional development for large companies, just from my PC.

When I'm in the office, I start by checking my emails. Then, I prioritise and schedule the tasks at hand and check the status of my projects. For example, I might be working on a script or coordinate with other teams or the client.

Generally speaking, there's always a good mix of extensive communication and creative work. I like this change between active talk and interaction and the extremely quiet phases, where I'm totally focused and block out everything else.

Neither is easy. Both require immense tact and instinct. When a client has no idea at all and is totally happy with all your suggestions to the point where they can't make a decision, you ultimately need to make the decision for them as a concept designer and hope that it really is a good fit. Meanwhile, it might not be possible to realise that very clear vision some clients have, or to align it with the actual training goals.

I often have to educate my clients, as many cannot judge the time and cost investments involved - for example, for some animations. Some expect teasers in blockbuster quality for next to nothing within a week. Of course, that's unrealistic. It takes a good bit of diplomacy and explanation.

Now, I would say, the most crucial aspect is found elsewhere: It's really important to start by defining and clarifying all the terms. Say, gamification: everyone has a different understanding of what that means. I need to get people on board from where they are. The best way to achieve that is to use specific examples and results from our portfolio. Overall, client consultation can sometimes be a balancing act.

I need to decide what to advise the client on, when to talk them out of an unrealistic idea, and when to respect their wishes. Thankfully, I have learned a lot in my nine years on the job.

I think I wanted to become a diver at some point. I really don't know why though. I guess it looked pretty cool with the wetsuits and such...

In the project business, personal development can be difficult. Of course, there's the big professional development (CPD) courses - I qualified as a certified face-to-face trainer last year.

Mostly though, I do many micro courses. I always keep an eye on what others in my field are doing, and try to learn from that to develop myself.

Actually, not that much. I had an idea what Software QA might imply, but I did not really comprehend the extensiveness of the job. However, when I saw this position advertised, I asked several people in a similar position what their role involves.

My brother is a software developer, so he gave me a detailed description of his role as a Software QA. It was different to what I expected - more complex.

What I do is a combination of different things, and not as technical as you would expect it to be - at least not so far in my role. Basically, I'm responsible for testing our flagship product, the imc Learning Suite - Learning Management System. I help to ensure the quality of the product and identify any problems before the end client receives their version of it.

I will also check if the User Experience (UX) has been designed as expected. Additionally, I test the platform from both the learner's point of view, and the administrator's perspective.

For example, I will verify the creation of the learning processes starting from the simplest scenarios to the more complex ones, and the experience of the learner when it comes to their learning progress.

QAs make sure that the User Experience is the one desired, by identifying problems early in the software development process.

QAs join a project when the requirements and specifications are written, by going through the documentation, providing feedback and developing the acceptance criteria. After the implementation has been completed, the testing phase / QA phase is done according to the requirements and acceptance criteria.

Software QA is an ongoing process, throughout the entire Software Development Cycle. Therefore, it is very important to communicate with the team members, because everyone who is involved in the development process has their own contribution.

Metaphorically speaking I would say each implementation is like an iceberg. What you see in the end is only the smallest part of the product development lifecycle. You have to really dive in, to see the entire iceberg, and that's part of my job as well.

It is interesting to see and be 'behind the scenes' to understand the processes, and how a feature is implemented. There is so much effort involved, and this was a totally new experience for me to be part of.

Before I joined imc, I was like everyone else - just an end user of different programmes or learning platforms, and I wasn't aware of the development lifecycle or constant maintenance that these products require behind the scenes.

You can learn to be a QA professional. It's preferable to have a technical background, but I don't have one either. I studied Statistics applied in Economics and only learned some basic IT things during my studies, but not much.

To be honest, everyone can be a QA expert, because everyone can be an end user. We have colleagues with different professional backgrounds, and they are great Software QAs.

Nervous, because this was a shift in my career. I learnt what my job would involve, but I wasn't sure if it would fit me. Nevertheless, it has been a positive experience which excites me every day, because the work is very dynamic.

The fact that I never get bored; I don't like repetitive stuff. There are always new implementations, new requirements - so you never test the exact same thing - the content changes.

And what I also love is that my colleges are open to all kinds of questions and never judge. At the beginning I felt like I was asking very stupid questions, because I don't have a technical background. I guess there were questions on a level like "is the earth flat or not?".

But the team never criticised my 'stupid questions', and instead took the time to explain the whole process to me.

By watching a movie! I love all genres as well as sitcoms. My mood dictates what to watch.

love Charlie Chaplin movies - I have seen them all. Other favourites include newer releases like "The Brothers Bloom" of "Four rooms".

Sympathetic! Everyone deserves the chance to be accepted.

As I explained to my father: Imagine you have a button in your car and when you press it, your car changes colour from black to red. My job is to program the button so that the car can turn blue.
It's the same with our Learning Management System (LMS), the Learning Suite. I am responsible for implementing the wishes of our customers in such a way that the Learning Suite is individually adapted to each customer's needs.

Intellij is a tool for programming languages like Java.

Five. There are so many things I didn't learn during my studies and what I had to completely rework here.

In other companies in Australia, I sometimes felt a bit left alone. Maybe it was because I came from another country. At imc, however, it is perfectly normal for there to be many different nationalities and for the international locations to work closely together.

Everyone is incredibly friendly and helpful and always supported me, especially at the beginning when I was a little lost. Not only the team in Melbourne, but also my colleagues in Germany were always there for me. I appreciate that very much and can therefore work much more liberated.

I just like to start off positively and relaxed in the morning and always drink two glasses of water after getting up.

Yes, many even. Michelle Obama, for example, is a great woman, but the Indian astronaut Kalpana Chawla or the Nobel Peace Prize winner Malala Yousafzai are also extraordinary personalities.

In general, I admire all women in industry, but also mothers. All women are my role models, from whom you can learn something and who make a difference.

I can motivate myself very well and am not afraid of hard work or to stay longer, if necessary. When I've put something into my head, I really want to achieve it and I think it's great when the results are right in the end.

Not a special country, but my dream is to see the whole of Europe - or at least as many countries as possible on the entire continent.

An Indian film called "Pink". It's about my heart's issue women and equal rights; especially in my home country there is still a lot in trouble here. In some regions in India, for example, it is still frowned upon that women drink alcohol.

The film deals with exactly that and deals with a woman who drinks alcohol and is raped. The man and the lawyers then argue in court that the woman would have behaved inappropriately by drinking. I find such films very important to point out and change grievances.