How to read a geospatial job posting

We hear the same sentence from candidates constantly. “I would’ve applied, but it asked for five years and I have three.”

Here’s what usually happened on the other side of that posting. A hiring manager listed what they wanted. Their director added two things. HR pulled language from the last person who held the role. Someone copied a software list from a posting they found online. Nobody in that chain expected one human to have all of it.

A geospatial job posting is a wish list assembled by committee. Learning to tell the real requirements from the aspirational ones is one of the highest-return skills in a job search, and it costs nothing to develop.

Read the responsibilities before the requirements

The requirements section is where wishes go. The responsibilities section is where the actual job lives, because someone had to describe work that genuinely needs doing.

Read it first, and read it for repetition. If three of six bullets involve data cleanup and QA, that’s the job — regardless of what the title says or how much Python appears further down. If the responsibilities mention client deliverables repeatedly, this is a client-facing role even if the posting never uses the phrase.

Then go back to the requirements and ask which ones the responsibilities actually demand. Anything that doesn’t map to a duty is usually a “nice to have.”

Years of experience are the softest number on the page

Experience ranges are frequently reverse-engineered from a salary band rather than from the work. Someone decided the role pays a certain amount, and a number of years got attached to justify it.

Our rule of thumb: if you’re within about two years of the range and you can point to relevant work, apply. If you’re substantially under but you’ve done the specific thing the role centers on, apply and say so directly in your first line. Recruiters and hiring managers read those.

Where the number does matter is when it’s paired with something structural — supervisory experience, sole responsibility for a program, or a licensure track. Ten years for a survey manager isn’t arbitrary. Five years for a GIS analyst usually is.

Decode the software list

Software lists are where postings leak the most information, if you know what to look for.

Look at order and repetition. The tools named first, and named again in the responsibilities, are the stack they actually run. Tools mentioned once at the bottom of a long list are often things one person on the team uses, or things they hope to adopt someday.

Watch for incoherent stacks. A posting that asks for ArcGIS Pro, QGIS, FME, ERDAS, Trimble Business Center, Python, SQL, JavaScript, and Power BI is not describing one person’s daily work. It’s describing the combined toolset of a department. Figure out which two or three belong to this seat.

Note what’s missing. A GIS role with no database mentioned anywhere is likely working in file geodatabases and shapefiles, which tells you something about the maturity of the operation. A remote sensing role with no mention of processing software may be more analysis than production.

And take software gaps less seriously than you take skill gaps. Learning ArcGIS Pro when you know QGIS is a matter of weeks. Learning to think spatially is a matter of years, and you either have it or you don’t.

Titles mean almost nothing across companies

GIS Technician, GIS Analyst, GIS Specialist, Geospatial Analyst, Spatial Data Analyst — these are not a ladder, and they don’t mean the same thing at two different employers. One company’s analyst is digitizing parcels. Another analyst is writing production Python and managing an enterprise geodatabase.

The same is true in surveying and remote sensing. Survey Technician can mean rod work or it can mean office calculations and deliverable prep.

Ignore the title. Price the role from the responsibilities and the pay range, then decide whether it’s a step forward.

The details buried near the bottom

Some of the most consequential information sits below where most people stop reading.

Travel percentage. In survey, LiDAR acquisition, and field data collection, “occasional travel” and “up to 50%” describe very different lives. If it isn’t stated, that’s worth asking about in the first conversation rather than the fourth.

Field versus office split. Postings routinely undersell field time. If the responsibilities mention site visits, equipment, or data collection at all, assume more field work than the posting implies and confirm early.

Clearance language. “Active clearance required” and “must be able to obtain a clearance” are separated by months of process. If you don’t currently hold one, the second phrasing is your opening; the first usually isn’t.

Licensure. A Professional Land Surveyor requirement is a hard gate — it can’t be substituted for. Certifications like GISP or ASPRS credentials almost never are, whatever the posting implies.

Employment type. Contract, contract-to-hire, and direct hire get described in similar language. It affects benefits, stability, and how you should read the compensation. Find it before you invest time.

What good postings look like

Not every signal is a warning. Some postings tell you the employer has their act together:

• A published pay range, especially where it isn’t legally required
• Named software with named workflows, rather than a keyword dump
• A description of the team — who you’d report to, who else does this work
• An actual project or program described, not just a duty list
• Any mention of certification support, training budget, or conference attendance
• Clear separation of what’s required from what’s preferred

That last one is rarer than it should be, and it’s a genuine mark of a manager who thought about the hire.

And what to be cautious about

• “Build our GIS program from the ground up” at a junior salary. Sometimes this is a real opportunity. Often it means no mentor, no budget, and no one internally who understands what you do.
• A posting that’s been up for eight months. Either the requirements are unrealistic or something about the role isn’t working.
• Required licensure paired with entry-level pay. The market for licensed surveyors doesn’t support it, and it signals an employer who hasn’t checked.
• No pay range in a state that requires one. Pay transparency rules vary and are still expanding, but an employer out of step with their own state’s requirements is telling you something.
• Heavy emphasis on “wearing many hats” and “fast-paced” with no description of the actual work. This can be honest shorthand at a small firm. It can also be a role nobody has defined.

The read is not a verdict

Reading a posting well doesn’t mean disqualifying yourself more efficiently. It means the opposite. Most people talk themselves out of roles they are viable for, on the basis of requirements that were never real.

If the responsibilities describe work you can do and want to do, apply — and use your first paragraph to address the one gap you’re worried about, rather than hoping nobody notices it. Naming it yourself is almost always stronger than leaving it to be found.

And when a posting is genuinely unreadable, ask someone who talks to these employers every week. That’s a lot of what we do.