How to Hire GIS Developers: Skills, Interviews and Red Flags

Hiring a GIS developer is harder than hiring a general web developer. The role sits between two disciplines: geospatial science, with its coordinate systems, data formats and spatial analysis, and software engineering, with its databases, APIs, testing and deployment. Strong candidates are comfortable in both. Many are strong in only one.

This guide covers what to look for, how to test it and the warning signs that save you from an expensive mistake.

Decide what kind of GIS developer you need

"GIS developer" covers several different jobs. Be specific before you write the advert.

• Web GIS developer: builds map applications in the browser with OpenLayers, Leaflet, MapLibre or the ArcGIS Maps SDK for JavaScript.
• Spatial back-end developer: designs spatial databases, APIs and tile services with PostGIS, GeoServer and Python or Node.
• ArcGIS specialist: configures and extends ArcGIS Online and Enterprise, writes ArcPy scripts and builds Experience Builder widgets or Pro add-ins.
• Data and automation engineer: builds pipelines that clean, convert and publish spatial data, often with FME, GDAL or Python.
• Mobile field app developer: builds offline-capable data collection apps.

A small product may need one person who covers two of these. A larger system needs a team.

The skills that matter

Spatial fundamentals

• Coordinate reference systems: knows why distances in degrees are misleading, when to reproject, and how to find the right EPSG code.
• Data formats: Shapefile, GeoJSON, GeoPackage, GeoTIFF, vector tiles, and when to use each.
• Spatial operations: buffers, intersections, spatial joins and simplification, and their performance cost.
• Data quality: invalid geometries, topology errors and mismatched projections.

Software engineering

• version control and code review
• a well-structured database design, with spatial indexes
• APIs, authentication and permissions
• testing, deployment and monitoring
• performance with real data volumes, not sample files

Communication

GIS projects involve non-technical users. A good developer can explain a trade-off, such as accuracy against speed, in plain language.

Test with a realistic task

Portfolios and certificates show interest, not ability. A short paid or time-boxed task tells you far more. Good tasks are small, realistic and close to your actual work:

• load a sample dataset into PostGIS and write a query that answers a real question, such as which customers fall within 2 km of a site
• build a simple map that loads 50,000 points without freezing the browser
• fix a dataset with mixed coordinate systems and invalid polygons

Review how they approach it as well as the result. Did they ask clarifying questions? Did they explain their choices? Is the code readable?

Interview questions that reveal real experience

• "Tell me about a time map performance was a problem. What did you change?"
• "How do you decide between storing data in geometry or geography in PostGIS?"
• "A client's layers are offset by a few hundred metres. What do you check first?"
• "How would you serve a dataset of five million parcels to a web map?"
• "What have you deployed to production, and who maintained it afterwards?"

Candidates with real experience answer with specifics: the data, the tool, the mistake and the fix. Candidates who have only followed tutorials answer in generalities.

Red flags

• cannot explain coordinate systems simply
• has only worked with small sample datasets
• treats every problem as needing the same tool
• no experience with version control or deployment
• portfolio of map screenshots with no explanation of their own role

Hire, contract or partner?

Hiring in-house makes sense when GIS is core to your product and you have steady work for years. For a defined project, a specialist contractor or a dedicated team from a GIS company can be faster to start, brings experience across many projects and reduces the risk of depending on one person. Many organisations combine both: a small internal team that owns the product, supported by an external team for peaks and specialist work.

Summary

Define the role precisely, test with a realistic task, and use interview questions that require specifics. The best GIS developers combine spatial understanding with disciplined software engineering, and can explain both to the people who will use what they build.