Continuing our Sector Spotlight on the IT and Communication, today we hear from Ross Mackie who is a Technical Solutions Architect at Kyloe in Kirkwall.
Ross started at Kyloe as a Software Developer. From there, he progressed onto the role of Lead Developer for Services before starting his current role.
Can you describe a typical day in your role as Technical Solutions Architect?
Day to day I work with several different teams in the company, from sales through to development. This involves working with our sales team to better understand our clients’ needs to make sure we deliver something that fits and works for them. Then helping carry that through to the business analysts who dig deeper into the client process and create the documents that outline the work we will carry out. I also work in and with the development team as a functional lead to help turn specs into reality.
How did you end up in this role?
I started at Kyloe as a Software Developer. From there, I progressed into the role of Lead Developer for services, helping to manage the workload and direction of the Services Development team. Then I moved into the role of Technical Solutions Architect which is a blend of a Solutions Architect and a Developer.
What is the best thing about your job?
The varied nature of working with different clients that all have different processes keeps things interesting as there is always a new problem to solve. As well as helping create and drive new solutions.
What is the worst thing about your job?
As part of my job I’m responsible for pulling together estimates for the amount of time (hours/weeks) that a clients’ requirement will take to implement. We want to get this as accurate as possible, but it can be quite tricky as the time required sometimes only becomes clear as the project progresses.
What skills do you need to undertake your role?
What qualifications do you have?
Would you recommend this job to young people, if so why?
Yes, I think any role within the technology industry opens a lot of doors and is only becoming more important/relevant (the robots can’t program themselves…yet) - when I started out as a Developer I wouldn’t have pictured myself where I am today. That role allowed me to gain a very in-depth knowledge of the platform we work with which opened the door for becoming a Solutions Architect.
Visit Kyloe on: