Could you share your field of research and how you applied your existing research skills to this project?

Certainly, my background is largely different from this project; I’m primarily from the STEM field, specifically engineering, while this project leans more towards social sciences. In terms of conducting research for RCT and online surveys, this was all rather new to me. I wouldn’t say my technical skills directly applied to this particular project. However, there are other skills such as writing and organising the structure of presentations or reports which are certainly useful and do stem from my previous background.

I’ve also gained knowledge on conducting surveys. Even though I wasn’t the one spearheading that aspect, I was thoroughly involved in every step. This included learning about the software and websites used for the survey, which was certainly an educational experience. Moreover, the concept of RCT was entirely new to me. By following the entire process, I was able to gain significant insights. Without a doubt, this has been an enormous learning experience.

I believe the most impactful moment was when I found myself stepping up to lead certain aspects of the project. For instance, arranging meetings with the client or coordinating group meetings. Sometimes, when a message came through on Slack and no one responded, I stepped in to reply. I made an effort to be more engaged, particularly when others were being quiet. I learned that in a team, if others are silent, it doesn’t mean you should be too. Otherwise, the project could grind to a halt. This aspect of teamwork has been a crucial lesson for me, and likely the most significant.

One major takeaway has been learning to manage my time effectively, especially since this project is in addition to my usual work. It required me to be more flexible when dealing with multiple tasks at the same time. At times, even when I felt exhausted after my day’s work, I had to push myself to fulfil my commitments to the team and the project. This is something I became acutely aware of during this project. I’m currently working on several projects simultaneously, and it’s essential for me to stay committed to each one. This was a new realisation for me as, in the past, I usually worked on just one or at most two projects at a time. Therefore, when faced with multiple tasks, I’ve had to push myself harder than before.

The primary distinction lies in the nature of the project. My research work tends to be more self-driven, whereas the Code-Switch project necessitates a more collaborative approach, involving a team of six people. Coordination with team members, as such, becomes a pivotal aspect of this project. While my research also requires some degree of coordination, it’s comparatively easier.

In a lab environment, my work predominantly involves planning and conducting experiments. While this does require teamwork, such as support from technicians and colleagues, especially for experiments that need multiple people, it’s more straightforward. If I need to schedule an experiment for the following week, I discuss availability with my colleagues, book a lab room, set up the equipment, and proceed with the experiment. This type of teamwork is simpler because technicians are expected to assist us, making it easier to arrange things. However, in the Code-Switch project, all participants are on the same level, each contributing to different aspects of the project. You can’t simply assign tasks to someone without their agreement. Even if you’re leading a workstream, it doesn’t imply you can allocate tasks to whoever you think should do them. You need to ensure they’re willing to accept the assignment. This aspect makes teamwork in the Code-Switch project quite different from that in a lab setting.

Before participating in this initiative, I honestly didn’t give much thought to internships. After graduating, I swiftly found employment and didn’t consider internships. I believe there are ample opportunities available; however, the time commitment for the Code-Switch project—about seven hours a week—is quite suitable for me. I wouldn’t be willing to dedicate significantly more time, such as 20 hours a week, to this kind of work. I feel that seven to ten hours each week is a reasonable commitment, not only for me but possibly for others too. We discussed this during an internal meeting with other participants from the Code-Switch project, and many agreed that the time commitment was optimal. They didn’t want to spend more time because they simply didn’t have it to spare. So, while there are undoubtedly many internship opportunities out there, they may not be a good fit if the time commitment is too substantial, like 20 hours a week.

Indeed, many people might harbour concerns regarding this, but I believe it’s a typical stage in the journey of any student or graduate. Experience comes with taking the initial step, and this programme serves as a bridge transitioning from academia to professional development. Yes, it can feel intimidating, but it’s an inevitability we all must face when stepping into the real world after university. The earlier we confront this reality, the better. Taking this step sooner rather than later could ultimately prove beneficial in securing a more favourable job position.

Absolutely, being a part of this project has not just assisted me in my upcoming interview, but it has also boosted my confidence to apply for this role. Generally, as an engineering student or professional, you tend to interact more with data and experiments. However, involvement in a consultancy project like Code-Switch necessitates significant interaction with people. This experience, through meetings with Code-Switch members, clients, and other project participants, is all about human interactions which significantly enhances your confidence and communication skills, both of which are key during interviews. For me, it has been particularly beneficial as English is not my first language, and I believe my proficiency has improved considerably through these interactions.

The project has also granted me vital experience in the business sector, and I now feel more than capable to apply for similar positions. Had I not been involved with the Code-Switch project, I might have been more hesitant about stepping into consultancy, questioning my preparedness or suitability. However, now I stand at a different point, one filled with confidence and self-assurance. I have been trained, I have gained experience, and I feel competent. If nothing else, the experience in consultancy has taught me that. So yes, this project has been immensely beneficial in boosting my confidence.