Systems Analyst skills: what to learn first, and what can wait

Nobody hires a systems analyst for knowing the vocabulary. They hire you because you can open a table, read a spec and spot the place where the business rule and the code quietly disagree. Learn the skills below roughly in order, and you'll spend your study time on the things interviewers actually poke at.

1,625 open jobs
Step one

Gets you the interview

SQL you can write without a templateJoins across several tables, GROUP BY with HAVING, and a LEFT JOIN that finds the orders with no matching invoice. If you can answer your own data questions in SQL Server Management Studio or DBeaver, you stop waiting on a developer and screeners notice.
Process mapping in swimlanesA current-state and future-state flow in Visio, Lucidchart or BPMN notation, with handoffs between teams drawn as lanes. It's the artifact hiring managers ask to see first, because it shows whether you understood the work or just the screen.
User stories with testable acceptance criteriaStories in Jira that a tester can pass or fail without asking you what you meant. Given, when, then works fine. Vague criteria like "system should be fast" are the tell of someone who hasn't done it.
Reading an ERD and a data dictionaryYou'll be handed an entity relationship diagram for an ERP or CRM on day one. Knowing primary and foreign keys, cardinality and where a lookup table hides lets you follow a record from order entry to general ledger.
Step two

Gets you the offer

Source-to-target data mappingThe spreadsheet that says which field in the old system lands where in the new one, with the transformation rule next to it. Case exercises love it, because it's where migrations usually go wrong.
Integration basics: APIs and file feedsEnough to read a JSON payload in Postman, understand a REST endpoint's required fields, and trace why a nightly flat file dropped records. Most systems work is about two systems talking, and panels test whether you can follow the conversation.
Running UAT and triaging defectsWriting test scripts, lining up business testers, and sorting their findings into real defects, training gaps and new requests. Doing that calmly in a triage call is what earns trust with a go-live.
Configuring the platform the posting namesHands-on time in Salesforce setup, ServiceNow forms and workflows, or SAP and Oracle transaction screens. Having changed a picklist or a business rule yourself beats only writing tickets about it.
Step three

Gets you promoted

Impact analysis before a change shipsTracing what else touches a field, report or interface before anyone changes it. Senior analysts are the ones who say "that will break the month-end accrual report" in the design review instead of after the release.
Solution options with honest trade-offsLaying out configure, customize or buy, with the cost of each in support and upgrade pain. Leads get judged on the recommendation, not the list, so practice writing a one-page decision memo.
Owning a system's roadmap and backlogGrooming the backlog with the product owner, sequencing work around vendor upgrade windows, and saying no to requests with a reason.
Reporting and data quality checksBuilding reconciliation queries and a Power BI or Tableau view that shows when the source and target systems stop agreeing. The analyst who catches bad data before finance does gets pulled into bigger projects.

Certificates worth your time

CertificateBest forEffortWorth it?
IIBA Entry Certificate in Business Analysis (ECBA)Career changers and support staff with little formal analysis work to point toa few weekends of study plus the examUseful as proof you know the terms. It won't outweigh a real process map in your portfolio, so do both.
IIBA Certification of Capability in Business Analysis (CCBA)Analysts with some real projects behind them who want a mid-level credentiala couple of months of eveningsWorth it if your company pays and your postings mention IIBA. Otherwise skip straight to experience.
IIBA Certified Business Analysis Professional (CBAP)Senior analysts aiming at lead or consulting rolesseveral months of steady studyCarries weight with consultancies and government contractors. Less so at small product companies.
ITIL 4 FoundationAnalysts working in IT service management or on ServiceNowa few weekendsCheap in time and often listed in IT operations postings. It teaches the change and incident language those teams speak.

Eligibility rules, exam formats and fees change, so check the details with IIBA or the certifying body before you pay for a course.

Put it on your resume like this

Weak

Gathered requirements and worked with developers on system enhancements.

Strong

Mapped 1,200 customer fields from a legacy CRM to Salesforce, wrote 85 acceptance-tested user stories, and led UAT with 14 business testers ahead of an on-time cutover.

Questions people ask

Which should I learn first, SQL or a modelling tool like Visio?

SQL. You can pick up Visio or Lucidchart in an afternoon, but querying data well takes practice, and it's the skill technical screens check directly.

Do I need Python as a systems analyst?

Not to get hired. It helps when you're cleaning export files, comparing two data sets or automating a repetitive check. Treat it as a promotion-tier skill and learn it once SQL feels easy.

Should I specialise in one platform like SAP or Salesforce?

Pick one once you've seen a few postings in your area. Deep knowledge of one ERP or CRM makes you easier to hire for that stack, and the analysis skills carry over if you switch later. Staying platform-neutral too long makes your résumé read as generic.

How do I practise these skills without the job?

Pick a process you know, like how a library checks out books, and write it up end to end: a swimlane flow, a handful of user stories, a small data model and a few SQL queries against sample data you build yourself. That folder becomes your interview material.

Got step one? Start applying. HeroApply matches you to roles that fit.

Start your trial