FIND YOUR PASSION –
CHALLENGE THE POSSIBLE

Michael, what is your typical working day like and what are your tasks?

This question is difficult to answer – I rarely have a typical working day. I started my knowis career as a software developer, so initially I spent most of my time programming, of course, but I also took on architectural tasks right from the beginning. Meanwhile, I have specialized in the field of software architecture. What I particularly like is that the tasks range from strategic long-term planning and implementation to "we need a solution in a quarter of an hour". On the one hand, I like to dive deep into tasks, on the other hand, I like the kick of putting out fires. I also see aggregating and passing on the resulting knowledge as an important part of my work at knowis, because this is how you create something that persists and is helpful particularly for new colleagues. 

What makes your job so special?

Changing tasks, often across teams, and working with new technologies and systems are special features that make the job really interesting for me. Current cloud technologies or methods such as SaaS (Software as a Service), DevOps solutions, Continuous Deployment and Continuous Integration are not yet so established on the market and exciting for us programmers and architects, as we often do pioneering work. The specialists in our IT department cover a broad range of qualifications, so we can handle many processes in-house. The close exchange with the development laboratories of the big IT players such as IBM or Microsoft is also a great enrichment for me – this networking opportunity is not something you are offered in every job.

How was your application process? What do applicants have to bring with them to be successful in your field?

I was positively surprised how much knowis responds to the applicant – we talked a lot about my previous professional experience and what I like to work on the most, which resulted in a constructive conversation. This is also helpful advice I would like to give applicants: Be open about your experiences and expectations, even if your CV may not be so extensive yet. No one is born a master. We are looking for employees with team spirit and open-mindedness towards new technologies. A solid basis in programming languages like JavaScript, Java or Python is great, but a really good programmer is someone who wants to get to the bottom of problems and, following the principle of 'trial and error', remains curious and eager to experiment. Be it coding or as a consultant for the team.

Do you enjoy living in Regensburg? You are also relatively new in the city.

The city of Regensburg has a lot to offer. I used to live in Munich and although Regensburg is much smaller, it can keep up very well. In summer I like to lie on the Jahninsel or cool off in the Danube. At this time of year I can also recommend the Jazz-Weekend, when the whole city turns into a concert stage. For the colder season, I think a season pass for the local theater is a great option. For its size, the Regensburg theater offers an extensive program of drama, dance and music theater – but also the 'Alte Mälzerei' is a great location for everyone interested in culture.

Sebastian, you study computer science at OTH Regensburg – how did you come to work at knowis and what are your tasks?

At OTH Regensburg, it is compulsory to do an internship for one semester. In search of an internship in software development, I googled potential companies in the Regensburg area, came across knowis and thought “Sounds good, I’ll apply there.” I also checked social media and my university’s information system for additional information on knowis, as some students had already done an internship there before me. At that time, I was not fully aware of the banking background of knowis. However, you should not be intimidated by this; I realized during the job interview: “Team Bilanzkritik fits perfectly.” I felt comfortable from day one and supervision during my internship was very good. That's why I chose to stay with knowis and continued seamlessly as a working student after my internship. So I’m still part of the Bilanzkritik team and work there as a backend developer. I’m primarily focusing on the server application and the Java-based part of the client. In addition, I have also taken on tasks such as the creation of maintenance programs.

You are planning to write your thesis at knowis. What is the process for this?

I determined the topic together with my team leader and an experienced developer of the team. We sat down together to brainstorm about current topics that are suitable as a bachelor’s thesis and that I am interested in. The result: “Feature Analytics: Assessment and Prototypical, Technical Implementation of Event Tracking and Feature Usage Mechanisms Within the Framework of a Business-to-Business Application.” I have already made a rough draft of this topic and proposed this to one of the supervisors of the OTH. As soon as my topic is officially approved, I will be able to start. As it will be quite a lot of work to write my thesis, I will pause my working student job during this period. This means that I can concentrate exclusively on my bachelor’s thesis during my 20 hours per week at knowis and have nothing to do with the ongoing product development for the time being. This gives me flexibility and allows me to arrange my working hours in a way that is most convenient for me. Also, my internal company supervisors from my team at knowis are always there to support me with their expertise.

What have you learnt so far at knowis? Does your job there help you in your studies?

The computer science program at the OTH is generally very practice-oriented, but before knowis I was limited to my own small, isolated projects in the context of lectures or tutorials, which simply disappear from sight at the end of the semester and gather dust. At knowis I got the chance to work in a team of multiple developers for the first time – with a separation between frontend and backend. Instead of opening my IDE (integrated development environment) and starting from scratch, I’m working on an existing application and I’m advancing an existing architecture. This also means that I can explore technologies that are not part of the curriculum at my university.

Do you have any tips for other students regarding the application process or the final thesis?

