Author: Maisie Alicia Eddleston

Posted on

A day in the life of a placement student in cyber security

Hi, I’m Maisie, a computer science student at Newcastle University. Last year I did a placement, working as a researcher at a cyber security company. This is a typical day in my life working remotely at the company.

8:00

I’d usually get up at this time and get ready for the day. My placement was remote so I didn’t have to get up too early!

9:00

At 9am, I’d start work for the day. I’d log on to my VM and Microsoft Teams as well as the other applications I needed for work. I’d then check my email and Teams, to check if I had any meetings that day as well as reply back to any messages.

After this, I would decide on what projects I wanted to work on for the day. I usually had a couple of projects on the go, so would decide on whichever was most urgent or relevant to research I had found. I would get up my code for that project and figure out what needed to be done. I would then write up my to do list for the day with the most important tasks to be completed.

9:30

After setting myself up for a good day, I would then start working. Usually I spent some time researching different libraries and new technologies that we could use to improve a project or solve a particular problem. I would spend some time reading the formal documentation, finding out about the technology, and ensuring it was suitable for projects.

10:30

At this time, I would usually have my morning call with my manager. I would talk through what I had been up to and the research I had found. Then I’d let him know my plans for the day and we’d discuss any new ideas for projects. If needed, he would also help me with any programming problems I had run into the previous day and give suggestions for possible solutions.

Sometimes I would be asked to quickly build small projects for other team members, such as test harnesses for other technologies created by the company. We would talk through the requirements of the program and I would prioritise completing that during the day.

11:00

Next I’d go downstairs and have a quick coffee break and say hello to my dog Ralph.

11:15

At this time, I was most productive after coffee! Usually I would start programming and getting most of my to-do completed for the day. I would try out the new technologies I had researched, using them to solve problems I had with my project.

If I had a project to create for a team member, I might also have a call with them at this time to learn more about the project requirements or to demonstrate how the project worked so far.

1:00

Then it was time for lunch!

2:00

In the afternoon, I would sometimes work on building demonstrations to show how new technologies could be used to benefit the company. This would usually involve building some test code to demonstrate how the technology worked. I would then record it and put together a demonstration video that could be shown to the sales team and higher management.

4:00

If I had time, I liked to end the day cleaning up my code and adding comments to make it more readable for others. This was an easy task to end the day, and would make it easier the next day to pick up from where I had left off.

4:30

I would usually have another quick call with my manager before the end of the day. I would talk through what I had achieved in the day and show him any code or demonstrations I had created. He would also help resolve any programming problems I had during the day.

5:00

The end of the work day, thanks for spending it with me!

Posted on

A day in the life of a placement student in AI

Returning from a year in industry with a company that specialise in artificial intelligence technology, we asked Joe what a typical Friday would look like during his remote placement.

8:30 am

As I was working remotely, a perk was having no commute time. This allowed me to get up at 8:30am and get ready for the work day starting at 9am.

9:00 am

At 9am, I would start work for the day and log on to Slack. I would continue working where I left off the previous day, which was usually continuing with an existing project. This could be a smaller project, such as benchmarking new libraries or open-source projects to compare with our existing projects. Alternatively, this could be a larger project which I would plan, develop and test, sometimes alongside the post-graduate student who joined the company at the same time.

11:00 am

After this, I would take a short break, where I would catch up with messages in the Slack chat. People would often post interesting articles related to work, which I would read at this time, or have general chat with coworkers about our current projects.

I would also have a listen to our work Spotify playlist and see if there were any new songs added.

11:30 am

At this time, I would have a weekly meeting with my line manager. During this, we would discuss my progress on my current projects and future plans for next week. On some projects, this would not be a one-on-one meeting and instead, a team progress meeting, typically with 3-4 people.

12:00 pm

I would usually take my lunch break at this time. However, it was flexible, so I could take it when it best fit my work schedule. I could also extend my lunch break, to go on a walk for example, and then work longer at the end of the day. Usually I would not do this on a Friday as I finish early anyway.

1:00 pm

After lunch, I would continue work for a few more hours. As these were my most productive hours, I would often focus on tasks such as the writing of formal documentation and presentations slides for clients. If not needed, I would just continue with my coding.

