Should Accountants Learn SQL or Python? The Postings Say SQL First, and Mostly If You're Heading Into Finance

SQL is named in 1,413 of the 42,124 live accounting and finance postings I pulled from the Audit Friendly job database as of October 2026, which is about 3.4 percent, while Python shows up in 381, or 0.9 percent. That makes SQL roughly 3.7 times as common as Python in the postings, and if you've been told every accountant needs to learn to code this year, the data suggests a more specific answer than that: learn SQL first, and learn it because of the kind of role you want next.

How often do accounting job postings ask for SQL and Python?

Across every accounting and finance role we classify, which covers accountants, controllers, auditors, tax, payroll, AP and AR plus the financial analyst and FP&A families, Excel is named in 24,414 postings, about 58 percent. Power BI follows at 2,508 (6.0 percent), then SQL at 1,413 (3.4 percent), Tableau at 1,173 (2.8 percent), VBA or macros at 574 (1.4 percent), Alteryx at 408 (1.0 percent) and Python at 381 (0.9 percent). I picked the postings by role rather than by keyword, so the denominator is every live role in the family and not just the ones that happen to mention a tool.

Those numbers will not match the software share figures in our Power BI piece, because that analysis tracked share of the whole index and this one counts role-classified postings only. The ordering is the same in both, which is the part that matters.

Where does SQL actually matter?

In the analyst roles, and it isn't close. I split out the 6,401 live financial analyst, senior financial analyst, FP&A analyst, senior FP&A analyst and FP&A manager postings, and 888 of them name SQL, which is 13.9 percent, about four times the rate across accounting and finance as a whole. Power BI hits 22.1 percent of those postings, Tableau 12.4 percent, and Python 3.6 percent.

So the picture is that one analyst posting in seven wants SQL while a typical accounting posting almost never does. That makes sense once you think about what the two jobs do all day. A staff accountant lives inside the ERP's own reports and the close checklist, and an FP&A analyst spends a damn lot of the week begging IT or a data team for an extract, which is exactly the friction SQL removes.

The part that complicates it

A mention is a demand signal and nothing more, and "SQL preferred" counts the same as "you will write production queries." I can't tell you from the postings how many of these 1,413 are genuine requirements, and I'd bet a fair share are nice-to-haves a hiring manager pasted in from the last posting. Python is also harder to see than it looks, because plenty of finance teams that use it for reconciliations or forecasting don't write it into the job description at all.

There's also an honest case for ignoring all of this. The Bureau of Labor Statistics puts the 2025 median pay for accountants and auditors at $83,680 and projects 5 percent growth through 2035, and it also notes that technological change is expected to affect the role over that decade, with routine task automation pushing more of the work toward advisory and analytical tasks. Nothing in that says you need a programming language. It says the routine work shrinks, and the question is what you do with the time.

Which one should you learn first?

SQL, if you want to move toward FP&A, financial analysis, or any role that sits close to a data warehouse. It's a small language, a few weeks of evenings gets you to useful, and 888 analyst postings are already asking. Python makes sense second, or first if your job is heavy on reconciliations and you'd like to automate them, because an hour of Python on a recurring tie-out pays for itself quickly. Neither is a bad bet and neither is mandatory.

If you're a tax accountant or an auditor staying in your lane, I'd put an hour into better Excel (power query, lookups, pivots) ahead of either. About 58 percent of postings name Excel and 3,479 of them mention pivot tables, lookups or Power Query specifically, so you get more return per hour there than in a new language.

What I'd do

Pick a recurring report you currently build by hand from an ERP export and take the export straight into a free local database such as SQLite or DuckDB, then write the query that reproduces your pivot. That's one afternoon. You'll find out fast whether you like this kind of work, and you'll have a real example to talk about when an interviewer asks about your technical skills, which beats a certificate with no project attached.

If you'd like a sense of how this plays out on the planning side, our FP&A forecasting playbook shows where the data-gathering time goes, and our count of which software employers ask for covers the systems side. The software directory scores the platforms behind those postings, and the remote accounting job listings are a handy way to see what a given employer wants in the actual posting.

Frequently asked questions

Do accountants need to learn SQL?

Not for most accounting roles. SQL is named in about 3.4 percent of the 42,124 accounting and finance postings we analyzed. It becomes much more relevant in analyst roles, where 13.9 percent of postings name it.

Is SQL or Python more in demand for accountants?

SQL, by a wide margin. SQL appears in 1,413 postings against 381 for Python, about 3.7 times as often, and the gap holds in finance analyst roles where SQL is at 13.9 percent and Python at 3.6 percent.

Should an FP&A analyst learn Python or SQL first?

SQL, on the posting data. Among 6,401 financial analyst and FP&A postings, SQL appears in 888 and Python in 230. Learn SQL to pull your own data, then add Python if you want to automate recurring analysis.

What tools do accounting job postings ask for besides Excel?

Power BI leads at about 6.0 percent of postings, followed by SQL at 3.4 percent, Tableau at 2.8 percent, VBA or macros at 1.4 percent, Alteryx at 1.0 percent and Python at 0.9 percent. Excel is named in about 58 percent.

Will automation replace accountants who can't code?

The Bureau of Labor Statistics expects routine tasks to be automated and the work to shift toward advisory and analytical tasks, while projecting 5 percent growth for accountants and auditors from 2025 to 2035. Coding is one way to move toward that work, though not the only one.

Pick the one report, run it through a query this week, and see what you think.