{"id":19106,"date":"2026-08-07T17:17:14","date_gmt":"2026-08-07T17:17:14","guid":{"rendered":"https:\/\/geosearch.com\/?p=19106"},"modified":"2026-08-07T17:21:10","modified_gmt":"2026-08-07T17:21:10","slug":"how-to-read-a-geospatial-job-posting","status":"publish","type":"post","link":"https:\/\/geosearch.com\/job-search\/how-to-read-a-geospatial-job-posting\/","title":{"rendered":"How to read a geospatial job posting"},"content":{"rendered":"

 <\/p>\n

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

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.<\/p>\n

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.<\/p>\n

Read the responsibilities before the requirements<\/strong><\/p>\n

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.<\/p>\n

Read it first, and read it for repetition. If three of six bullets involve data cleanup and QA, that’s the job \u2014 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.<\/p>\n

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 \u201cnice to have.\u201d<\/p>\n

Years of experience are the softest number on the page<\/strong><\/p>\n

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.<\/p>\n

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.<\/p>\n

Where the number does matter is when it’s paired with something structural \u2014 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.<\/p>\n

Decode the software list<\/strong><\/p>\n

Software lists are where postings leak the most information, if you know what to look for.<\/p>\n

Look at order and repetition<\/strong>. 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.<\/p>\n

Watch for incoherent stacks<\/strong>. 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.<\/p>\n

Note what’s missing<\/strong>. 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.<\/p>\n

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.<\/p>\n

Titles mean almost nothing across companies<\/strong><\/p>\n

GIS Technician, GIS Analyst, GIS Specialist, Geospatial Analyst, Spatial Data Analyst \u2014 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.<\/p>\n

The same is true in surveying and remote sensing. Survey Technician can mean rod work or it can mean office calculations and deliverable prep.<\/p>\n

Ignore the title. Price the role from the responsibilities and the pay range, then decide whether it’s a step forward.<\/p>\n

The details buried near the bottom<\/strong><\/p>\n

Some of the most consequential information sits below where most people stop reading.<\/p>\n

Travel percentage.<\/strong> 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.<\/p>\n

Field versus office split.<\/strong> 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.<\/p>\n

Clearance language.<\/strong> “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.<\/p>\n

Licensure.<\/strong> A Professional Land Surveyor requirement is a hard gate \u2014 it can’t be substituted for. Certifications like GISP or ASPRS credentials almost never are, whatever the posting implies.<\/p>\n

Employment type.<\/strong> 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.<\/p>\n

What good postings look like<\/strong><\/p>\n

Not every signal is a warning. Some postings tell you the employer has their act together:<\/p>\n