5 answers
Asked Viewed 236 times Translate

How is a computer system analyst day normal?

Please rephrase the question or add context or an example to clarify what types of answers you're looking for. (The question doesn't sound very clear - or grammatically correct to me - but then I could be wrong as I am not a native English speaker.) Alex Gerulaitis

+25 Karma if successful
From: You
To: Friend
Subject: Career question for you
100% of 5 Pros

5 answers

Updated Translate

Alex’s Answer

Answering this question:

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.)

Updated Translate

John’s Answer

To understand specific job responsibilities, you can review actual job postings at websites like Indeed.com. The term systems analyst is a general term and the daily responsibilities vary from company to company. I tend to view IT positions as either a server administrator or a network administrator. In either case, the IT person makes sure the server or the network is running as expected. This includes diagnosing problems, installing updates, user change management (add/delete change users). Both positions have a range of diagnostic tools that monitor the servers or network and identify problems. Most of the time, the server administrator supports products like Google for Education or Google for Business, Microsoft Server, Microsoft Exchange Server, Microsoft Sharepoint Server and so on. Sometimes, companies develop their own applications instead of buying them from a vendor. In this case, the server administrator might need to know a little more about application development. I've not run into too many server or network administrators that don't like their job. If you get an undergraduate computer science degree the starting salary is about $70K, but I know folks that have a general undergraduate degree and learn about the products through vendor training courses. Cisco, Microsoft, Google, and others have courses and exams to get certified using their products.

John recommends the following next steps:

I would reach out to a local business and talk to their IT folks about their daily routine.

Updated Translate

Estelle’s Answer

It is a normal day for a person with a degree in a computer science field. You may find yourself working for a large company as on of many analyst working 9-5 in a cubicle. Or you may find yourself working for a smaller company with more flexibility (not a cubicle) but maybe longer hours getting projects finished because there are less of you working on them. Whatever you decide to do in life, I hope you find it interesting and at times rewarding. We dont work for fun but to make money.

Updated Translate

Chaz’s Answer

A typical day for a computer analyst starts by checking the meetings planned for the day. The next step is usually preparing for the meeting. This could involve researching a topic, preparing a presentation, or preparing a list of questions needed for the meeting.

Updated Translate

Bob’s Answer

Does this answer your question?