Can you tell me what a typical work day is like? What are your daily tasks and how do you get them executed?

Also, what kinds of programming languages do you use? How do you differentiate your role from that of a Graduate Data Science role?

Hi, I'm an SE grad in my first rotation. A typical day would look like: I like to do 30/45 mins of self-lead learning (currently it's GCP), then I'll have a daily stand up meeting in the AM, let the team know how my tasks are going/if I have any blockers. After that I will spend some time working on my tickets that I discussedin the standup meeting, lunch, probably another call with the dev team to go through any issues, there's some time for side of desk projects & personal development goals, and a bit of training towards foundational certifications too. On a more felxible basis there are things like TechTalks you can tune into, wider team meetings to understand what's going on within your department etc, sprint planning every fortnight ish & then a demo for the sprint you've just finished too.
As for the programming languages, I personally have been learning a low-code no-code (software that writes software) called Pega to use in my day to day tickets, but grads in other teams have been using languages like Python, GoLang, and JavaScript. I wanted to keep practicing my coding throughout this rotation so I chose to do that as personal development goal, and I chose to learn a new language too (Java) - there's also loads of opportunities to use a language outside of your day to day (hackathons/coding challenges/self lead learning)
Hope that helps!

Thank you so much Jenny. This is a detailed description and I love it.
How are you assigned tasks and can you give me a typical example?

So in the sprint planning they will decide which user stories (basically tasks that need to get done dev wise) and then they will estimate how long each story will take & if the team has capacity this sprint etc. they'll then assign you tasks / you can volunteer when you feel more confident based on your personal capacity

Hi Goodness, that really depends on how your team works. I believe most teams in LBG use agile methodology (it's worth a google for more info). Some teams use scrum which is where you have 'sprint planning' to decide who is assigned to what task. One of my teams uses kanban which is where you assign the tasks to yourself if you have the capacity to take it

An example might be a user story something like: "When the customer chooses service X on the claims form, I want the following Qs to be visible (i.e. their visibility is conditional on a previous answer) Qx Qy Qz..." I will then have to go into the application and make sure the logic of that user story has been developed, maybe do some unit test or send it to the test team to run tests :)

But yes, to second Bethany it's down to the team :)

Thanks Bethany and Jenny. I guess I still have a lot of learning to do. Thanks for taking your time to answer my questions.

No problem! :)

Hi, as a grad SE working in the Cloud Center of Excellence in an agile team, a typical day would start with a catchup with my mentor and fellow graduates/apprentices in a team, a very informal drop-in session for support and guidance. The first meeting of the is the daily standup, for updating the team about your progress, work and requesting support if needed. The rest of the day depends on what projects or tasks you're involved with but I usually spend a good part of it working on the tickets I am assigned with. Finally the team has a drop in a session at the end of the day for support and questions. Hope this helps :)