What a systems analyst really does
You sit between the business and the tech team, figure out how work really flows, and make the systems fit it.
What the work involves
What fills a typical week for systems analysts, built from O*NET occupation data.
- Troubleshoot problems where a system is not doing what the business needs and get it working again.
- Watch and interview staff to learn how information actually moves through their work.
- Map processes and data so you can see where systems fail to talk to each other.
- Write requirements and field mappings that developers and vendors can build from.
- Test new system changes and coordinate when they go live.
- Meet with managers to agree on what the system should do and what comes first.
- Train users on changed screens and steps.
What the days are like
- You are talking to people almost all day; this is a communication job as much as a technical one. Contact with others: 73% constant contact; Telephone conversations: 79% every day (O*NET Work Context)
- Other people's work depends on what you specify, so your mistakes become their problems. Work outcomes and results of other workers: 81% high responsibility (O*NET Work Context)
- You get a lot of say in what you work on and in what order. Determine tasks, priorities and goals: 65% a lot of freedom (O*NET Work Context)
- Precision matters; vague requirements cause expensive rework later. Importance of being exact or accurate: 54% extremely important, 45% very important (O*NET Work Context)
- Deadlines arrive weekly and long weeks are common. Time pressure: 50% once a week or more; Duration of typical work week: 56% more than 40 hours (O*NET Work Context)
How people get into it
Job Zone 4. Most roles call for a bachelor's degree, often in information systems, computer science or business, plus several years of related experience. Many analysts start in IT support, development or a business department such as finance or operations and move into the analyst role because they understand both sides.
The Firstday trial, easy to hard
Three simulated tasks at Corrigan Supply Co., a fictional company, with AI coworkers who message you, react to your work and coach with questions. Nobody scores you.
What the trial can't show: The trial compresses weeks of interviews, meetings and testing into short sessions with prepared transcripts and test results. It cannot show the slow pace of getting sign off from busy managers, office politics across departments over months, or the hands on time spent inside a specific ERP or vendor product.
Reading about it is one thing.
Find out how the work feels to you before you spend on a degree, course or job change. Your first trial is free.
Other careers you can try
Job details on this page are built from O*NET OnLine, 15-1211.00. This page includes information from the O*NET 31.0 Database by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA). Used under the CC BY 4.0 license. O*NET® is a trademark of USDOL/ETA.
