Life at AgileWorks #1: Interview with software developer Kaarel

"Meaningful projects, challenging work, autonomy" - these are the keywords Kaarel uses to describe working at AgileWorks, where he has been an employee for over seven years. In this post we explore what has kept him at AgileWorks, what he particularly values about the company, and his advice for those just starting their careers in software development.

Kaarel, can you please start by telling us what you do at AgileWorks on a daily basis?

I am involved in various projects either as an architect or team lead. Most of my time is spent on analyzing various topics, discussing with other developers, and reviewing code, so there is usually little time left for actual coding.

How did you come to join us and why did you choose AgileWorks for your next challenge?

Before AgileWorks, I worked for a long time at a company whose main activity was not software development, and I was essentially a solo developer on various internal projects. Since I had to fill many roles from developer to designer, I gained a very broad range of experiences, but at some point, it seemed that to further develop my software development skills, it would be beneficial to work in a team with other developers.

I quickly clicked with AgileWorks. The small but competent team, where you can learn everyone's names and faces in a day or two, was very appealing. I also liked that at AgileWorks, developers communicate directly with clients, understanding their needs better rather than just being a cog in a big system where requirements are filtered through multiple layers before being poorly translated into code.

Your journey at AgileWorks started over seven years ago. What has kept you with us all these years?

By nature, I am not one to easily hop from one place to another. The cohesive and pleasant team, the enjoyable and employee-wellbeing-focused work atmosphere, and the opportunity to work on projects that genuinely interest me have certainly contributed to my staying at AgileWorks.

You have also taken on the role of mentor at AgileWorks, guiding new software developers. What do you think is especially important in mentoring and guiding developers, and what should every mentor focus on?

Working in one field for a long time, you often forget how many details have become second nature over the years and what topics you struggled with at the beginning of your career. When mentoring, I often try to put myself in the other person's shoes to understand if a misunderstanding is due to a gap in basic knowledge. Then we can work together to fill that gap.

Knowing you are an avid reader, could you please recommend a book for development enthusiasts and explain why you chose that particular one?

Instead of a book focused on software development, I recommend Steve Krug's classic "Don't Make Me Think," which teaches you to look at things from the end user's perspective and helps developers better understand and engage in discussions about user experience.

What are your three recommendations for a novice software developer?

Firstly, I recommend finding a hobby project early on where you can apply and hone your skills. An area of interest will definitely give you the motivation to continue even if the dry theory and exercises become tiresome.

Secondly, spend time delving into various topics and understanding the details in depth.

Lastly, find opportunities to work with others - this can be either as paid work or as part of a hobby project - to amplify your development through team experiences.