Felix Neumann, software architect, at IVU in Berlin since 2012
IT specialist Felix Neumann has been working in the Development division of IVU since 2012. Why did he join us as a graduate, and what motivates him day-to-day?
Felix, you joined us as an IT graduate. What did you have in mind when looking for a job?
As a student, my greatest fear was always ending up in a bank or insurance firm. Abstract work with financial figures is not my thing at all, I had no real interest in it. First and foremost, I was looking for a company that I can identify with – like IVU. We work every day to ensure that people get from A to B. That is tangible, beneficial and useful. I like that.
Of course, the working environment was also important to me: nice colleagues, a boss I get on with. I was pleased that IVU ticked all these boxes so well.
What exactly do you do?
I'm a software architect. In other words, I design software systems, coordinate implementation with colleagues and customers and, of course, help with programming.
The most recent specific example is our Ticketshop product for long-distance buses with integrated price control. For use cases like these, we have provided our customers with a system that controls and manages prices. I found that a really exciting project, partly because it was technically and professionally challenging, and partly because it's exciting to see how these prices actually arise. We learned a huge amount here in conjunction with the customer.
What does your average workday entail?
As IVU has a flexible work-time system, we can start and finish when it suits us. I usually arrive at around 9 a.m. To begin with, I read my e-mails over a cup of coffee. For the rest of the day, I work mainly on tickets, which we manage via our issue-tracking system Jira. Generally, I have a ticket with a specific task that I complete here. At around 11 a.m. each day, we have a joint status meeting in the kitchen where we discuss what's happened, what people are doing at the moment, what problems there are and what's coming up next. When I've finished development, I obtain feedback through pull requests and act on the results. I also take a look at what other colleagues are developing and give feedback.
There's usually enough time to try out new things once a week, for example to make day-to-day work easier for me and my colleagues. Just recently, I tried out a tool for monitoring our servers more effectively. This helps us especially in quality assurance before the software goes to the customer.