Kris: Theoretical Mathematician as a Solution Engineer

When and why did you join BE-terna as a Solution Engineer, what initially drew you to the company?

I first came to BE-terna in 2016. At that time, I was working as an external contractor via my previous employer. In the first few months I quickly realised that I really liked working here. A year later an opportunity arose for me to officially join BE-terna and get a permanent position as a solution engineer.

When my previous employer asked me if I was willing to go work at BE-terna, I thought to myself “Sure, why not? I can gain a lot from this.”, so I guess you could say that I was initially drawn in by the desire to try new things and gain experience. However, what really kept me here was the great working environment, focused work, and clear company vision.

What is the job of Solution Engineer like at BE-terna? What is a typical day like for you?

Being a solution engineer at BE-terna is in many ways similar to being a solution engineer anywhere else, since the job responsibilities are pretty much the same, but there are some important advantages. A fairly high ratio of application consultants per solution engineer certainly makes the job of any solution engineer at BE-terna considerably easier. It means that there’s always someone you can turn to when you need some additional info on the business process you are implementing, and at times this also provides a much-appreciated buffer between you and the client. Hence, the work feels more focused with less distractions. 

A fairly high ratio of application consultants per solution engineer certainly makes the job of any software developer at BE-terna considerably easier.

I usually like to start my day by reviewing what I did the day before, what I plan to accomplish by the end of the day, and checking if my work is on track or if I'm falling behind. Due to the agile methodology, which is commonly used throughout BE-terna, I meet with my team every morning to quickly review what tasks we are working on, and then every two weeks for forward planning. The rest of the time before lunch is usually dedicated to development. After that, it’s lunch time at the local canteen! :) Occasionally there are some other meetings regarding refinements, one on ones with consultants if necessary, and so on, which are usually planned in the afternoon but times vary. After meetings there’s always more time for coding to keep you happy. :)

What are the pros and cons of being a solution engineer?

Let’s start with the most obvious pros: From a company perspective, the role of solution engineer is (one of) the most sought-after professions, so you can find a job pretty much anywhere in the world. On top of that, as computers and software are present in all industries, the job diversity is very wide and skills learned in one industry are easily transferred to another. As a solution engineer you experience a mixture of team and individual work, which is one of the pros I particularly like. As developers constantly work with computers, using a great deal more than just the basic software, their work-related skills also come in handy in everyday life fairly often.

As developing software usually comes with some time constraints and/or deadlines, you may find yourself under stress and working long hours, so you need to be able to work well under pressure. Technology is changing every day, hence the need to be proactive and improve yourself is constantly present. Your skills are often roughly as up to date as the software you’re working on.

The way I see it, most of the cons are just an incentive to better yourself, and so they're not really a con if they make you a pro! ;)

What does it take to be a Solution Engineer?

Put simply, a good solution engineer needs to be able to solve problems. However, you don’t usually solve problems alone, so communication and collaboration skills really come in handy. To solve a problem, you first need to understand it, so knowing your field of work and understanding the business is essential. Designing good solutions is easiest when you have the right tools, so it is important to know all the tools that are at your disposal and to understand when to use them. In the end, after the problem is solved, writing code is simple. ;)

As technology is constantly evolving, solution engineers also need to constantly improve themselves by embracing new technologies and learning new skills quickly. On top of that, it doesn’t hurt to have a positive attitude, some creativity, and attention to detail. Being able to think critically and not just blindly following instructions is a great skill that any developer should have, as long as it doesn’t prevent you from accepting criticism and learning from it.

Put simply, a good solution engineer needs to be able to solve problems. However, you don’t usually solve problems alone, so communication and collaboration skills really come in handy.

Who would you recommend BE-terna as an employer to?

I would recommend BE-terna to anyone who wants to work in a large, well-established IT company with some of the most experienced people in the field, whether it be as a solution engineer, application consultant, project manager, or any other position. If you are ambitious, want to develop your career, and are looking for a steady job with a reliable future, then BE-terna is definitely the company you are looking for.

When I was a kid, I wanted to be...

I wanted to be a theoretical mathematician, and I was for about 4 years. #AchievementAccomplished ;)