Short version: A computer systems analyst sits between the business and IT, translating what people need into systems that actually deliver it. You don't need a specific degree, but you do need SQL, requirements elicitation, process modeling, and depth in one enterprise platform (ServiceNow, Salesforce, SAP, Workday, or a major cloud). Add a credential — IIBA's ECBA or CBAP, PMI-PBA, ITIL 4, or a vendor cert — and build a small portfolio of real artifacts. For a focused career changer, that's roughly nine to eighteen months part time. The U.S. Bureau of Labor Statistics projects about 10% growth through 2033, faster than average. Then the hard part isn't the skill — it's getting a human to see your resume, which is where a strategist changes the math.
On this page
What a computer systems analyst actually does
A computer systems analyst — sometimes called a business systems analyst, IT analyst, or solutions analyst depending on the employer — sits at the boundary between people who use software and the systems that run the business. The job exists because that boundary is almost always leaky. Someone in finance needs a new report, procurement needs the ordering system to talk to the ERP, sales needs Salesforce to reflect the new pricing model, and the leadership team wants to migrate a decade-old on-premise application to the cloud without breaking anything. Every one of those requests starts as a fuzzy conversation and ends as a working system, and the analyst is the person who does the translation in between.
In practice the work breaks into five recurring activities. You elicit requirements by running interviews and workshops with stakeholders, watching how work actually gets done, and asking the questions that surface the requirements people forgot to mention. You document those requirements in a form that developers, testers, and vendors can build against — user stories, use cases, functional specifications, business rules. You model processes — the current-state, the future-state, and often several options in between — using BPMN, UML, or a lighter swimlane diagram. You partner with engineering, product, and vendors through design and build, answering the interpretation questions that always come up mid-flight. And you own testing and rollout, writing test plans and user-acceptance scripts, coordinating training and change management, and staying close to the system long enough after go-live to catch what didn't survive the transition.
The role varies more than most job titles suggest. In a Fortune 500, a systems analyst may specialize in one platform — SAP, Workday, ServiceNow, or Salesforce — and spend a career going deep. In consulting, the same title means you rotate through client engagements, learning a new industry every quarter. At a mid-market company, you may be the sole IT analyst, doing everything from writing requirements to running vendor selections to training end users. Understanding which flavor you want changes both the credentials and the platform you should invest in.
Variants and adjacent titles
You'll see the same skill set advertised under a dozen different names. Business systems analyst and IT business analyst are the most common near-synonyms. Solutions analyst and functional analyst lean toward vendor implementations. Applications analyst often lives inside a specific platform team. Systems consultant is the consulting-firm version. All of them share the same core work; the differences are industry, employer type, and how deep into one platform you're expected to go.
Education & degree paths
There is no single required credential to become a systems analyst, and that's genuinely good news. You have three viable routes, and the right one depends on your time, money, and starting point.
Route 1 — A bachelor's degree in a related field
Most working systems analysts hold a four-year degree, most commonly in information systems (MIS), computer science, business analytics, industrial engineering, business administration, or a related quantitative field. A degree gives you a structured foundation in databases, software engineering concepts, and organizational behavior, and it still clears HR filters at the large, regulated employers — banks, insurance companies, healthcare systems, federal contractors — where a degree is functionally required. It's the slowest and most expensive route, but if you're early in your education or already studying one of these subjects, it's the natural on-ramp. Note that any major can work if you pair it with the technical skills — plenty of analysts have degrees in psychology, communications, or the humanities.
Route 2 — An advanced degree
A master's in information systems (MSIS or MIS), business analytics, or an MBA with an information-systems concentration is a strong lever for career changers and for analysts targeting senior, consulting, or management roles. Advanced degrees make sense when you already have some professional experience, need a credential to switch industries, or want to accelerate toward solutions-architect or IT-management tracks. The programs typically run one to two years and cover the requirements-to-architecture pipeline in depth, along with the organizational and financial context in which enterprise systems get chosen.
Route 3 — Non-degree route
Plenty of working systems analysts do not have a matching degree — they broke in from help desk, QA, customer support, application support, or an adjacent business role and picked up the skills through certificates, on-the-job training, and deliberate portfolio-building. This route trades cost and speed for the need to be more intentional: without a degree to signal capability, you need a professional certificate, a small portfolio of artifacts, and enough hands-on time in a real environment to speak credibly in interviews. The route works, but it works fastest for people who can find an internal move at a company that already knows their work.
Core skills to build
Here's the stack, in the rough order you should learn it. Resist the urge to chase enterprise-architecture frameworks or a shiny cloud platform before you can write a clean requirements document — that's the single most common way beginners waste months.
| Skill area | What you actually need |
|---|---|
| Requirements elicitation | Interview and workshop facilitation, five-whys and root-cause techniques, user-story and use-case writing, business-rule capture, backlog refinement. The most-requested skill in analyst job descriptions after SQL. |
| Process modeling | Current-state and future-state mapping in BPMN, UML activity/sequence diagrams, swimlane diagrams, and simple flowcharts. Fluency in one diagramming tool — Visio, Lucidchart, draw.io, or Miro. |
| SQL & data | SELECT, filtering, JOINs and what each does to your row count, GROUP BY and aggregation, subqueries and CTEs, and enough data-modeling vocabulary to read an ERD and reason about integration. |
| Functional specifications | Writing specs that developers, testers, and vendors can build against — acceptance criteria, edge cases, non-functional requirements, and traceability from business need to implementation. |
| Systems & integration concepts | How APIs, batch integrations, event streams, and middleware move data between systems. You don't have to build them, but you have to specify them and reason about failure modes. |
| Testing & UAT | Test-plan design, writing UAT scripts, defect triage, and running a UAT cycle with business users. The last-mile skill that turns a paper design into a system people actually use. |
| One enterprise platform | Depth in at least one of ServiceNow, Salesforce, SAP, Workday, Oracle EBS/Cloud, or a major cloud (AWS, Azure, GCP). Platform depth is what unlocks the higher-paying roles. |
| Facilitation & writing | Running a workshop with a room full of stakeholders, translating jargon in both directions, and writing documentation people actually read. Hiring managers worry about these more than any tool. |
Certifications & credentials
A credential won't replace a portfolio or real experience, but it's a credible signal — especially when you lack a matching degree or direct experience — and the structured curriculum keeps self-taught learners on track. The ones worth your time fall into two buckets: general business-analysis credentials, and vendor certifications on the platform your target employers use.
- IIBA ECBA (Entry Certificate in Business Analysis). The most respected entry-level credential in the field, aimed squarely at new entrants. Covers the BABOK Guide fundamentals — requirements, analysis, and solution evaluation.
- IIBA CBAP (Certified Business Analysis Professional). The senior-tier credential once you have several years of experience. Widely recognized and often listed as preferred on senior job descriptions.
- PMI-PBA (Professional in Business Analysis). PMI's business-analysis credential, useful if your work sits closer to project management and delivery.
- ITIL 4 Foundation. Essential context if you'll work anywhere near IT service management — the language most enterprise IT organizations use to describe how they run.
- CompTIA Project+ or Scrum credential. Delivery fluency — how work moves through an agile or hybrid team — is table-stakes for most modern analyst roles.
- One vendor platform certification. Salesforce Administrator, ServiceNow CSA, SAP Business Analyst, Workday HCM/Financials, or an AWS/Azure/GCP fundamentals credential. Pick the platform your target industry uses and go deep on one, not shallow on many.
The step-by-step path
Seven steps, ordered so each one earns you the input for the next. Don't skip ahead — the order is what makes this efficient.
Understand what a systems analyst actually does
Before you invest months, get clear on the real day-to-day. A systems analyst sits between the business and IT, gathers requirements, models processes, writes functional specifications, and shepherds software and infrastructure changes through design, testing, and rollout. Read job descriptions from three or four target employers, talk to two working analysts on LinkedIn, and honestly assess the fit. If you like meetings, ambiguity, and writing, you're in. If you'd rather build the software yourself, look at engineering instead.
Choose your education route
Pick one of the three routes — a bachelor's in a related field, an advanced degree, or a non-degree path built from certificates and adjacent-role experience. Optimize for what gets you to provable competence fastest given your budget and starting point. If you already have a degree in an unrelated field, you almost never need another one; a professional certificate plus a small portfolio is usually the faster path.
Build the core systems-analyst skill stack
Work through the eight skill areas in the table above, in order. Spend the first three months on requirements elicitation, process modeling, and SQL — those are the skills every job description asks for. Then add functional-specification writing, testing and UAT, and one enterprise platform. Learn one diagramming tool cold rather than dabbling in three. Fluency in one BI or cloud platform beats a shallow tour of five.
Earn a credential to validate your skills
Choose based on where you are. New to the field: IIBA's ECBA plus one vendor certification (Salesforce Admin, ServiceNow CSA, or a cloud fundamentals cert). Some experience already: CBAP or PMI-PBA, plus a deeper vendor credential. Add ITIL 4 Foundation if you'll work near IT service management. Credentials keep self-taught learners on track and give a hiring manager a credible signal on the resume.
Get hands-on with real systems work
Build a small portfolio: a full requirements document for a realistic scenario, a current-state and future-state process map, a test plan with UAT scripts, and a short case study on a system-selection or data-migration exercise. Contribute to an open-source project's requirements or documentation. If you're already working, volunteer for the analyst-shaped work at your current job — the requirements gathering nobody wants to write up, the process map that would help the team. Real artifacts are what open interviews.
Gain experience and break into your first role
Get reps through the shortest route available: an internship, a help-desk or application-support role, a QA or junior project-coordinator seat, or an internal move from operations, finance, or HR into an IT-adjacent role. Then target genuinely entry-level titles — junior business systems analyst, IT analyst, associate systems analyst — tailor each application to the platform and industry, and pursue referrals so a human sees your work rather than an algorithm screening you out.
Land the role and keep advancing
Prepare for behavioral, case, and light technical interviews — expect requirements-elicitation scenarios, a process-modeling exercise, and SQL questions. Negotiate your offer, and once hired, deepen toward one of the senior tracks: senior systems analyst, solutions architect, product management, or IT program management. Two years of shipped systems in one platform is usually enough to unlock a meaningful salary jump.
Map the seven steps to your calendar.
Use the free Career Path tool to lay out the skills, certifications, and portfolio artifacts on a realistic timeline — then let a strategist run the search when your materials are ready.
Start with the Career Path tool →See how Marqee worksA realistic timeline
Every path is different, but here's what the five most common trajectories actually look like, from starting point to a systems-analyst seat.
- New graduate → junior systems analyst0–6 months post-graduation. If you majored in MIS, CS, or business analytics and did an internship in an analyst-shaped role, expect to land a junior title within the first six months of a focused search. Add an ECBA credential during senior year to strengthen the resume.
- Career changer (self-taught) → associate analyst9–18 months of part-time study. Roughly three months on requirements and SQL, three on process modeling and one enterprise platform, three on portfolio artifacts and a credential, and the rest on the job search. Faster with a bootcamp or full-time study.
- Help desk / support → business systems analyst1–3 years internal. The most reliable non-degree path. Ship one platform certification, take on requirements-gathering work informally, and apply for internal analyst openings once you have two credible references from IT leadership.
- QA or project coordinator → systems analyst1–2 years. QA folks already read specifications critically and understand testing; project coordinators already own scope and stakeholder wrangling. Both are half an analyst already. Add ECBA and one platform cert, and the internal move gets fast.
- Adjacent business role → analyst1–2 years. Someone who's spent time in finance operations, HR ops, procurement, or sales ops already understands one enterprise system deeply. Add SQL, a business-analysis credential, and formal process-modeling skills, and the pivot to an IT-side seat is straightforward.
How to break in
Breaking in is rarely about a single "get hired" move — it's about a bridge role that gets you close to systems work, then a sideways step. Four bridges reliably work.
Bridge 1 — Help desk or application support
The classic path. A support role puts you inside the systems all day, exposes you to real user problems, and builds relationships with the IT teams that eventually hire analysts. Take on the ticket work nobody wants — the ones that require documenting a workaround, the ones that need a small process fix — and you'll build both an internal reputation and a portfolio without leaving your seat. Twelve to eighteen months in support with a certification and internal advocates is a well-worn path into a junior analyst role.
Bridge 2 — QA or test analyst
QA and systems analyst are close cousins. QA people already read specifications critically, know how to write test plans, and understand release management. Add explicit requirements-elicitation skill, a diagramming tool, and one platform certification and the move is straightforward. Internal QA-to-analyst promotions are common because the team already trusts your work.
Bridge 3 — Adjacent business role
If you've been in finance operations, sales ops, procurement, HR ops, or a similar function, you already understand at least one enterprise system deeply — and probably better than the IT people who administer it. That domain depth is enormously valuable to an IT team hiring for that platform. Learn SQL, earn a business-analysis credential, and pitch yourself for the analyst role that sits between IT and your current function.
Bridge 4 — Consulting analyst
Large consultancies (the Big Four, Accenture, IBM, and specialist boutiques) run structured entry-level analyst programs, often hiring both new grads and career changers. The bar is high and the hours are demanding, but you emerge two years later with exposure to a range of industries, a strong platform depth, and a resume that opens doors at almost any internal analyst role afterwards.
Salary & job outlook
According to the U.S. Bureau of Labor Statistics, the median annual wage for computer systems analysts was roughly $103,000 in the most recent OES release. Here's what the range looks like at each level of the career.
| Level | Typical US base salary |
|---|---|
| Junior / associate systems analyst | ~$65,000–$80,000 |
| Systems analyst (mid-level) | ~$85,000–$105,000 |
| Senior systems analyst | ~$105,000–$130,000 |
| Lead analyst / solutions analyst | ~$125,000–$160,000 |
| Principal analyst / solutions architect | ~$150,000–$200,000+ |
Total compensation stretches further at tech and finance employers, where bonuses often add 10–20% and equity or profit-sharing can add another 10–25% at senior levels. Consulting shops pay similar bases with heavier travel loads and stronger bonuses. Regulated industries — healthcare, insurance, government — tend to pay closer to the base ranges but come with more stable hours and stronger benefits. Location matters too: San Francisco, New York, Seattle, and Boston pay a meaningful premium over Midwest and Southeast markets, though remote-friendly roles have compressed that gap.
The U.S. Bureau of Labor Statistics projects employment of computer systems analysts to grow about 10 percent through 2033, faster than the average for all occupations, adding tens of thousands of jobs over the decade. The drivers are all secular: continued cloud migrations, ERP and CRM modernizations, cybersecurity work spurred by regulatory and threat pressure, and the ongoing digitization of industries that haven't finished the last wave. Automation is changing the toolset — configuration and low-code platforms handle work that used to require custom development — but it raises rather than lowers the value of analysts who can frame the right requirements and judge whether a proposed system will actually work for the people who have to use it.
A day in the life
A typical day starts with a stand-up around 9 a.m. — fifteen minutes with the engineering and product folks on your current project to align on the day's work and surface blockers. From about 9:30 to noon you're usually in elicitation mode: a stakeholder interview, a workshop with a business team, or a working session with a vendor. You take notes, ask clarifying questions, and turn the raw conversation into user stories or business rules before you lose them. Around midday there's usually a lunch break where you catch up on Slack and skim the emails you missed during the morning workshops.
The early afternoon is documentation mode: writing up requirements, updating a process map, drafting a functional specification, or refining acceptance criteria. Then a mid-afternoon block for partnership work — answering developer questions on the current sprint, sitting with QA to walk a test plan, reviewing a vendor's design deliverable, joining a data-migration checkpoint. Late afternoon usually mixes in some quiet analysis: writing a SQL query to validate a report, reviewing an integration spec, or preparing materials for the next day's workshop. The rhythm has plenty of meetings, but the through-line is that every meeting produces a written artifact, and every artifact moves a project closer to shipping. For the exact tactical guide once you land interviews, see the Computer Systems Analyst resume example and matching interview questions.
Frequently asked questions
A bachelor's degree is common but not universally required. Most working systems analysts hold a four-year degree in information systems, computer science, business analytics, or a related field, and larger and more regulated employers still prefer it. A meaningful share of employers, however, hire on demonstrated skill — SQL fluency, credible process modeling, a professional certificate, and a track record from an adjacent role such as help desk, QA, or business operations. If you can prove with real artifacts that you elicit requirements, model processes, and shepherd changes to production, the lack of a degree is rarely a hard blocker, especially at mid-market and consulting employers.
For a focused career changer studying part time, roughly nine to eighteen months to job-ready is realistic: about three months on business analysis fundamentals and SQL, three on process modeling and one enterprise platform, and the rest on portfolio artifacts, a credential, and the job search. Studying full time through a bootcamp or intensive certificate can compress the skill-building to four to six months. A traditional bachelor's degree in information systems takes about four years but is not the only route. Most people who break in through an adjacent role like help desk or QA move into a systems analyst seat within one to three years.
The core stack is requirements elicitation, business-process modeling (BPMN or UML), SQL, functional specification writing, systems and data integration concepts, testing and user-acceptance planning, and working knowledge of at least one enterprise platform such as ServiceNow, Salesforce, SAP, Workday, or a major cloud. Just as important are the soft skills: facilitating a workshop with a room full of stakeholders, translating jargon in both directions, and writing documentation people actually read. SQL and clear written communication are the two skills that show up in almost every systems-analyst job description.
The most portable general credentials are IIBA's Entry Certificate in Business Analysis (ECBA) for new entrants and the Certified Business Analysis Professional (CBAP) once you have experience, PMI's Professional in Business Analysis (PMI-PBA), ITIL 4 Foundation for service-management context, and CompTIA's Project+ or a Scrum credential for delivery fluency. On top of those, pick one vendor certification on the platform your target employers use — Salesforce Administrator, ServiceNow CSA, SAP Business Analyst, or a major cloud fundamentals certificate — because platform depth is what unlocks the higher-paying roles.
According to the U.S. Bureau of Labor Statistics, the median annual wage for computer systems analysts was roughly $103,000 in the most recent OES release, with entry-level analysts often starting near $65,000 to $80,000 and senior and lead analysts routinely earning $120,000 to $160,000 or more, especially in tech, finance, and healthcare. BLS projects employment of computer systems analysts to grow about 10 percent through 2033, faster than the average for all occupations, driven by continued digital transformation, cybersecurity work, and cloud migrations. Pay varies significantly by industry, region, and platform specialization, so treat these as broad ranges rather than guarantees.
Prove skill in place of work history. Build a small portfolio of artifacts — a requirements document, a current-state and future-state process map, a test plan, and a short case study on a realistic scenario — and earn a credential such as ECBA or a vendor certificate. Look for adjacent ways to get reps: help desk, QA, application support, junior project coordinator, or an internal move from operations or finance into an IT-adjacent seat. Then target genuinely entry-level titles like junior business systems analyst, IT analyst, or associate systems analyst, tailor each application to the platform and industry, and pursue referrals so a human sees your work rather than an algorithm screening you out.
Yes. Demand for people who can translate business needs into working systems remains strong across nearly every industry, the U.S. Bureau of Labor Statistics projects faster-than-average growth through the early 2030s, and the work pays well with clear paths into senior analyst, solutions architect, product management, and IT program management roles. Cloud migrations, ERP modernizations, and continued cybersecurity work keep the pipeline of projects deep. Automation is changing the toolset, but it raises the value of analysts who can frame the right requirements and judge whether a proposed system will actually work for the people who have to use it.
Related guides
Build the skills yourself — then let a strategist run the search.
Everything above is learnable on your own, and you should learn it. But once you have the resume, the credential, and the portfolio, the hardest stretch is getting a human to actually see them. That's what Marqee is for — a Career Concierge who finds the systems-analyst roles that fit, tailors your resume to each posting, reaches the hiring manager directly, and finds a referral inside the company so you skip the pile.
See pricing & get started →See how Marqee works