The best tip to start with, I think, is: Just do it! So, in any case, look for a job as a working student in the professional field of your course, because putting what you have learned into practice in a company is something completely different from what you do in the lectures every now and then. At knowis, I can apply my knowledge and continuously improve my skills. What also helped me a lot during the application process was my personal interest in software engineering in general. During my school days, I was already part of a student-run company that took care of the IT equipment of our school, and I have remained enthusiastic about this subject until today. This is an important factor, especially when it comes to internships, and it helps you to find out if it really fits. Both for the applicant her- or himself, and on the part of the company.

Do you also work on any programming projects in your spare time?

I am a real geek and therefore of course have projects that I’m currently programming in my private time. Besides other hobbies, I’m secretary of our local skiing club and my current task is to bring our internet presence into the current decade. For this purpose, I am developing a modern web application that also works on mobile devices. At the same time – and this is the more complex part – I’m creating an administration tool that digitizes everything that is now managed on paper, such as course registration, vouchers, and membership data. So, programming is definitely a part of my life beyond work and study.

Markus, how did you come across knowis and how long have you been here?

I have been with knowis for five years now. Previously, I worked in various banks in the lending business for many years. I therefore know from my own experience what is important to our clients, banks and financial institutions. Because I've always been very interested in IT, at some point in my life I wanted to switch to this field as a profession. So, the question was: where do I find a job at the intersection of banking and IT? That’s how I came to knowis.

You only recently became a product manager – what did you do previously with knowis?

At the beginning of my knowis career, I worked as a business analyst. During that time, I looked after many projects while working at the customer's site. The requirements for a product manager are in some respects similar to the tasks that I worked on as a business analyst for many years. In my new position, this helps a lot to understand the big picture, for example, by knowing how the knowis banking platform is actually used and what our customers' experience has been with it. That's why switching to product management was the right step for me to continue to use my strengths and at the same time expand my knowledge.

What are your responsibilities as a product manager?

As an agile software company, we think and plan in release cycles. We want to renew and improve our software on a regular basis, so as a product manager, I deal a lot with feature requests and the enhancement of our software, as well as the prioritization of the different requirements.

New requirements come either directly from the customer or are suggested internally, for example, by our business analysts or the solution engineers. My job is to translate the often rather unspecific needs. This means I must think carefully about what is needed in particular and whether it might already be feasible in other ways. At the same time, it is always important to assess the development effort of a feature; for this part, I collaborate with an IT architect or developer.

Ultimately, I have to weigh how sensible the implementation of such a feature would be, that is to measure the business value against the development effort. Before each release, for example, we try to estimate the sensibility in a ‘business poker' process, where we discuss everything in detail and view the features from different angles. If a feature is to be considered for the next release, I define criteria that must be met during development. These are compared after the implementation and verified by the testing team – so you can already see: product management at knowis is closely integrated with other departments.

What skills or special abilities should you bring as a product manager?

It is very important to develop an understanding of how our software is used. When assessing the 'value' of a feature, a product manager should be able to capture the customer's view and, based on that, prioritize the requirements, while at the same time considering the implementation effort. In addition, the constant development of the knowis software platform is an important topic that needs to be structured and clearly defined.

A basic understanding of the technologies used, and the ability to work closely and effectively with different stakeholders, are among the requirements that a Product Manager should bring to knowis.

What do you like to do in your free time?

Most of all, I spend time with my family, or I am outside in nature, for example, when mountain biking. Also, I really enjoy water, which is of course very convenient here, as Regensburg is beautifully situated on the banks of the Danube. I love swimming there in the summer or just strolling along the river.

What does your typical work day at knowis look like and what are your tasks as a software engineer?

First and foremost, I am involved in the development of our cloud platform. I work with the programming languages JavaScript and TypeScript, but also modern cloud technologies are used.
Over time, my job has also changed a bit – the focus is now more on IT architecture. Incidentally, that's one of the reasons why I like to work for knowis: everyone can develop their own professional interests or reorient themselves as far as possible. As head of one of the engineering teams, I now also take on organizational tasks and am the contact person for questions and problems of my colleagues. 

What is special about the work at knowis?

Knowis has grown very fast in recent years. This always results in new fields of activity and positions. The employees themselves can grow into the new roles because the positions do not need to be created and filled, but arise as needed. Anyone who engages in knowis can definitely take on more responsibility and new tasks. I find it very pleasant that you can work autonomously and independently and are not dictated to from above.

How was your job interview? Do you have tips for the application process at knowis?

The atmosphere during my conversation was very relaxed and enjoyable. At knowis, the personality of the applicants is still a decisive factor for the selection and therefore we also talked a lot about me as a person, my previous work experience and what motivates me in my work. Shortly after the conversation, I got a commitment from knowis.
Currently, as head of engineering, I lead a small team myself and I have been involved in a lot of job interviews. It is important to me personally that the candidate is passionate about the subject and has a clear idea of how he or she can support our team.

