Software Engineer Apprentice Review

Software engineering is about gathering software requirements, designing software, creating software, and testing software. This involves emails, meetings, peer reviews, learning, programming, writing documentation, undergoing training, and open discussions. Requirements are normally discussed with a customer or authorised staff member, design involves both the user experience (UI) and the structure of data (architecture), creating software involves programming, debugging, discussion, and testing different ideas, and testing involves comparing a program against documentation that outlines what the program should do and how a testing result qualifies as a pass or fail. Along with this practical side, there is also writing the documentation. This involves many meetings and reviews. Documentation requires following templates, defining various parts of a project, and being as thorough as possible. Being an apprentice also means that university work occasionally overlaps with employment, and a level 4 diploma involves logging daily activities and researching domain-specific knowledge in order to answer questions. Reports to team leaders, managers, and project leaders are commonly done in person.

Absolutely. I've learned some of the fundamentals of programming, and can create programs in C#, Python, ADA, and VBA. I've also learned some Excel and other Office skills. Writing formal documentation and business-specific processes are also a big skill that helps substantially outside of work. Communicating effectively, especially over emails or during a presentation, has been honed substantially while working at BAE. Working as a team, recording information efficiently, and prioritising work between university, diploma, and the various responsibilities of employment all improve over time and benefit both my work and personal life. My internet research skills have improved too, having to research often for a diploma question or to learn something new in programming. Through university, I've also learned how to write more effectively with reports, as well as some programming-specific skills such as using a particular framework, using databases, or building a website. Finally, software engineering processes such as defining requirements, designing a program, and testing properly have all been freshly developed during work. I've also learned about source control, which I use both at work and at home.

University is fantastic, my only issues with it being location and lack of proper feedback on assignments. The actual content and opportunity (through digital resources and the library) is great and enjoyable to use. The diploma has two sections: answering questions and logging my daily work. The questions are somewhat enjoyable at times, and the logs do provide a nice way to look back over how far I've come and remind myself of my accomplishments at work. It can be a drag, but it's overall a positive experience. Actual work has changed over time. At first, lots of information was given rather late or not at all, and it's easy to feel lost. That being said, the professional attitude towards personal issues and individual variation (such as learning speed, talent, and previous ability) is brilliant and definitely makes it easier. Once I found a placement that had proper work with a team (and team leader) that communicates, my enjoyment at work increased massively and even prompted some programming at home. Overall, I enjoy my programme and look forward to both work and university.

There is a distinct lack of information at first, but the actual induction, training, and layout is done very well. The yearly structure is simple, straightforward, and effective. If I had to come up with problems in the programme, I'd say that the diploma could use some more structured, standardised time for writing logs. I'd also suggest some resources or structured learning to prepare for the third year of university - it's well known that the third year of university is difficult and that the previous two years do not cover enough content to properly prepare apprentices. The actual layout of 3 days work, 2 days uni (two years), then uni full time (one year), then work and diploma full time (one year) with the final six months being a portfolio that is assessed at the end of the apprenticeship is very simple and effective. It can be a lot to balance, but it's also very doable.

For personal issues such as those regarding medications and physical health, support has been incredible. In terms of accidents and emergencies, BAE Systems has been massively accommodating and understanding. I feel like as an apprentice, there is less support for actual learning than I'd have hoped for, but I assume this is because university is supposed to make up for it. There is also an absolutely incredible response when reaching out for specific help, both in general and when asking particular individuals or management. Everyone is positive and willing to help, and I'll always be redirected to someone who can assist otherwise. Management try to make people feel comfortable and can have a normal conversation in a way that makes things seem relaxed, but not unimportant. There is a lot of support for diploma-related activities, and suggestions are often listened to.

East riding college offer a library, as well as digital resources, that cover lots of interesting material as well as having content that is great for work, assignments, and personal projects. Classes are slow-going and can often feel under standard when compared to the work done at BAE and the experience expected by work, as well as the ability displayed by colleagues, but the college offer plenty of ways to teach yourself if you are inclined. Some tutors do not seem particularly knowledgeable about what they are teaching and some clearly lack (relevant) experience, but it's also the case that they have to cover a wide range of topics and try to accommodate every students' needs, so it is unclear to me how much of this is a lack of proper support and how much is the nature of educational facilities. Having said this, tutors are often willing to help or at the very least, throw some ideas at you or redirect you to the proper resources if necessary. Feedback is often poor, but this is slowly improving after constant complaints and suggestions for improvement. Creative support for projects is very good, as is the mental health and financial support. Tutors are often flexible and understanding, and also allow us to put work first, and have never been problematic in this sense.

