For years, GIS was the work of one person with a desktop licence and a good eye for maps. In many mid-sized companies it still is. That is the first risk worth looking at.
Location data now touches asset records, field crews, routing, site planning and risk work. When it lives in one person's head or on one laptop, the business has a quiet dependency it may not see until that person gives notice.
The single-expert problem
A simple test: if your maps and spatial data stop being reliable when one person is on vacation, you do not have a capability. You have a person.
We see the same pattern in other functions. A controller who holds the only copy of the close process. A maintenance planner who knows which assets matter. GIS is no different, and the fix is the same: define the roles, write down the workflows, and hire so that the knowledge is spread across more than one seat.
Roles a working GIS function usually needs
You do not need a large team. You do need the following jobs covered, even if one person covers two of them at a smaller company.
- GIS analyst: runs spatial analysis, builds maps and answers operational questions from location data.
- Geospatial data engineer: moves, cleans and structures spatial data so other systems can use it. This is where most mid-sized firms are thin.
- GIS developer or integration specialist: publishes data as services so asset, engineering and analytics tools read from the same source.
- Data steward or owner: decides what counts as the authoritative version of a dataset, and keeps records of where it came from.
- Business-side lead: an operations, engineering or planning manager who knows which decisions the data should support.
The last two are often missing. Without them, even a strong technical hire ends up fielding one-off map requests all day.
Who is hiring for this, and why
Demand is not limited to mapping firms. The employers we talk with that have real spatial needs include:
- Utilities, energy and pipeline operators tracking assets across their lifecycle
- Municipal and provincial or state agencies, and the contractors who work for them
- Engineering and environmental consultancies
- Transportation, logistics and distribution businesses
- Manufacturers and food producers with multiple sites or complex supply routes
- Software and platform companies embedding location features in their products
In Canada and the US alike, many of these employers are competing for a small pool of people who combine spatial skills with solid data engineering. That combination is the hard one to find.
Where AI changes the hiring brief
Automated feature extraction and pattern detection can cut hours of manual digitizing. That is useful, and it shifts what you need from people. You want someone who can check model output against the real world, document how results were produced, and say when a result should not be trusted.
When a spatial model influences where a crew is sent or which asset is flagged for replacement, a wrong answer has a cost. Hire for judgment and validation habits, not only for tool familiarity.
What to screen for
Software knowledge matters less than most job postings suggest. Platforms change. These traits carry over:
- Data discipline. Can the candidate explain how they track metadata, ownership and versions?
- Integration experience. Have they published data that other teams or systems actually consumed?
- Communication. Can they explain a spatial result to a plant manager or a controller without a map and a glossary?
- Scripting ability. Python or SQL is now a baseline for anyone expected to repeat work reliably.
- Documentation habits. Ask what happens to their work when they are away.
Permanent, contract or both
Many GIS needs are project-shaped: a data migration, a platform upgrade, a one-time asset inventory, a clean-up before an audit. A contract specialist is often the right answer for that work, with a permanent hire to own the result afterward.
The mistake is the reverse: hiring a permanent analyst to do a six-month migration, then having no plan for the work after it. Decide up front which part of the need is ongoing and which part is a project.
A short checklist before you post the role
- Name the decisions the spatial data should support.
- List who uses it today and how they get it.
- Identify the one person everyone relies on, and what they know that is not written down.
- Decide whether the need is a project, a permanent function or both.
- Set a pay range based on the data engineering and integration skills you need, not only the mapping ones.
What to do next
Start with the dependency. Find out who holds your spatial knowledge, write down what they do, and decide which second skill set you need beside them. Then hire to that gap rather than to a software name.
If you are scoping a GIS, data or analytics role in Canada or the US, a Traverse recruiter can help you define it and find people who fit it.