Before Fasthosts, I worked in various roles. I worked in retail, as a sound engineer, and in personal finance. I didn’t start my career in IT until 2000 when I started working for one of our resellers. I moved here in 2002, starting off as a front-line technician.
What were your first few weeks like with Fasthosts?
Quite hectic. It was very ‘by the seat of your pants’. It’s not an environment where you’re told “just make this widget” or “just do that”. As a Linux systems engineer we’re given problems and expected to come up with solutions to those problems. You have to be hungry for learning new technologies, for problem-solving, for getting stuck in, for coming up with out-of-the-box and in-the-box ideas.
As a Linux systems engineer we're given problems and expected to come up with solutions to those problems.
How has your career developed with us?
Massively. I started off in the front-line trenches where I worked support for a year and a half, then moved through to second-line, where I was later made team leader. Then in 2007, I went to third-line technical support, which transitioned into my role now as Linux systems engineer. There’s been a consistent progression all the way through. When I started there wasn’t much of a Linux focus at all. There were two senior Linux technicians, one developer and one infrastructure guy, no one else at the company used Linux at all. It was certainly interesting coming in then, when we didn’t have many Linux-based products, compared to now when a lot of the infrastructure is based around Linux.
What motivates you to further your career with Fasthosts?
There’s an interesting challenge every day. I never come in thinking that the day is going to be boring and easy. I can’t imagine being sat at a desk doing the same technical process every day. That wouldn’t suit me at all, I like to sink my teeth into trouble shooting and problem-solving. As a Linux systems engineer I’m always working with new technology because everything is constantly changing. In some ways, it’s like starting a new position every few years because you’re suddenly dealing with a whole load of new stuff.
Is there anything else you think might be of interest to new starters?
Nobody expects you to know everything. Anybody coming in would be expected to get stuck in and try their best, but the support is certainly there. In infrastructure systems the team all have our specialities and things we’re well-versed in, so you know who you need to go and speak to if you have a MySQL query, or a question about a particular storage type, or anything like that. Outside of work, we have a lot of keen members of the FHRunners group which I co-founded.
"As a Linux systems engineer we're given problems and expected to come up with solutions to those problems."