How is a computer system analyst day normal?
#computer-science #information-technology #computer-software #computer-engineering #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer #computer
What does a typical day look like for a computer system analyst?
In short, it's mainly about (1) incident response and resolution, (2) following and refining standard operating procedures. More details below.
I work at Disney in a small team responsible for content distribution - or in other words, for delivering media files to Disney partners and to internal destinations. My official title is "Senior Systems Administrator", and a large part of my job is data analysis that is done by collecting and analyzing large amounts of machine data via tools like Splunk, Datadog and Solarwinds. So you could say that I am a system analyst, although that's only a part of my job. This is to establish my qualifications with respect to your question.
Assuming your question is about a "typical day" for a computer system analyst, I'd agree with John Faig's answer that it's a lot about incident response and resolution. When your work day (or night) begins, a system analyst is expected to go through a few processes or SOPs (standard operating procedures), a lot of which revolve around effective and efficient incident response:
- Shift start: determine if there's anything that needs attention right now and if not, review what happened since your last shift
- Any emergencies? If so, familiarize and help if you can.
- Review shift reports from prior shifts to get an idea what happened and if there are any unattended issues or incidents.
- Review any other alerts channels for any alerts that may have slipped through (email, Slack, etc.)
- Review recent incidents in the helpdesk or incident tracking system (JIRA, ServiceNow, Zendesk, etc.) to see if there is anything outstanding and/or ho the incidents were resolved
Once the above checklist is dealt with, two main tasks to work in throughout the shift.
- Regular shift duties:
- Respond to incidents as they occur, resolve and/or escalate as needed.
- If no incidents, work on projects. (Patching, migration, analytics, setting up alerts, onboarding, documentation, etc.)
- Shift end:
- Leave no loose ends: ensure incidents and projects you've worked on during the day have been documented and updated so that the stakeholders (e.g. your manager, teammates) can easily see what happened and what you've been working on
- Write up a shift report summarizing what happened and if there are any outstanding issues.
That is it!
(Hope this helps; if it doesn't - please let me know - I'd love to know what I can do better.)
John recommends the following next steps: