A friend invited me to apply as a software developer, so I did. When I got the results from the assessment test – the examiner informed me that I failed the exam but suggested me a QA position. I immediately jumped on the opportunity without knowing what QA was. The manager offered me that opportunity in the company as he knew my learnability. Nokia provided training, coaching, and mentoring, and I enjoyed the work. As I developed my knowledge, an architecture and specification position opened, and I was excited about it. But I thought I was not yet ready for the role. I consulted my manager about it and asked for his opinion, and he encouraged me to go for it and to try it out. Fast forward to hardship and several leaps of faith, and I am excited to grow and try new things. This year I started my new position. Looking back, I am grateful to mention three key points: 1. Don’t be afraid to try new things. There’s no additional knowledge if you already know it – what is QA? 2. Develop your knowledge. Learning is a never-ending process: if you don’t know – study! 3. How will you know if you don’t try? You might regret it one day if you haven't tried.

If you are seeking a career that will be memorable and impactful, sometimes you may need to step outside of your comfort zone and take a leap into unknown waters. I took the leap twice - once when changing my role function (from accounting to recruiting), and secondly, industry-wise when joining Nokia. I did not regret either of those decisions and I feel this is where I belong. Don't be afraid to pursue your passion, with dedication and consistency your career aspirations can become a reality.

My top advice to someone starting is to build a strong foundation in the basics of IP networking. Spend time thoroughly understanding the fundamentals by reading and revisiting classic texts like those by Tanenbaum and Widjaja—they pay dividends throughout your career. Depending on whether you’re working in the control, data, or management plane, go deep into the details and truly understand the bits and bytes of how a feature works and the problem it is solving. Be open to taking on all kinds of work; no task is insignificant, as even seemingly small pieces often support critical components of the system. Especially in a small team, every member pulls their weight, and each contribution matters—both for the product and for your own growth.