西瓜视频

My role mainly included receiving unreleased devices from various supplies, which I would study the data sheet for and use to develop a proof of concept for new features or hardware we (the team) wanted to implement in the architecture. Every couple of sprints we would have demo's where we created a proof of concept; here I would solder, code and build to make the proof of concept On a day to day basis, we would have meetings with suppliers where they would explain how their software or hardware worked and we would negotiate making specialised versions and alterations to their products to fit our needs. As a networks and systems engineer I would use Corvus and CANalyser to trouble shoot signals in test vehicles and build a triage for other team members to use to make troubleshooting easier.

Yes I learnt and developed on a lot of skills, embedded software development, (low-level) software development with C & C++. Programmatic problem solving, public speaking through presentations.

Yes I would say I was given a lot of responsibility, one way this was done and I appreciate was the writing of my JIRA tickets. Rather than each team member being assigned a ticket, we were all instructed to create stories and tasks which were in alignment of the EPICs assigned to the team. I appreciated this because, it encouraged me to have a deeper understanding of the work the team was doing and what the mission was. As well as this is created a real sense of ownership over my work, as I set the deliverables and success criteria. And I was responsible for ensuring the team was moving towards the EPIC and not away.

I received a lot of support while one placement, I'm so grateful for it. I was never afraid to ask questions or say that I did not understand at any point. The team were very patient with me directing me to resources whether it was a youtube video or a confluence page to help explain my gap in knowledge and even sitting down to explain anything in their free time. Additionally when I wanted to learn more they were boost up my skills.

It was nice, I never felt uncomfortably pressured to deliver. My motivation to deliver came from a sense of belonging to the team and contributing positively rather than fear of underperforming or upsetting my superiors. Within my team, I enjoyed my time, I would say that everyone are people I enjoyed hanging out with not just working with, I enjoyed going on many work socials with the team and having chats with them in the office.

I really enjoyed my placement overall. It provided valuable hands-on experience and helped me develop both technical and professional skills. One aspect I particularly appreciated was the opportunity to contribute meaningfully to real projects and see the impact of my work. However, I do wish there had been more structured opportunities to explore other teams and departments. Gaining broader exposure would have helped me better understand the wider business and potentially discover other areas of interest. That said, the experience was still highly rewarding and has positively influenced my career direction.

Yes

Be proactive if you're going to work at JLR, it is very easy to be forgotten I have found, and I had to strive almost daily to not only find work but to also find opportunities to develop myself. There are a lot of opportunities at JLR you just need to actively seek them out. In terms of the application process, make sure you reach out to someone who has done the placement before and ask for their advice. Ensure you have a lot of projects you can talk about in depth, show your transferable skills and most importantly tie them to the JLR core values; customer love, integrity, unity impact and growth.