One Day in the Life of a Software Developer

One Day in the Life of a Software Developer

by Carolin Dirks

To be honest, most maths students who are just about to finish their studies have no specific plan of what kind of job they want to pursue after graduating. Up to that point, they might have realised what they did not know in their first semester, namely that there are plenty of opportunities in different areas of industry and academia for a mathematician besides the “obvious” choices, like the financial sector and insurance companies. Artificial intelligence, automation technology, big data, deep learning, computer vision – just a few fields of great interest for modern industry, and all of them are very closely related to maths. Most of them seem to promise a much more exciting job opportunity than an insurance company – with so many possibilities, why did I finally decide for a job as a software developer in an insurance company? The short answer: Because it offers a huge lot of fun, exciting tasks, complex mathematical and computational problems, and besides, great colleagues and an outstanding working atmosphere.

Let’s have a look at the long answer. For me, during my last years at the university it became clear that I wanted to be a software developer. Solving specific tasks using logical skills and computational tricks and contributing to something “useful” were the important parts for me, in addition to a strong desire for a preferably stress-free and enjoyable working atmosphere, while I did not really care about the specific application behind my work. The job advertisement at a big and well-known German insurance company sounded exactly like what I was looking for, next to the very good reputation of the employer regarding the labour conditions. So I took the chance, honestly without a specific imagination of how a “typical day” as a software developer would look like.

Now, 1.5 years later, I am still not able to say what a typical day looks like, simply because every day can be very different. Every day can pose different tasks and new challenges, with almost no repetitions, with lots of new things to learn, with lots of new insights – and the more I understand how things work, the more I can participate actively in new areas of responsibility. A developer is not only the aimless “executor”, but also needs to keep an overview of the whole software architecture, stay in touch with the “client” (in my case, the company itself, especially those who are going to work with the new software after its release) and other departments and work together with the rest of the team in order to develop a viable product. Thus, the best way to describe what I am really doing is to divide my tasks into three “areas”: The learning part, the conceptional part and the implementational part.

Carolin Dirks

My first year in my new job was dominated by the learning part. A mathematician is typically not educated in many practical skills, a mathematician is educated in independence, learning receptivity and frustration tolerance – in being able to understand complex problems and find smart solutions by her- or himself. Basically (and hopefully not sounding overbearing) a mathematician is able to understand almost every problem, and this is in my opinion one of the main reasons a mathematician is hired. Consequently, I needed to learn a lot, about programming languages and especially about state-of-the-art tools and technologies in software development. This was a whole new world for me – before, I had literally only implemented “plain code” without a suitable development environment, without fancy testing tools and without connecting to databases. And for me, there are very few places which are more suitable for getting a wide insight into so many different fields connected to development. Learning is not only considered to be necessary, but also promoted – and everyone in my department is encouraged to spend time on learning. Additionally, we have the philosophy that, roughly speaking, every developer in my team should be basically able to do every task – of course everyone has some kind of focus, based on his or her knowledge, but everyone is also encouraged to undertake tasks where he or she is a complete beginner.

Today, learning new things is still a daily business in my job. Another part which becomes more and more important is the conception and discussion of particular features of the new software. The “clients” (in our case, the “specialist department”, those who, in contrast to me and my team, know how an insurance as a product needs to work) decide about new features they want. This can be a very small and simple request like “I want this button to be green instead of blue” or a big new feature like the possibility for the customer to report a damage case. The developers (like me) discuss the technical requirements and details, check if everything is technically possible, roughly figure out which parts of the software are affected and what has to be done and wrap everything up in one or more specific tasks. In addition, the developers can contribute their own ideas or write “IT-only-tasks” (tasks which do not bring a visible new feature, but are necessary for some other reasons).

Consequently, the last part is the implementation part – namely solving the tasks. This (mostly) means implementing new pieces of code, integrating them into the complete software (after a quite strict reviewing process by other developers) and writing automated tests for the new features. One task can take from a few minutes (like the green button) up to several weeks, often accompanied by further discussion rounds with the “insurance experts” or with other developers. Besides, a task can be done completely alone or even in a team of several people – in every case, the whole team discusses everyone’s tasks in a daily meeting together, where problems can be put on the table or opinions can be exchanged. All in all, everything is based on teamwork: If you don’t know the answer to a question, lots of phone calls and sometimes a whole bunch of people staring at the problem later always lead to a solution.

