• If you want to do something ask
• Just because you do not get a return offer does not mean you did not perform well

Doing a "Year in Industry" (Placement Year) was one of the most important experiences of my University life. This article aims to answer some popular questions I've had about my placement year as well as give some key advice to people considering placement.

The Background​

I worked at LexisNexis Risk Solutions as a "Placement Data Scientist", this was under their professional services team, which meant I was in a customer facing role, and was delivering work for customers. The main tools I used were Python for data processing, and Big Data Warehouse technologies. Common machine learning algorithms, such as regression models or trees were used for client pieces where appropriate.

What does Day One look like?​

This was an "induction day", throughout which I had a couple presentations about the company, the work, and clients I might be dealing with as well as meet and greets with multiple teams. The most impactful thing that, however, was meeting the previous years placements, our contracts were 13 months long, the final month is overlapped with the start of the new placements. This gives a month worth of skills handover and networking time, which really gave me an edge in both my client work and communication with the team. If I were to build my own placement programme, I would include this as well.

Prior Experience?​

A common question is whether I had any prior experience, for the purposes of the jobs I was applying for I had no paid prior experience, I was an Ambassador for Intel's OneAPI and I was a "Peer Tutor" (essentially a class assistant or PA) for my university classes. But I had not worked in a proper corporate environment before. what I did have, was:

• Passion
• Projects
• Presentation Skills

The first two come as a pair, you cannot work beyond your university brief, or beyond the curriculum if you do not enjoy what you do, as such your extra projects, and GitHub Profile can really help set you apart to other applicants who may have a great set of grades but do not show the same level of passion, enthusiasm, and drive to learn as you do.

As for presentation skills, this came from practice during education, and in general I enjoy talking about what I do, this especially for a consultancy-esc placement like mine, is a key skill to have, and even if you're not in a client role, being able to talk about the value you add is super important life skill that can make sure you get recognition you deserve.

The search for a placement​

I began my search for a placement in Mid November 2024, which was during my 2nd Year of Undergraduate studies. I had started my search due to my housemate obtaining his offer from IBM during this time, and this had kicked my into gear in order to start my own search. The whole process took up until January the following year, where I ended up with two different offers of employment. One for Software Engineering, and another as a Data Scientist. I ended up accepting the Data Scientist offer, as it was more closely aligned to what I wanted to do.

During my job search I faced many challenges, the biggest one I had was managing the number of technical stages, I was in a fortunate position where I ended up with 3 or 4 technical stages (of various difficulty) all due at roughly the same time, this was not ideal, and if I were to go back and give myself a piece of advice it would be to stagger interviews so you do not have so many steps back to back.

Another challenge I had faced was knowing what exactly interviewers or recruiters wanted from an application, this, unfortunately is not something that I have the answer to. However, I will say that something I always asked at the end of an interview was "Is there anything on my CV that would make you not hire me?", this question got mixed reactions, some interviewers loved the confidence that it gave, others were surprised that I had asked it. All of them gave feedback, which meant each interview I had, each application I had after was better than the previous. I believe this question, along with having the confidence to ask it, is one of the reasons I have done well in interviews, from placement to experiences beyond.

The process(es)​

In tech, different companies, from different levels have varying degrees of difficultly and length of process. Going into industry placement, I was certain that for most mid sized or competitive companies there is no reason to have more than 3 rounds of interviews, having done a placement and competing in the grad market, I still hold this opinion. As such many of the processes I went through simply looked like this:

• Initial call with recruiter
  • Do I understand the role?
  • Does this role align?
• Initial Technical Stage
  • I always made sure to get in front of a human as soon as possible
  • This was either a small programming task, or discussion around my prior work
• Take home assessment
  • Due to the client facing roles I was applying for this also included prepping a presentation
  • In one such case there was no take home assessment, but I did need to present an already existing piece of work.
    • For this I chose TheoryOfComputingGUI.
• Final Interview
  • Present take home assessment

I was very fussy in my application process, I did not want to overwork my self before signing a contract, as such I refused to write a cover letter, even during graduate jobs I stand by this opinion, they're often not read and really just a tick box from the hiring firm.

After placement​

Going back into my final year of university was a shock, the loss of regular income and loss of some luxuries (such as only sharing with one person), really hit me hard, for those who go into placement and start enjoying themselves, its important to keep in mind this might happen to you. As such it took me a month or so before I felt like I was back in the "university mind set". But rest assured, a couple times out with my friends, and back to the study grind and any feeling of "going backwards" had soon disappeared.

Another thing that happened, which leads into the "don't ask, don't get" advice, is I ended up working part time for my placement company throughout my final year, about mid way through my placement I asked if this possible, and 4 or so months later I got confirmation not only that it was possible, but they would love to have me continue. This really set me apart in the graduate market, a future blog post will go into detail about how I coped with 20 hour work weeks, plus university and social life. But the whole experience was rewarding, and I would recommend it to any one who thinks they can do it.

