Being a network engineer at RSAWEB

March 26, 2019

At RSAWEB we have a team of heroes who go out of their way to keep you connected and successful. This week we spoke to Cameron Rosslind, one of our incredible network engineers, who keeps things running smoothly.

 

How long have you been a network engineer? 

Well, RSAWEB gave me my first job. I started here in 2014, this August it will be five years. 

In layman’s terms, what is it that you do? 

As a network engineer, I manage, maintain and support the company’s infrastructure.  

What does your average day entail? 

Usually, I find myself supporting clients and resolving any issues they may have with their connectivity or infrastructure. I am also involved with planning maintenance on our own network; upgrading or replacing hardware, looking for new hardware to improve the network and make it more efficient. A big part of my job is also managing and monitoring the network to ensure that everything is stable and under control. 

My days are quite regular, except for the rare moments that something stops working and we need to spring into action to fix things as fast as possible. Besides the day to day stuff, I keep myself busy with side projects and research that will help the company. I enjoy working with new equipment and finding ways to integrate it into our systems, my job is not as monotonous as it may seem.

 

What is it like working at RSAWEB? 

The culture here plays a big part, it’s a big reason that I’ve stayed here so long. The team, the people and the environment are welcoming and friendly. The team is not huge, so you don’t end up feeling like just another employee. We actually get to know each other and the lines between colleagues and friends get blurred.

What is your favourite part of your job? 

Working out the kinks in something that was running smoothly a few minutes ago. The sense of achievement you get for being the one to find a solution to the problem that everybody has been trying to fix. 

What is the most stressful aspect of your job? 

Getting issues that affect large parts of the network. It can get very stressful when you’re trying to get multiple clients up and running after an issue arises. Often, you’ll be working with a whole team of people from various departments, or even clients, while finding the root of a problem. It can create a lot of pressure. There are also times when maintenance doesn’t go according to plan and you end up having to call the team, who are always happy to help you find a solution at odd hours.

What advice would you give to a network engineer on day one? 

I started as an intern, feeling very fresh and as though I didn’t know anything. It was quite daunting despite my years of studying and all my qualifications – I still felt unprepared. 

I would say that while studying is very important, you should try and work as soon as you can⏤experience is invaluable and whatever you have learnt will grow exponentially. 

On your first day, in some cases even your first few months, don’t be afraid of what’s going on. You do eventually know it all and learn it all, but it takes time, you will get there.