Build the technical base
Computer science, information technology, information systems and related study are common routes. The right depth depends on the kind of systems and employers you are targeting.
Preparation · Education and evidence
A bachelor’s degree is typical in U.S. BLS guidance, but the page also notes that some employers hire candidates with a business or liberal-arts degree and relevant technical skills.
Computer science, information technology, information systems and related study are common routes. The right depth depends on the kind of systems and employers you are targeting.
Analysts connect technology with organizational goals. BLS says business coursework or management information systems can be helpful; domain knowledge matters in fields such as health care or finance.
Practise turning a vague problem into questions, a simple process map, clear requirements, test cases and a short explanation of trade-offs. Keep examples fictional or use data you have permission to share.
A practical, low-cost work sample
Imagine a small library’s website shows a room as “available,” but the booking desk says it is reserved. Before suggesting software, write down:
Then make a one-page process map and a few test cases. Ask someone familiar with operations to challenge your assumptions. The point is to demonstrate clear reasoning, not to claim professional experience.
Try the interactive order-status case →A separate fictional case, with different records and a private investigation note. No employer, customer or production data.
A route is not a checklist of expensive purchases
Some employers prefer graduate study for particular roles, but BLS does not say every systems analyst needs an MBA or master’s degree. Start with the employers and role type you actually want.
| If a posting emphasizes… | Look for evidence of… |
|---|---|
| Requirements and workflows | Interview notes, process maps, user stories, clearly stated assumptions |
| Data and reporting | Careful data questions, query or spreadsheet work, definitions and quality checks |
| System changes and testing | Test cases, edge conditions, environment awareness and change documentation |
| A regulated or specialist industry | Relevant domain knowledge, privacy and controls, plus the role’s stated technical needs |
A national median, wage range and industry differences—with caveats about what those figures can tell you.
Read this guide Explore this questionWhat the U.S. employment projection measures, what annual openings mean, and what to check locally.
Read this guide Explore this questionA realistic look at collaboration, accuracy, autonomy, pressure and the work products behind the job title.
Read this guide Explore this questionWhich tasks may be assisted, where checks matter, and why there is no reliable replacement percentage.
Read this guide Try the workInvestigate conflicting fictional records, choose a safe first move and leave with a note of your reasoning.
Open the caseSources and scope
Education statements summarize U.S. BLS guidance; employer requirements differ. O*NET provides occupational task and knowledge context. This original exercise is illustrative, not a credential or assessment.
Occupational information on this page is adapted from O*NET OnLine, sponsored by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), under the CC BY 4.0 license. Ikigain has adapted and interpreted the information; USDOL/ETA has not approved, endorsed or tested these modifications. O*NET® is a trademark of USDOL/ETA.
Sources checked 28 September 2026. This is an editorial guide, not a local salary quote, hiring guarantee or individualized career advice.
Saved paths and work-sample notes stay in this browser. Fictional exercises are for exploration, not professional assessment.