A Chit-chat Day with the "Investor" - Inside Cadana

A Chit-chat Day with the "Investor" - Inside Cadana

Meet Nwanze Franklin, the Mobile Engineer known as "Investor" at Cadana. With six years of software engineering experience, Franklin has become an essential part of the team. His interest in how things work on computer screens and phones led him to software engineering.

In this conversation, Franklin talks about what it takes to be a successful remote software engineer, emphasizing the importance of qualities such as ownership and responsibility. He also discusses the challenges he has faced and overcome, highlighting the value of working well with a team.

Hello 😅 "Mr. Investor", please introduce yourself, your role here at Cadana and a little bit about your professional background.

My name is Nwanze Franklin I am a Software Engineer. Most people call me “Investor” because I know a lot about investments but I have no money.

At Cadana I am the Mobile Engineer responsible for building the pixel-perfect app our customers use. I have been a professional software Engineer for 6 years now.

What would you say drove your interest into this career path you find yourself right now?

I have always been curious about how things work behind the scenes on a computer screen and phone. My curiosity drove me into software and I wrote my first code in 2012 after I met a guy who was building a J2ME (Java Mobile Edition) apps.

Interesting! Tell us, from your perspective, what are the key qualities and skills that make a software engineer successful in a remote working environment?

There are several qualities required to become a successful remote Software Engineer. Undoubtedly, a vital one is "Ownership": The sense of responsibility.

Could you share a common challenge or problem you've encountered in your software engineering role and how you've effectively addressed it?

The common challenge is usually team collaboration. In my experience working in teams can be very difficult especially when you have people who have very strong opinions about processes, tools, and “certain ways of doing things”. At Cadana I have a different experience, the team is highly effective, open to criticism, and embodies ownership.

How do you manage stress, tight deadlines, and the everyday demands of your job as a software engineer?

Tight deadline is always a thing with startups because they have to innovate fast as that is the only leverage they have against the other tech giants competing with them. With my vast experience across fields, I break protocol and implement quick designs even without the designer to meet the deadlines after which I ease stress by playing FIFA online.

In your opinion, what are the most important skills for effective teamwork, and what is your approach to fostering productive collaboration with your colleagues?

Mutual respect and Effective Communication are two very important skills needed to foster team collaboration. I communicate with my team members in a tone that doesn’t sound offensive while keeping an open mind for pushbacks and resolutions.

How do you stay up-to-date with the latest trends, processes, developments, and skills in the ever-evolving field of software engineering?

I often take courses quarterly to improve my knowledge, read news from different tech blogs, and experiment with a few things I learn especially around security.

What aspects of your work do you find the most fulfilling and enjoyable?

Getting positive feedback from users of my product. An honest review is fulfilling, it lets you know that users enjoy your product and also points out the flows which push you to improve on it.

Outside of your professional life, what do you like to do for fun or to relax?

I do a few things for fun, Playing games e.g. FIFA, Driving, Eating, and travelling.

If someone is aspiring to start a career in software engineering, what advice would you offer them?

It is not a get-rich-quick scheme and so requires a lot of work which you must be ready to put in. Focus on the basics because they are the building blocks upon which mighty software is built. It also takes time.