At the time of your application, knowis was still a small Regensburg start-up. How did you find out about us?

Knowis is a 'hidden champion' in the industry. I was looking for IT companies, especially in Regensburg, and searched for potential employers through portals like XING, kununu and LinkedIn. Ultimately, I became aware of knowis via a job advertisement on XING and got more information about the company on the home page. The website was not that informative five years ago – which is fortunately very different today. Nevertheless, I immediately identified with the company and the tasks based on the job description and applied right away. As a result, I was invited to a job interview relatively quickly.

Prathibha, you are one of the software developers working on the knowis isfinancial platform. What are your responsibilities?

The development of isfinancial is split into two parts, the frontend and the backend. I am part of the backend where I concentrate mostly on the implementation of features that fulfill business requirements and on the data base, so, things like storing the data. In my team, we also take responsibility for the new stories, for example the new requirements that product management creates and which we then develop. My tasks also include maintaining and fixing bugs for the existing versions of the software that are already installed at the customer's site.

You have a small daughter. How do you manage to balance career and family? How does knowis support you?

As a young working mother, I have learned to lower my expectations both professionally and privately and to keep things simple. Especially when children are still small, they need a lot of attention and care from their parents, and of course every now and then we need to see the doctor unplanned, sometimes even during my working hours. This has also never been a problem for my team. If this happens, I simply do my work at a later time.

It is important to be transparent from the beginning to meet the expectations of both employer and employee, and to find the best option for both parties. My daughter is now two years old. When I started working part-time again, she had just begun day care. The whole family had to adjust to the fact that I am now a working mom. So during this phase we had some challenges to overcome, but knowis and especially my team were really cooperative and understanding. Nobody gave me a strict timetable; I was completely flexible in terms of my working hours and the completion of my tasks. In the beginning I worked in the afternoon, from 14:00 to 18:00. Without the great support of my team during this phase, I probably would not have considered coming back.

How was the transition from full-time to part-time work for you?

I first had to get used to the change from a full-time to a part-time job. I really like my job, so it was hard for me at first that I couldn't be there for 8 hours. At the beginning I was also a bit afraid that I would no longer feel like a part of my team. But my concerns were completely unfounded, everything is just like before. My team makes me feel needed and includes me. I can also increase or decrease my working hours flexibly. In this way knowis has enabled me to have a smooth start back into working life.

Also during the Corona period, when my husband and I worked from home, it was initially difficult to manage child care and home office. But also here my team supported me: I was able to do my work when it suited me best. We arranged team meetings in a way that everybody could participate. I also found it impressive how knowis shifted the weekly company stand up [editor’s note: a meeting for the whole company to share what has happened over the past week] to a digital space. I think we even learned more from the other teams than we did in the office.

Are there any programming languages or development tools you prefer to use?

I have mostly worked with Java until now, but I started playing around with the data base a lot in my former job in India, and here at knowis it has also become a part of my responsibilities. I just love to learn about the database, somehow it just fascinates me.

Christian, you've been with knowis as a Business Analyst since 2017. How would you describe your daily work?

Most of the time, there is actually no real work routine in my job. As a Business Analyst you have a wide variety of tasks, depending on whether you are working on a specific customer case or focusing on internal projects. I do a lot of different things: from writing stories, to conceptualizing the application based on business domains, or to sales situations in which I present showcases. A large part of my day consists of coordination – whether at the customer's site or in the office in Regensburg. It is my job to map out how to implement requirements within our software product in the best possible way. That calls for lots of discussions and a good deal of planning to find the optimal solution.

You are part of the Professional Services team. What is this team’s function?

Our main job is project business with our customers. We support financial institutions primarily in process analysis and the realization of requirements that result from it. But we are also there as a sparring partner for our customers on all other topics that are important in such a project, i.e., planning, next steps, communication with stakeholders and the preparation of project plans. So, we always try to provide the best possible support for our customers at every step and offer our know-how.

A customer project often starts with a workshop. Why is that and can such workshops also work in digital form?

We like to use different methods for such workshop formats to achieve a common objective for the entire project team. In our case, these are mainly User Story Mapping and Event Storming. With both methods, we can develop technical domains on the one hand, and define the first epics and sets of stories on the other. Such agile procedures make it easier to grasp the whole breadth of a topic, but they do not necessarily dive deeper. The details are worked out later in the individual sprint iterations in the context of Scrum. It can happen from time to time that things that were perhaps not an issue a few months ago suddenly come up in the project. For example, legal requirements or documentation requirements can change. These topics are then prioritized much higher in the software application.