The programming fundamentals, resources (such as books), and programming at home (both out of necessity with assignments, and enjoyment) has all helped with my role. The fundamentals are glossed over at work, and there's a "learn through doing" approach that is slow and inefficient when starting out. Library resources help with making connections I wouldn't have otherwise, and can help with things such as learning effectively, writing proper documentation, good practices within programming, designing in a pleasant and functional way, as well as project ideas. These are skills that help at work through being more professional, quicker, and fuelling motivation. Motivation is further fuelled by doing things that are different to work that inspire working at home, and ensure programming practice when programming isn't a priority at work at that moment in time. Some units are also directly beneficial. Object Oriented Programming helped a lot with the basic understanding of C# and Visual Studio, and is fun too. Websites offer networking capability and an different way of looking at programming which has helped at work, and Databases is directly useful as databases are used in some projects. Having a fundamental understanding of databases has greatly reduced project time that would have been spent learning, and it applicable in a wide range of things. The upcoming networking unit seems beneficial, looking ahead has already helped me at work. The course also offers decent personal management, project management, and problem solving units and tasks that all assist my work in a general sense. The actual resources and support from tutors is a benefit to my role too, as bouncing some ideas, directing my learning, and fuelling creativity is all encouraged in the college environment. College also provides an opportunity to discuss non-sensitive work, and general programming, at length in a relaxed environment with colleagues. Teaching other students and helping them with their college work also gives me the chance to solidify learning. Finally, the assignments provide a means to experiment in a way that isn't wasting work time or potentially damaging to BAE Systems. I can practice programming, learn about source control (accidently deleting important data at times), and learn without having a negative impact on my role.

Professional networking, training courses, award ceremonies, outward bound, and various walking, meditation, and other health initiatives all allow employees to get involved. There are quite a few lunchtime activities to do instead of having lunch, and employees come up with their own extra-curricular activities too, such as playing a sport. A makerspace is being discussed at the moment, offering a place to work on personal projects with a community and resources that would otherwise be unavailable.

Yes

From a personal point of view, BAE offers a lot of flexibility, understanding, and personal growth. Professionally you will learn much more than your peers, in many different ways. You'll learn technical details, such as various programming languages, as well as documentation and general software engineering skills, each of which will be useable for the rest of your life. Even business-specific information is tremendously useful in this way, as most software engineering practices and skills are transferable. I'd even say this is often obviously the case. Your professional and social network will expand a lot, and you'll be able to work alongside and learn from multi-decade professionals in the field. You never stop learning and getting better in all aspects of your life once you work here, and you mature very quickly. It goes without saying, the financial, employee incentive, and professional advantages are brilliant as well. There are opportunities to work abroad, and work is pleasant and fun most of the time as well. Of course there are stressful times too, but the support is there and you are rewarded for doing well. Simply, BAE Systems is fun, fantastic professionally and financially, and if you have any experience or drive to do well in the role, you will go very far. Being motivated to help yourself is rewarded massively, and you are only really limited by your own commitment to the programme and company. Additionally, although I am new to the business, it appears that there is plenty of room for progression within the business. I can say this with certainty regarding the early stages of your BAE Systems career.

When applying, be yourself and don't be afraid to talk about your hobbies and personal life. Emphasise anything related to your role of course, but try to relax! Communicate and play as a team member in any group activities. Both when applying and if you get in, be open minded. When working, constantly try to learn. You're surrounded by established, impressive professionals who are willing to help, as well as having more money, free time, and future potential than you'll have ever had, and this opportunity does have a time limit. Take responsibility for learning, volunteer for opportunities, read or practice a little at university and at home, talk with your colleagues and classmates. If doing software, I'd recommend doing some fun projects at home to peak your interest. At university establish what you need to do for a good grade, do it well, but do quickly. The real benefits come from using that time to improve your professional skills and theory understanding, and practice programming outside of work in a way that allows you to recharge from work too. Along similar lines, take breaks often, try to lead a balanced life (socialise outside of work, sleep properly, have a hobby or two), and speak up if you have any issues. Keep healthy and outside of university and a little light reading/practice, don't feel guilty if you keep work at work. In essence, take responsibility for your own learning and development, speak up when you have a problem, network, and have fun. Oh, and if you're applying for a software role, don't worry about mathematics. University covers it more than well enough, and it isn't any more difficult than maths you'll have already done. Maths can definitely help, but there is plenty of resources and support, and it is absolutely not necessary that you are brilliant with maths. In a similar line of thinking, a lack of experience is not a negative, as long as you ask questions, stay curious, and proactively engage in order to learn and make up for it. Also log everything you do! This will help with university assignments, diploma logs, and can serve as a guide or cheatsheet later on if you use a program or language then forget a lot of it in the future. A document for individual programs, and an overall log that you spend a couple of minutes in the morning or at the end of the day to document the overall "what I've done today" in note form, and you're sorted.