I also aimed to finish at a point where it would be easier to continue from later, such as completing a certain functionality. I would then write myself a quick note about my progression so I did not forget over the weekend. If I still had time to spare, I would then focus on cleaning up and commenting my code.

2:00 pm

At this time, I would have a meeting with my post-graduate coworker. We would catch up and discuss our progression with our projects and help each other with any problems we had encountered. Normally we would do this twice a week, often on a Friday as our work was winding down for the weekend.

3:00 pm

On a Friday afternoon, we would have a full company casual meeting. As there were 8 people in the company, we would each discuss interesting aspects of our work from that week, such as new progress and challenges overcome. We would also discuss more casual topics, such as our plans for the weekend and other general chat.

4:00 pm

On a Friday, we had an early finish for the weekend!

If you are interested in hearing more about Joe’s placement and how he found it, there is a separate blog post here.

Posted on

How my placement improved my university experience

Last year, I did a placement with a cyber security company. I found the experience extremely rewarding and that it benefitted my university experience when I returned for my final year of my computer science degree. This is a list of the advantages that my placement provided me with, that might convince you to complete one too. 

Finding my interests

Before starting my placement, I thought I might enjoy working in cybersecurity, but I had not had much prior experience in this field. My placement was an amazing opportunity to learn about what a career in this field involved and whether it was the right fit for me. I was able to learn about the different areas of cybersecurity and I found out what interested me the most. This helped me make a better, more informed decision when choosing my year 3 modules, as I already knew I would enjoy security and cryptography. It also helped me decide on my dissertation title as I had many topics of interest from my placement which I wanted to explore further.

Throughout my placement I was given the opportunity to learn about the different teams involved in the organisation, including research, software engineering and marketing. I could then determine which best suited me. By figuring out my career goals before finishing university, I am able to ensure my choices at university, such as modules and societies, align with these goals so I can better achieve them.

Applying theoretical knowledge

Throughout my placement, I was able to apply the theory I had learnt at university. This helped me gain a deeper understanding of the concepts I had studied, as I saw practical examples of how they were used and had experience building real systems.

Using my knowledge I had gained at university, I was able to create software prototypes for real customer requirements and test harnesses for the team to use. This was extremely rewarding, as I could directly see how my work was benefiting the company.

Networking and new opportunities

I was given the opportunity to meet lots of new people on my placement with different skills I was able to learn from. As well as helping me develop my technical knowledge, they gave me guidance and advice about my future career. Since returning to university, they have continued to support me, and have offered me a job starting after graduation. This was extremely beneficial to my university experience, as it helped reduce the pressure of looking for a job whilst studying. I am very grateful for their support, and learning from these individuals was probably the most rewarding part of my experience.

Gaining confidence

During my placement, I gained the confidence to work independently and as part of a team as my communication skills improved. I felt more confident working on team projects this academic year and took on a more leading role. I also had to deliver lots of presentations during my placement, a skill I have always found challenging but was able to develop throughout the year. I am now more confident in my ability and will use this new skill when giving my presentation for my dissertation.

Learning dissertation skills

During my placement I was able to gain new skills that I have since been able to apply at university. I learnt technical skills, such as becoming fluent in a new programming language, Golang, which I have continued to use at university and will use to develop my dissertation project. Additionally, I learnt new soft skills, including written communication skills and presentation skills. These skills directly relate to those needed for a university dissertation and will be extremely beneficial when I start.

Posted on

What to do the first week of your internship

When starting your internship, it’s important to make a good first impression and set yourself up for a good year. These are some things I wish I had known the first week of my internship to get the most out the experience. 

1. Get to know your role

It is important to know how your role fits into the company and what your responsibilities will be. It will help you meet and exceed your manager’s expectation and show that you are dependable and responsible. If not entirely clear from your job description, it’s perfectly okay to ask for clarification of what tasks are expected of you and the projects you will be working on. By learning what success looks like in your role, you are much more likely to achieve it and put forward your best work.

2. Start a ‘success’ document

Start creating a document for recording projects and tasks you have particularly enjoyed or succeeded at and how it impacted the company. It will help keep track of your achievements and can be used for a number of reasons. Firstly, it can be used when having check-ins with your manager, to show what tasks you have accomplished or how you have helped other team members. Alternatively, it could be used to reflect at the end of your internship, to demonstrate how you were successful in your role and how it has benefitted you and the company, to help gain a return offer. It could also be helpful for updating your CV after your internship or giving something to talk about during future interviews.