Nothing in in this post will be ground breaking, nor do I intend it to be. This is a simple, and hopefully effective guide that you can use when life "steps up a bit", whether its the same work,social and university as me or if your life is just a little busier than it was previously.

I will cover:

• Know your limits
• Guard your time
• Compartmentalise
• But what about social?

Introduction​

A huge reason for wanting to attend university in the first place was the social aspect of University, so when I started to pick up multiple jobs during my final year, time got busy.

A quick background, I was on a four year course at University of Kent, specifically studying computer science and artificial intelligence. This blog post focuses on my final year of university. While I was continuing to work for my placement year company.

I was working an average of 24 hours a week, 4 hours with university based jobs, and 20 hours at in corporate London. This, on top of a Research Dissertation and one module a term was a lot. In order to handle the workload, and tasks I stuck to three core ideas, "Know your limits", "Guard your time" and "Compartmentalise". These principle are all very simple at face value, but it took me a little while to realise how they would all work together.

Know your limits​

You must be honest with yourself on the time you have, and what you can achieve, while there isn't a "most important" principle among the ones listed, this was one of the toughest lessons I had learn.

Simply put, every one of us, has a limit, whether it be hours we can stay awake for, to how long we can hold a conversation, we all in one way or another have a point where "we just can't" anymore, if you're someone who has not yet discovered this limit, then you should give yourself a pat on your back. For the rest of us, when we're shuffling lots of tasks, and commitments it's important to consider how likely we are to be able to complete everything we have given ourselves to do on that particular day.

If you're anything like me, then you likely keep a calendar relatively up to date, with "loosely" defined time slots for specific tasks, or commitments this is a tool from Compartmentalise. This can work great to a certain extent, but what happens when you have 3 or 4 deadlines all occurring on the same day? What if you physically do not have enough time to do something?

Well, as harsh as it is, there will be a time you just cannot do something in the time you have, and it is incredibly important that you are honest with anyone relying on you, and more importantly yourself when this happens. If you are not, you could find yourself a victim of burnout, and this can be difficult to "get over".

Guard your time​

The principle boils down to, once you know your limits, you know what you can and cannot achieve, similarly you should have an idea of the time you have to complete a given task. By ensuring you pre-block your calendar / make plans early you are able to prevent (to the best of your ability) the sudden changing or re-prioritisation of a task to the detriment of another.

Similar to a many computational algorithms, you should have some "overhead" for the tasks you have, if you know a task will roughly take 2 hours, add an extra half hour, if you know the delivery date is next week, aim for a day or two prior to the due date, you must remain flexible Life changes quickly, and you have to be agile, it will lead to increased stressed, but knowing you have that buffer to play with will minimise the costs.

Compartmentalise​

Sticking all tasks, and feelings, into their respective compartments, allows you to concentrate on specific area of your life at specific times. In my case, by ensuring university was kept to university, it meant that work felt like a "break" for the day-to-day living of studying. Likewise, if work got particularly stressful my dissertation felt like a passion project at that time, which allowed for me to remain calm throughout an otherwise incredibly stressful time.

With each aspect of my life at the time (work, social and university (study)), I made sure to do my best to only think about one at a time, putting each aspect into its own "compartment" within my head and loose plan allowed me to context switch between the aspects without worry about what the other aspect was doing. This was only possible because university didn't depend on my work, and while my social life was closely tied to university at the time, I didn't share projects/teams with the people I socialised with.

But what about social?​

I know, I know I promised talking to you about social life as well. When I first signed the contract extension for my part time work, I realised that my time I had available would greatly decrease, I knew what university demanded from me at the time (considered I already had two years under my belt), and having just completed a years placement I also knew what professional work required of me.

So when it came to social? How do I manage that. I got a lot of advice throughout working and studying on this a lot of online sources will tell you academic and professional commitments come first, and this is true, but humans are naturally social animals, most of us require this, in order to thrive, you must include your social life into time, **do not feel afraid to push back on something just because its colliding with something for yourself.

You've been looking forward to that pub trip with your mates all week, and now priorities have changed? Push back, you need that time and you will risk other commitments and tasks if you are not careful.

• What I do: Data science for anti-fraud; final-year CS (AI) student
• What I write: tutorials, project write-ups, tooling guides (Obsidian, DataSpell, VS Code)
• Who it's for: engineers, data scientists, and curious learners

A few pieces of background:

• I currently work on anti-fraud models and pipelines, focusing on feature engineering and model interpretability.
• I study Computer Science with AI at the University of Kent — expect posts that bridge practical engineering and ML concepts.
• Tools I often use: Obsidian, DataSpell, and VS Code.

Contact me:

• GitHub: https://github.com/Scot-Survivor
• Discord: @Scot_Survivor
• Email: questions@scot-survivor.com