All three parts together make this a perfect job for me. As an applied mathematician, I am still able to make use of the skills I acquired during my studies and still solve complex problems. The job does not only require programming skills, but also the ability to “delve into” specific issues and to analyse all sides and effects of a problem, while always raising new challenges and opportunities to learn new things – but without the pressure of exams and the question of “what should become of me” in the future.

Posted by HMS in Blog
One Day in the Life of two Mathematicians Juggling with Data

One Day in the Life of two Mathematicians Juggling with Data

by Mara Hermann & Marisa Mohr

The daily routine of a mathematician in the field of Data Management & Analytics can be diverse: Data collection, preparation and analysis, the design of artificial intelligence (AI) models, and much more. The opportunities to get involved in a data project are usually not limited to one’s own field. We, Mara (Senior Big Data Scientist) and Marisa (Senior Machine Learning Engineer), are two mathematicians who juggle data in a variety of ways every day. In this blog post, we describe what a day as a data juggler is like and how we use mathematics in our everyday lives.

If you study maths, you are faced with a wide range of possible career paths. But you should definitely take a look at the field of data management & analytics – not just because the Harvard Business Review called the data scientist’s profession the sexiest job of the 21st century [1]. In recent years, many specialised job titles have emerged, for example “Data Engineer”, “(Big) Data Scientist” and “Machine Learning (ML) Engineer”. However, they all have the same aim: to process data in such a way that useful information can be extracted (learned) from it and computers can act intelligently based on this knowledge. In particular, working with and implementing AI algorithms requires more than just AI experts – it’s a team sport. Regardless of their job title, it takes many different specialists working together as a team and complementing each other. Other areas of computer science such as database management or software engineering are also becoming increasingly important. 

Marisa, what is your role as an ML engineer in the team and when do you still use maths?

Due to the above-mentioned diversity and the numerous connections to other team members, it is difficult to describe a typical day of an ML engineer because every day is characterized by new challenges – fortunately. However, even with the most complex challenges, our mathematical-analytical approach does not make us despair.

The mathematical modelling of data in a learning algorithm, be it through a slightly more applied, specialised linear regression, or through a fancy artificial neural network, usually takes up no more than the last 5-10% of a whole data project. For a prediction to work really well, the end-to-end idea is crucial. Where does the data actually come from? And what data do I need to arrive at a valid result? Do I have the right data? Can I get to more profitable data, or do I have to change the prediction goal? It’s crucial to understand the big picture. After all, you need exactly the data that fits the problem you want to solve. 

All of AI […] has a proof-of-concept-to-production gap. […] The full cycle of a machine learning project is not just modeling. It is finding the right data, deploying it, monitoring it, feeding data back, showing safety — doing all the things that need to be done to be deployed.

Andrew Ng [2]

In general, an ML engineer is a person who helps deploy machine learning or artificial intelligence algorithms in a productive environment so that they can be used in the day-to-day business without difficulty. That sounds like a lot of infrastructure operations and software engineering, and yes, that can be a big part of an ML engineer’s job. You have to understand the existing IT landscapes and systems at the customer level to decide how to build a pipeline in those existing systems between the data and the output of a prediction, and how to deploy everything at the end. But as mentioned before, AI is a team sport. Of course, as an ML engineer, I’m not the specialist in everything, but it’s important to stay on top of everything.

Marisa Mohr

Now, how much mathematics is needed in this interdisciplinary field as an ML engineer primarily depends on the level and interest of the individual in the mathematical-statistical techniques that are being used. There is this type of ML engineer who spends all day building infrastructures or programming software to make an intelligent algorithm run productively in the client system. This kind of ML engineer is certainly more influenced by computer science than I am as a mathematician. I admire that, but I could never get lost in coding, and the good thing about being an ML engineer is that you don’t have to. The profession is so multi-faceted and multi-dimensional that everyone can follow their own passion and take their personal role in the team – with the bonus of dabbling in other roles every now and then.

As a mathematician, I have taken on various roles over the years. During a project phase, I often take on the role of a general strategist or project manager, ensuring that the team follows the same vision to bring together input and intelligent output in the productive environment. Then, when data modelling specialists are required in the project, I have the opportunity to follow my mathematical passion in the form of smaller data explorations and visualizations, through the evaluation of mathematical relationships in the data, to the selection and training of learning algorithms. The latter also includes consideration of accuracy, training time, model complexity, number of parameters, and number of features. In addition, parameter settings and validation strategies have to be selected, underfitting and overfitting have to be identified by understanding the bias-variance trade-off, and confidence intervals have to be estimated. A deep dive into maths for ML can be found on Medium [3]. As a mathematical minded ML engineer, my role can therefore be similar to that of a data scientist from time to time.

