Software Engineer Review

CGI operates on a project basis so the role will vary depending on the project. I worked in the Space, Defence and Intelligence business unit on a big-data cybersecurity project for a large client. My work involved upgrading an existing software platform to implement new features and improve stability. On this project, we utilised the agile methodology to coordinate our work. We would start the day with a scrum meeting known as stand-up. In this meeting, we would take turns to share our status with the rest of the team, detailing what we did the previous day, what we intend to do today and if we need any assistance in completing our work on time. My day to day job mostly consisted of working on my assigned tickets (tasks), with the occasional peer review of someone else's work to make sure it satisfied the success criteria and was of high enough standard to be committed into the shared codebase. I also took on other responsibilities, such as monitoring the daily build to ensure no breaking changes had been introduced and that any issues were fixed before we shipped to the client. Depending on the work I was assigned, I would sometimes have the opportunity to communicate directly with the client, via meetings and product demonstrations. Towards the end of my placement, when the new cohort of interns were starting their placements, I helped them onboard and get settled into the project.

Over the course of the internship I had numerous opportunities to take on responsibilities. One responsibility I took on was to monitor our nightly build and flag up any issues or breaking changes so that they may be fixed before performing any upgrades to the live systems. Even as an intern, my project manager let me take on an entire section of the project and see it through from start to finish, requesting assistance from a senior dev only when needed, rather than being led by them. This was extremely valuable to me because I got to work directly with the client and made sure to understand their needs and how we could support them. I led the development of this work and completed the vast majority of the corresponding tickets myself. Overall, the project managers were very happy with letting anyone at any level take initiative and take charge of their own career development, providing as much support as possible.

My placement was invaluable in teaching me new skills, both relating to technical knowledge and the professional working environment.
Technical skills:
We primarily used Linux as our development platform so a strong knowledge of the system was essential. I previously had a bit of knowledge of Linux but this was vastly expanded through working on the project, especially since some of the work was highly complex and required a deeper understanding of the systems involved and their interactions with each other.
I also started the project with some knowledge of Python, which helped me make progress with the more development-heavy tasks that used Python as the scripting language. However, I was able to learn a lot more from the experts on the team who have many years of experience and were able to teach me about software development best practices.
Our software platform is built with Ansible, which was completely new to me, but was a core component of most of my work. Through completing a wide range of work on various areas of the project, I developed a proficiency in Ansible and become comfortable enough with it to use it on a daily basis and understand how to further strengthen my knowledge of it.
Soft skills:
This was my first time working in a professional setting with a team of seasoned software developers. However, the welcoming and supportive company culture made it relatively easy to settle in and learn the ropes. One of the most important things I learned while on the project is how to communicate in a way that is efficient and productive for everyone involved, whether in-person, via video conferencing or on a messaging platform. I learned how to ask better questions that get better answers, how to help others effectively and how to work together to find a suitable solution to a problem. I also learned about understanding client needs and how to balance their requirements with technical or time constraints. This was important since not all proposed work was feasible in a given time scale and we had to be able to compromise appropriately in order to satisfy client needs while maintaining the stability of the system.

Since there was no requirement for previous experience to get onto this project, I had a lot to learn from the beginning in order to get up to speed. This involved a few intensive training courses, a lot of reading and spending some time with other developers to learn about the project workflow and the expectations within the team. Fortunately, this process was very smooth, mainly due to the supportive nature of everyone on the team. It was never difficult to get help and I was made to feel like a core part of the team from day one. My manager made it clear from the start that everyone was willing to provide as much support and guidance as necessary and I found this to be true throughout the entire placement. I had fortnightly meetings with my manager to assess my progress and see how I can push myself further and make the most of the placement, which I found extremely helpful and insightful.

The company culture was refreshingly relaxed and friendly. On my project, management were not strict about timetables and working hours, as long as the prioritised work was being completed to a high standard. There was always a friendly atmosphere both in and out of the office, to the extent that people would often join the meetings early just to engage in early morning banter. There was a lot of mutual respect within the team and with management, which meant that everyone was treated like an equal no matter what level they were. It was easy to bring up concerns and know that they would be listened to and acted on appropriately. This meant team spirit and productivity were always high, even when work became difficult and stressful. We also had plenty of socials, both within the team and with the wider company, so I got the chance to network with people from around the office and company who I may never have met otherwise.

The internship was my first look into professional software development and more generally the professional working world. Despite the line of work being slightly different from what I aspire to do long term, the placement was far more enjoyable and fulfilling than I could have imagined. I developed a wide range of technical and soft skills and got to network with many people around the company including the head of the project and the head of the business unit, both of whom are very down to earth and friendly. I was given meaningful work to do and was made to feel like an important asset to the team. Despite the knowledge gap between the interns and the full time developers, there was never any sense of imposter syndrome, as we were given plenty of support and guidance. The work was complex in nature, but also highly rewarding. The socials were varied and fun and I developed strong working relationships with my colleagues. Upon receiving an offer to return to the company as a grad, I accepted immediately.

Yes