Career advice in GIS tends to travel by word of mouth — a conference talk here, a LinkedIn post there, a professor's assumptions from five years ago. Job postings are a more honest source. They're written by the people actually paying salaries, for the roles they actually need filled right now. So we looked at what's in them.

The Market by the Numbers

A few figures set the scene. Indeed alone lists roughly 14,000 active GIS postings at any given time in 2026, and the average GIS salary sits around $79,639 a year, with meaningfully higher pay for candidates who bring developer, administrator, or AI skills to the table. Postings that mention a professional certification appear in 37% of senior-level listings, compared to just 16% at entry level — a gap we'll come back to, because what it doesn't mean is almost more interesting than what it does.

The Software Employers Actually Name

Job postings are specific about tools, and the pattern is consistent across hundreds of listings:

ArcGIS Pro / Online / Enterprise remain the default reference point in the majority of postings — still the industry's common denominator.

QGIS shows growing, steady adoption, particularly in organizations where licensing cost and open-source flexibility matter.

AutoCAD appears in near-even numbers alongside ArcGIS, a reminder that CAD-to-GIS data conversion remains a genuinely marketable, underrated skill.

PostGIS / PostgreSQL has become the default answer to "how do you store spatial data at scale" — proficiency here reads as a baseline expectation, not a differentiator.

Scripting Is No Longer Optional

Python is the single most-requested skill after the core GIS software itself, and postings are increasingly specific about it — GeoPandas, rasterio, and scikit-learn appear by name, not just "Python" as a generic line item. Alongside it: SQL for spatial queries, JavaScript (Leaflet, OpenLayers) for web GIS work, and Git for anyone maintaining scripts or pipelines as part of a team.

The signal here is clear: the scripting layer has moved from "nice to have" to a baseline expectation for a meaningful share of roles, especially anything above entry level.

The Certification Finding That Surprised Us

Here's the counterintuitive part. Postings that mention a certification pay, on average, about $7,000 less than postings that don't mention one at all. That's not a typo, and it's worth sitting with, because it cuts against a lot of conventional advice about credentialing.

The likely explanation isn't that certifications hurt your earning potential. It's that certifications function as a competency signal, most useful when an employer has no other way to evaluate a candidate's baseline skill — which is more often the case for senior, specialized, or higher-compliance roles, and less often the deciding factor in itself. Certifications show up in 37% of senior postings versus 16% of entry-level ones, which tracks: more senior roles, more need for a fast, legible signal of competency before a deeper technical interview. But the certification isn't what commands the pay premium on its own. A real portfolio and demonstrated skill do most of that work.

That's a useful, if slightly humbling, thing for any certification program — including our own — to be honest about. A credential should prove competency and build trust quickly. It was never meant to substitute for it.

Degree Requirements Are Softening

A related shift: a traditional four-year geography or GIS degree is no longer the hard gate it used to be. Many postings now explicitly accept a GIS certificate combined with a few years of hands-on experience as an equivalent path in. Portfolios and demonstrated project work are doing more of the gatekeeping that degrees used to do — good news for anyone building real skills outside a traditional academic track.

The Soft Skills Buried in the Fine Print

Beneath the technical requirements, the same handful of soft skills recur across almost every posting we looked at:

Explaining spatial findings clearly to non-technical stakeholders

Producing documentation clear enough for someone else to pick up the work

Reconciling data that arrives in inconsistent formats from inconsistent sources

Troubleshooting independently, under real deadline pressure

None of these show up in a keyword search the way "Python" or "PostGIS" do. All of them show up constantly in the actual body text of job descriptions — which suggests they're valued precisely because they're hard to screen for on a resume alone.

Who's Actually Hiring

The demand isn't concentrated in one sector. It spans government agencies and utilities managing asset inventories and permitting; urban planning and transportation departments modeling zoning and transit; conservation and environmental organizations tracking habitat and land use; and consulting and engineering firms running project work across multiple clients at once. If your image of "who hires a GIS analyst" is narrower than that list, it's worth updating.

Read the Postings, Not Just the Predictions

The fastest way to close any gap between where you are and where GIS hiring is heading is to build toward what's actually written in these listings — not toward what a course outline assumed five years ago, and not toward whatever the loudest conference talk claimed last quarter. The postings are, in their own unglamorous way, the most current source available.