This role change and diversity is what I love about working as an ML engineer, or working in a data project team in general. Another ML engineer could certainly take many more technical roles, especially when it comes to gathering the appropriate data without which no ML or AI model works. And that’s where Mara comes in.

Mara, what do you do all day as a data engineer and when do you still use mathematics?

After my studies in mathematics, I started working as a data scientist for an IT company. When I applied for the job, I was asked in the interview what title I would prefer: data engineer or data scientist. At the time, I was convinced that the latter was the only reasonable choice for a mathematician like me. Even during my studies, I was a working student in the fields of data science and in addition to that, I also attended lectures on data mining, neural networks and other related topics. 

The connections between mathematics and data science are numerous – in fact, data science is mainly the application of mathematical models to various use cases. And I wish this fact would be taught  more often and more emphatically at university.

Have you ever wondered what all that mathematical theory is good for? If you are a mathematics student – have you ever been frustrated about all the types of matrix factorizations one has to learn in numerical mathematics? Or perhaps you are a high-school graduate contemplating the high art of analysis and algebra but you fear it will end in nothing?

I can soothe you: The use cases for mathematics and its theories are boundless. 

Mara Hermann

One of my favourite examples that I encountered during my job as a working student are recommender systems. A great introductory article on this topic can be found on Medium in which recommender systems are defined as “algorithms aimed at suggesting relevant items to users” [4]. Those items could be for instance products in an online shop or movies on a streaming platform. The interaction between items and users can be represented by a sparse matrix where each entry describes e.g. how a user rated a specific movie or if a user bought a given product. One approach to retrieve information and learn recommendations from this matrix is to decompose it into two smaller and denser matrices, the so-called matrix factorization. One matrix then describes the user representation and the other one the item representation – a great illustration of how a mathematical framework can be used in practise, just to name one example. Also other mathematical methods find use in the theory of recommender systems.

Now I fancied about how various and “sexy” [1] the applications of pure (and sometimes dry) mathematics in data science can be. But if you read this article carefully, you may have noticed that I wasn’t asked about my work as a data scientist but as a data engineer. Why?

As already mentioned, working on AI or – generally speaking – a data project is a team sport and in this course you also get in touch with other roles and switch positions from time to time. With my mathematical background I always had great respect for the role of a data engineer which I thought would be reserved for “real” programmers with an IT background. In the beginning of my studies I wouldn’t have thought that I would ever be interested in coding and, like Marisa, I will probably never be as much into programming as someone who studied computer science. But data engineering is so much more than sitting in front of the laptop, producing green letters on a black screen while typing at the speed of light.

The “unsexy” sibling of data science sure inherits more aspects from computer science than from mathematics [5]. As a data engineer, one designs, implements and monitors data pipelines which may feed a Data Scientist’s ML models. Additionally, data storage and quality are a huge part of the cake. Programming skills and willingness to permanently learn new technologies are indispensable in this job.

With this role description in mind, it’s true that you don’t necessarily need maths for being a data engineer. But that doesn’t mean that mathematicians can’t be good or even excellent data engineers at all. Their education entails a lot more than knowledge in algebra, analysis and many other subjects. It is often said that mathematics and philosophy are closely interrelated, some universities like Oxford even offer lectures combining both disciplines [6]. Even without attending such a course, a mathematics student acquires a lot of soft skills which are basic tools in the everyday life of a data engineer: One has to handle complex systems consisting of different data sources connected through various pipelines. With logical and analytical thinking one can better understand and design ETL (extract, transform and load) processes. Thoroughness and checking for accuracy are key to monitoring data pipelines and ensuring high data quality. Resilience, deduction and reasoning are of great help during performance tuning or debugging data pipelines. With some of these capabilities in your tool kit you have a great foundation for the role of a data engineer, practical experience comes with time. 

Thus, the opportunities for a mathematician in the data sector are broad. Different types of people and skills are required and there are numerous further training possibilities. Also, data projects can be very diverse, since data is everywhere: e-commerce, food and fashion retail, logistics, mobility, smart buildings,… One can always find a use case which fits one’s taste. I can definitely recommend taking the chance and gaining an insight into this branch. 

Regardless of which field of study or career path you choose, I can only encourage you to look beyond the horizon and also get a taste of other roles and fields than the ones you are already familiar with. Be it positive or negative, it will be a learning experience for you. And you will be an enrichment for every team if you can think out of the box.








Posted by HMS in Blog