Moving our technology from traditional tech and onto the cloud is not just a case of transferring the same applications and processes into a new space. To benefit from this new technology requires new ways of thinking and new ways of working, including how we access and process data.
The Cloud team are a collection of architects, tech leads, and developers who are responsible for developing the infrastructure, policy and assurances required to deliver, providing resource and assistance to all cloud initiatives, and working on initiatives that include cloud components or dependencies.
In this blog, Arthur Wilcox catches up with Harrison Thompson to find out about his new role at the ONS and what it's like to be a DevSecOps engineer in our Cloud Division.
Firstly, tell us a bit about yourself and long you’ve been working here?
Harrison: I’ve been working at ONS for 2 and half months now. My background is mostly public sector organisations in the education sector specifically, but I was in the private automotive sector for my previous role. Very glad to be back in the public sector doing something meaningful.
What was your first impression of the ONS when you joined?
Harrison: My first impression was that it was quite large an organisation with more going on than I could even comprehend. Fortunately, I think I’ve slowly grasped the basics for my area over in CATD (Cloud Architecture and Technical Design)!
Can you tell me about your role and responsibilities? Are they what you expected?
Harrison: As mentioned, I am part of CATD. I am working as a Tech Lead, mainly looking after our cloud services that reside in GCP. My specific focus at the moment is very much around the IDS (Integrated Data Service) platform, its security and automation. I expected to be working on cloud infrastructure, but the pace of delivery and sheer amount of work produced is a lot greater than I expected.
Can you tell me about the development tools and tech stack you are currently using?
Harrison: I mainly work with Terraform, with the repositories hosted on GitHub. My IDE of choice is VSCode. This of course comes with various modules and integrates with CI/CD pipelines in GCP. Our pipelines contain various tools and processes to check the quality and security of our code, which helps ensure consistency across our contributions.
In your first 3 months, is there a recent project or accomplishment that you are particularly proud of?
Harrison: The thing I’m most proud of so far is the improvements to automation that have been made to the IDS platform. I’ve worked closely with new colleagues to implement changes and improvements alongside them which has helped me embed myself into the team. This is important to me, as I do not work from the same office as any of my colleagues in CATD.
What have been your biggest challenges in these first few months, and how have you dealt with them?
Harrison: The biggest challenge so far is the number of new things I still need to learn and get my head around. ONS is a very big place with complex workstreams all over the place, it will take a long time to gain a deeper contextual understanding of where and how things fit together. Special mention goes to working on GCP when my past experience is all Azure based, though fortunately for me, lots of concepts are similar.
How do you find the team experience and culture? Is it supportive, competitive, laid-back, or something else?
Harrison: The team has been the best part of working at ONS so far, my colleagues in CATD are all extremely supportive and are ready to assist with anything I have needed help with. The high levels of talent and experience in the team are immediately clear. Colleagues outside of CATD that I’ve encountered have also been a pleasure to work with so far.
How do you find the communication and direction between your colleagues, managers and senior leadership?
Harrison: Communication is good between colleagues and managers, with daily stand-ups a great place to flag any ideas or issues. There is also senior leadership presence in these which gives me confidence that information is flowing smoothly in and out of the team. Wider organisational communication is also good, I receive various updates through email and Teams calls, as well as information on the intranet.
What do you think sets the ONS apart from other places of work?
Harrison: The ONS distinguishes itself from other government departments I’ve worked in by having one of the best flexible working policies I’ve ever seen, as well as one of the best promotion/progression programs that I have ever seen. There is nothing like it in the other departments I have worked for, nor in the private sector that I have seen.
And finally, what advice would you give to someone who is considering joining the Cloud Division, specifically?
Harrison: Do it, it’s a great place to work!
All our DevSecOps vacancies in the Cloud Division are live now, so if this sounds like something you'd like to explore further have a look through them.