- Search Graduate Jobs
- Browse Employers
- Accounting and advisory
- Environment and agriculture
- Banking and financial services
- Government and public services
- Charity, social work and volunteering
- Construction and property services
- Human resources
- IT and communications
- Creative arts and culture
- Education and training
- Mining, oil and gas
- Energy and utilities
- Retail and consumer goods
- Engineering, R&D and manufacturing
- Transport and logistics
- Entertainment, travel and hospitality
- Top 100
- Log in
- Sign up
A day in the life of…
Salesforce Consultant at Deloitte
Amelia Carbonie studied a Bachelor of Information Systems (Co-op) at University of New South Wales in 2016, and is now a Salesforce Consultant at Deloitte.
My alarm goes off from across the room, a deliberate measure so I have to climb out of bed to turn it off. I grab my phone, and go back to bed to quickly check some messages and read news before eventually getting out of bed at 7:15. The morning routine of getting dressed, eating breakfast, and getting ready is done within 30 minutes so I can get out of the house by 7:45.
I arrive at the client site right after 9, and usually I’m the first one from my team there. I’m currently working with a cross-functional team for a major insurance provider, and it’s the first time since I’ve started working at Deloitte that I’ve gotten a really good insight into what the other teams in the Digital practice at Deloitte does. We have UX designers, front and back end developers, and business analysts/developers each across the Sitecore, Mulesoft, and Salesforce technologies working together to achieve one common goal.
The first thing I do after unpacking is to head straight to the kitchen to fill up my water bottle – all the walking in the morning has made me thirsty, and staying hydrated also helps me to stay focused throughout the day.
I open Outlook to check both my email and task list. Today is the last day of Sprint 8 and we will be heading into Sprint 9 shortly. As the business analyst for the Salesforce team, it is my responsibility to update and send over our sprint planning slides ready to be presented back to the client product owners and the rest of the Deloitte streams later this afternoon. I retrieve the sprint planning slides from our previous sprint so I have an existing template to work off, and start labelling the progress of our previous sprint items as Complete, In Progress, or as an Ongoing task. For any items that I’m unsure of (mainly the technical items), I touch base with the Salesforce technical lead to get status updates on each of the outstanding items. I also start figuring out what tasks we will be covering in Sprint 9. My colleague, currently working from home, messages me on Skype to give me a hand with the slides as well.
10am is our team’s daily standup, where each of the different Deloitte streams provides a brief update on what we did the previous day, and what we are intending to do today. As today’s the last day of the sprint, most items are now done – the few outstanding items will be moved to Sprint 9 to finish off.
After standup I try to catch up with our technical lead for a few extra details, however he has a meeting with our project manager so I’ll need to wait a little longer before being able to catch up with him. Another graduate in my team asks me if I want some coffee, and it definitely feels like a good time for coffee. We both head downstairs and walk towards a coffee shop hidden in the alley way. It’s not my favourite coffee place nearby, but my fellow grad seems quite fond of the place, and for once it’s not packed.
I come back from my coffee trip and quickly check my calendar – I actually have a meeting right now that I didn’t notice earlier. I quickly grab my laptop in one hand, secure the coffee safely in the other, and as my hands are both full, throw my mouse in my pocket. I am slightly late to the meeting, where I am catching up with one of the product owners and client-side business analyst to get additional clarification on some defects raised in our SIT (systems integration testing) triage session last week. The product owner clarifies requirements regarding duplicate contact rules that were not functioning as required in Salesforce, and it’s something I’ll need to check after this meeting. I suspect this functionality was built in our development environment, but was not pushed into our SIT environment. We quickly go through the remaining 3 defects and clarify them within 15 minutes – it’s quite an efficient meeting by usual standards, and it’s also helped to close a few defects that don’t need to be addressed by my team as the defects aren’t expected business functionality.
However as we’re navigating through Salesforce, the product owner raises a concern about missing fields required for his team in Salesforce. I quickly look at the object metadata and find the missing fields have been created in Salesforce, but missing from the page layout. As we are reaching the end of our allotted meeting time, I decide that the easiest way to follow up on this is to organise another meeting with the product owner tomorrow. We both agree on tomorrow morning as a good time to catch up again, and we go our separate ways.
On returning to my desk, I quickly write down action items from my meeting, as well as pressing tasks for the remainder of the day. The first thing that needs to be finished is definitely the sprint planning slides – I’m meant to send these over to our release train engineer by 12pm so she can clean up the slides for the sprint planning session at 2. As the technical lead is still absent (probably at a meeting), I update the slides for sprint 9 with the spillover items from Sprint 8, as well as possible items to be built. I send the slides over to my team for feedback as this will be faster than waiting for them to come back to their desks.
As I wait for a reply, I send the follow up meeting invite to the product owner for tomorrow morning. I also extract all the fields from the required Salesforce objects, put them into Excel and update with brief requirements from the meeting (whether a field needs to go in a 1 column or 2 column layout view). I provide screenshots of Salesforce with the email I send over with further detail as I recall the product owners don’t have Salesforce access, so sending over just the Excel would be confusing.
I check my JIRA (our project tracking tool) related emails and see a lot of new defect tickets now assigned to me, some as a result of the earlier meeting today. These will need to be actioned later, but not immediately as they don’t have a hard deadline.
My manager replies to my email and answers the remainder of the questions I had for the sprint planning slides. The slides are done! I take a quick break and have a look at my phone –it’s time for lunch. I head to my usual lunch spot on the corner of the road, and decide to try something different – a roast beef sandwich. I eat on the ground level of the client building whilst browsing on my phone – the sandwich is a little messy, might stick to my usual chicken schnitzel sandwich next time.
As I return to my desk after lunch, I’m chased up by my release train engineer – turns out the slides weren’t sent out earlier by my manager, so I email them to her so she can finish preparation for the sprint planning session. A fellow graduate comes up to me for some help with data loading and attribute mapping into Salesforce. I explain to her the logic of the steps that she needs to complete, then guide her with uploading data into Salesforce. Once this is complete, I have a few spare minutes to go through our JIRA board and action and update some tickets before the sprint planning session.
The sprint planning session for Sprint 9 begins! The functional lead from each of the different streams take turns presenting their completed + outstanding items from Sprint 8, before discussing their goals for Sprint 9. I present the slides from the Salesforce team – having done this two weeks prior I am now familiar with the routine and handling any questions that come my way. The rest of the session continues with the other streams providing their updates – as this meeting is in a two-hour block, I’m conscious of the amount of time lost to do other things on my to do list, so I listen whilst also continuing to go through more JIRA tickets.
One of our offshore developers raises an issue with a ticket he has been assigned – he’s unable to replicate a defect that has been identified. I log into Salesforce and create a few test records before being able to successfully replicate the issue, and give the developer clear instructions on how he can reproduce the issue so he can eventually fix it.
It’s definitely a relief when the sprint planning session is over so I can head back to my desk and get more work done in the afternoon. I manage to update a few more JIRA tickets before some unexpected visitors drop by my desk! The SIT testing team are looking to get some verification and understanding over one of the capabilities we are testing in SIT. They run through their various queries with me and I answer them to the best of my ability – as they leave however I have another visitor waiting for me (feeling quite popular today with all these visitors!). This time the visit is a follow up to the earlier one today with my fellow grad – she’s done the initial upload of data into Salesforce, but needs help on one more section. I go through the required steps again and the reasoning behind why we are uploading the data in a particular way, until she feels confident enough to finish the rest herself.
Once my final visitor for the day has departed, I jump back onto JIRA for one last sweep of our task board. A few more defects have been fixed by the offshore development team and assigned to me for testing. I test the defects to make sure they’re fixed, and once I’ve confirmed they are working as intended, I mark them as done.