3. Introduce yourself to everyone

Try and get to know people during your first week. One way to remember everyone is by writing down their name and a brief description of their role after meeting them. People will appreciate you learning their name and it will help build friendships. It will also make it easier to initiate conversation in the future, such as when asking for guidance or advice, and help you to work better in a team.

Learning about peoples’ roles will help you learn more about the structure of the company and how it operates. By networking with others, you are more likely to be given the opportunity to work with other teams and gain new experiences and skills.

4. Learn the structure of your day

The first week of your placement is the perfect time to establish a good routine at work. To do this, learn how often to check-in with your manager, whether that should be daily or weekly, as well as other team members when collaborating. This will help you stay organised and better plan for these meetings.

As well as this, set up a routine for your own day for maximum productivity. This could be creating a list of daily objectives each morning, checking your emails at a certain times and using your most productive hours to complete more difficult tasks. This will help you stay focused and maximise your time.

5. Volunteer for projects

When possible, volunteer for projects at work. This will help you learn new skills and gain experience you might not otherwise get. It will show your enthusiasm for the role and your willingness to learn. You are also more likely to be remembered for future projects which could lead to more opportunities with the company. Your placement is what you make of it and you can get more experience by putting yourself out there and expressing what you want to do.

Posted on

My Review Of Otta

It can be extremely daunting when looking for a new job. I’m about to graduate this year in Computer Science and have spent hours scrolling through job posts online. So when I heard about this new recruitment platform, Otta, I was very intrigued.

It is a tech startup launched in 2020 that claims to ‘help you find your perfect job’ in tech. They have an extensive number of companies hiring on the platform, all of which have been vetted by the team at Otta. They say they only have the ‘most exciting, innovative and fast-moving companies’. ‘From startups to tech giants, you’ll find over 3,500 top companies and 70,000+ live jobs on Otta’.

According to Otta, they are more transparent about job opportunities than other recruitment platforms and include unbiased reviews, salary insights, diversity, and their honest take on every company.

The aim of the company is to help you be ‘picky’ and find your dream job. We tested it out to see if it was as good as it claimed to be.

Creating an account

Firstly, you have to create an account to view any job posts. To do this, you have to complete a quiz to assess the type of job you are looking for. This will allow Otta to only show you relevant job posts.

It asked questions such as what type of roles would you like to see, where would you like to work, when do you want to start, your preferred company size and your minimum expected salary.

Then it moved on to more tech-based questions, such as what industry you would like it work in, where you could select options such as AI, Security, eCommerce etc. As well as your favourite technologies to use, where you could select options such as Python, Java, AWS, SQL and many more.

I found it really useful that Otta asked these more technical questions, as most recruitment platforms, that are not tech-specific, do not include filters for these options. This seems like it will help you find roles that are more suited to your skills in tech as it is such a varying industry.

It was also just fun to complete this questionnaire and start thinking about exactly what you want to do as a career, rather than just choosing a position that is available.

View your roles

After creating an account, Otta showed me ten roles to swipe through that were suited to me from my questionnaire. You could either save or apply to any of these jobs and after going through the ten, could generate new results. It was easy to use and all of the roles interested me.

However, my favourite part was the description of each job. It included what the job involved, the company mission, insight into the company, company benefits, links to articles about the company and the people at the company. It was much more in-depth than on any other recruitment platform I have seen and allowed me to easily learn about the company I was applying for. I particularly liked the transparency of the description, including the salary benchmarks and statistics included by Otta such as growth rate and diversity. 

Conclusion

In conclusion, I really enjoyed using Otta. I believe it is perfect for people wanting to find graduate jobs or internships in tech. However, it is probably not as suitable for people in other industries. Overall, I found it a lot easier to use than traditional recruitment platforms and found relevant roles were much quicker to find.

My favourite part of the platform was the availability of information and the transparency for each job. It gave me more insight into each company and helped me better understand if I would be a suitable fit for a role. I hope this is something other recruitment platforms will do in the future.

I will definitely be using this platform again, alongside other tools, such as the NU Careers service and LinkedIn, to find my next job. Find the website here.