I am a Senior Software Software Development Manager for a product with a very large customer foot print, and multiple large deployments monitoring all infrastructure of Cloud environments for a large multi-national corp.
I also develop and maintain some modules of the product along with other senior developers from my team. I often work remotely or from office buildings near to my home.
My team is geographically distributed with footprint in US (CA), Mexico and India.
I will describe my regular and typical work day here. However, if there is a escalations, hot issues going on, it kind of takes over most of the work day.
Hope this helps.
I reach office or start work around 10 AM, and then spend 30 minute reviewing emails and slack. I mark important emails and slack messages for response later, and archive everything else. Then I spend next hour or so in status or sync-up meetings with my manager / DevOps teams / Cloud Admin teams / et al. I get out of this by noon, and that's when I take my first break with a strong black coffee.
I spend the next hour responding to the emails and slack messages that I had marked earlier. Then I make a list of ToDos based on the Urgent-Important quadrant rules. And this leads to lunch.
Post lunch, it is a team status meeting with my team and based on the team's priorities that I have received or generated from earlier meetings, emails, slack, etc, we discuss work prioritization, allocation, de-prioritization, strategy, timelines, etc. This lasts exactly an hour per team.
I keep early evening to look for and respond to any escalations, customer issue, PM requirements, working and sync-up with Sustenance Engineering POCs, etc. This also includes triage of bugs filed on my areas and assignment to individual module owners, who can either work on those directly or assign them to junior developer they are mentoring. I try complete all code reviews assigned to me during this time, and possibly work on something which is not very critical and can be taken off the team load.
(Evenings are completely devoted to getting back to home and spending time with my children & wife, meeting friends for a cup of tea, and reading one chapter of one of the books that are on my reading list.)
I keep the 9 PM to 10 PM slot for my US and Mexico team and it is split & conducted exactly in the same way that is done for my India based team during their post lunch slots.
I attend meetings with Dev Ops, Cloud Admins, Customer facing PMs etc in the night in the 10 PM to 11 PM slot, to get the feedback on the changes that my team has done for them, and if they see any red flag in operation and we might have to look at it.
And that wraps my regular day.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am a Senior Software Software Development Manager for a product with a very large customer foot print, and multiple large deployments monitoring all infrastructure of Cloud environments for a large multi-national corp.
I also develop and maintain some modules of the product along with other senior developers from my team. I often work remotely or from office buildings near to my home.
My team is geographically distributed with footprint in US (CA), Mexico and India.
I will describe my regular and typical work day here. However, if there is a escalations, hot issues going on, it kind of takes over most of the work day.
Hope this helps.
I reach office or start work around 10 AM, and then spend 30 minute reviewing emails and slack. I mark important emails and slack messages for response later, and archive everything else. Then I spend next hour or so in status or sync-up meetings with my manager / DevOps teams / Cloud Admin teams / et al. I get out of this by noon, and that's when I take my first break with a strong black coffee.
I spend the next hour responding to the emails and slack messages that I had marked earlier. Then I make a list of ToDos based on the Urgent-Important quadrant rules. And this leads to lunch.
Post lunch, it is a team status meeting with my team and based on the team's priorities that I have received or generated from earlier meetings, emails, slack, etc, we discuss work prioritization, allocation, de-prioritization, strategy, timelines, etc. This lasts exactly an hour per team.
I keep early evening to look for and respond to any escalations, customer issue, PM requirements, working and sync-up with Sustenance Engineering POCs, etc. This also includes triage of bugs filed on my areas and assignment to individual module owners, who can either work on those directly or assign them to junior developer they are mentoring. I try complete all code reviews assigned to me during this time, and possibly work on something which is not very critical and can be taken off the team load.
(Evenings are completely devoted to getting back to home and spending time with my children & wife, meeting friends for a cup of tea, and reading one chapter of one of the books that are on my reading list.)
I keep the 9 PM to 10 PM slot for my US and Mexico team and it is split & conducted exactly in the same way that is done for my India based team during their post lunch slots.
I attend meetings with Dev Ops, Cloud Admins, Customer facing PMs etc in the night in the 10 PM to 11 PM slot, to get the feedback on the changes that my team has done for them, and if they see any red flag in operation and we might have to look at it.
And that wraps my regular day.