These workshops also work in a digital format with the help of special tools: From my own experience, I can say that a discovery workshop for story mapping works well via video conference. The rules of the game are generally somewhat different for online conferences. Since you perceive gestures and facial expressions differently, you have to speak more and often question things that would be intuitively understood in a personal conversation on site. But basically, a lot of things that were thought to be "only possible on site" before Corona work online as well. In my job, I have noticed that both customers and colleagues or partner companies react very positively to the digital alternatives because, for example, you save an incredible amount of travel time that you often cannot use productively.

What qualities do you need to be a successful Business Analyst?

Flexibility and resilience are definitely part of it, but I think the most important skill for a Business Analyst is abstract thinking. If you get stuck, be it when you are thinking of how to solve a requirement in our banking platform or how to approach a customer meeting, it often helps to zoom out and take a different perspective. It is very important to be able to take the customers’ point of view and understand what exactly they want to achieve with their requirements.

Applicants should definitely be interested in new things and not be afraid of making mistakes, because there are always situations in which you have to come to a decision on your own. Much of what you do as a Business Analyst is pioneering work – so you rarely have a ready-made standard solution at hand. A trial-and-error mentality is therefore simply part of it.

You know both sides – the job in a bank and at an agile software company. How would you compare everyday banking with your work at knowis?

The comparison is not so easy at some points. Banks are often institutions that have grown over decades and have formalized and bureaucratized everything. knowis is a young company, plus the company’s business area of software development is incredibly busy. This concerns new technologies or the understanding of how to prepare software architecture, for example. As a result, there are often no patterns or blueprints to fall back on. A bit of research is always part of our work – and if you want to be innovative, too much bureaucracy is simply a hindrance.

You are part of the testing team. What is this team responsible for exactly?

There is a quote from John Ruskin that describes our work very aptly: “Quality is never an accident; it is always the result of intelligent effort”. Our team is specifically responsible for testing the knowis product isfinancial. Put simply, we click through the software and put its correctness, functionality and usability through its paces. We do this from the perspective of the future user. In addition, Product Management involves the testing team in the requirement process from the start. So, if we can foresee from a requirement that its implementation could lead to quality defects, we have the chance to intervene at this early point to prevent problems later on in the finished software.

Test Analysts make up part of our team. Their task is to look at the requirements for the software together with our Product Management team. They write test case designs, draw up test plans, and make specifications for how we want to test our release.

In addition to the Test Analysts, there are the Test Engineers, like me. The profiles of both roles are actually pretty similar, but the job of Test Engineer has a more technical focus. We use automated tests with test scripts that are defined by frameworks. My job is to write these test scripts and to set up and maintain the underlying framework in such a way that the tests practically imitate a user: clicking, writing text in fields, and checking whether this triggers the expected outcome.

As a Test Engineer, are you mainly on the hunt for bugs?

Well, you could say that, but it sounds a lot easier than it is if you put it that way. Developers of course review the code they are working on, but they don't test the bigger picture. I'll explain it using an example: If you embed a text field in an application, the text field itself may work, but it may not work anymore if a number field is built in above it. That's why it's our job to integrate the software modules into the UI and thus test the big picture in interaction with other things. To test in the UI, we also have to build our test apps ourselves.

What are common methods or procedures for testing software?

For us, quality assurance comes first. At the beginning of every release, we do a risk analysis to assess which and how many of the features are critical. We try to assess the effects of possible errors in the customer's software. Then we need to decide how much to automate and how much to test manually. We do feature tests in parallel with the actual development process. At the end of the release, we have a large number of regression tests; this means repeatable test cases. This ensures that no new errors have crept into existing parts of the software through modifications. Another option is to include use case tests in which a complete customer scenario is run through end-to-end.

How do you become a software tester? Which skills are important for this job?

THE classic software tester does not exist. But there are a few qualities that you should have to work in testing. You need an eye for details. Maybe this is also one of the reasons why my co-workers were so quick to nominate me for the position of safety officer. In addition, you should have a quality-focused way of working and be motivated to get to the bottom of things. A certain amount of flexibility and creativity is also required, because in an agile process like our development, there are always unpredictable things that can influence your work and force you to think outside the box. What is also necessary: good communication skills, because as a tester you are always in a lively exchange with other teams; at knowis mostly with Development and Product Management. Pointing out mistakes to people is often not the most rewarding task, so a little sure instinct helps a lot.

In addition to these soft skills, the technical background is important, especially as a Test Engineer. It is of course an advantage if the programming level is high enough that you can easily exchange ideas with the developers about the software. In any case, you should have basic knowledge of programming languages such as Java, JavaScript and Typescript.But you don't need to know everything; you just have to know where to look when in doubt or who to ask.

Do these qualities also influence what you do in your leisure time?

I do a lot of sports to balance my job: I regularly work out in the gym, go hiking or mountain biking. As you would expect from a computer scientist, I’m also a little nerdy: I am a gamer. But I am also a real family person and love to spend time with my wife, my brother – for example doing sports – and my parents.