GIS Developer mock interview questions
19 questions a GIS Developer panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. Spatial data, PostGIS and web mapping rounds for GIS developer interviews.
Answer one real GIS Developer question now
A question a GIS Developer panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“Two datasets that should line up on the map are offset by a few hundred metres. Talk me through how you find out why.”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Thinking past the interview? Carmen can help with your whole GIS Developer career: a switch, a raise, or what comes next.
19 gis developer mock interview questions
The questions a GIS Developer panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
Two datasets that should line up on the map are offset by a few hundred metres. Talk me through how you find out why.
Why they ask it: The classic GIS debugging question. Misaligned layers are almost always a coordinate reference system or datum problem, and the interviewer wants to see you check metadata before touching geometry.
A strong answer: Check the declared CRS of each dataset first, then whether the declared CRS is actually true (a file tagged as WGS84 that contains projected coordinates is common), look for a missing or wrong datum transformation between two geographic systems, consider axis order swaps if points land in the wrong hemisphere or ocean, and fix by reprojecting with an explicit transformation rather than shifting features by hand.
- 2.
When do you store data in a geographic coordinate system and when in a projected one, and what goes wrong if you measure distance in the wrong one?
Why they ask it: Tests whether you understand that degrees are not a unit of distance, which is behind a large share of silent spatial bugs.
A strong answer: Geographic coordinates in degrees are good for storage and interchange across a wide area. Measurement and buffering need either a suitable local projected system or a geodesic calculation, because a degree of longitude shrinks toward the poles. In PostGIS that means using the geography type or transforming to an appropriate projection before calling distance or buffer, and knowing that Web Mercator distorts area and distance heavily away from the equator.
- 3.
This PostGIS query finds all parcels within 500 metres of each school and it takes minutes. How do you speed it up?
Why they ask it: Spatial SQL performance is daily work. The interviewer wants to hear about index usage, not a rewrite into application code.
A strong answer: Confirm GiST indexes exist on both geometry columns, read the plan with EXPLAIN ANALYZE, replace a buffer then intersects pattern with ST_DWithin so the index can be used for the bounding box filter, make sure the distance units match the CRS or use geography, avoid wrapping the indexed column in a transform function inside the predicate, and consider subdividing very complex polygons so the exact test is cheaper.
- 4.
You need to serve a national dataset of millions of features to a web map. How do you design that?
Why they ask it: Design question about scale. Shipping raw GeoJSON to the browser is the answer they are waiting for you not to give.
A strong answer: Vector tiles generated per zoom level, with geometry simplified and attributes trimmed at lower zooms, served from a cache or CDN, either pre-generated for stable data or generated on demand from PostGIS for data that changes. Discuss how updates invalidate tiles, keeping a separate query API for feature detail on click, and choosing raster tiles for imagery or dense layers where vectors would not help.
- 5.
Explain the difference between a shapefile, GeoJSON, GeoPackage and a spatial database table. When would you pick each?
Why they ask it: Formats come up constantly in GIS work because data arrives from many sources. This tests practical knowledge of their limits.
A strong answer: Shapefile is a multi-file legacy format with short field names and size limits, still common for interchange. GeoJSON is plain text, easy for the web, verbose, and by the current spec in WGS84. GeoPackage is a single SQLite-based file that handles multiple layers and larger data, good for handing a dataset to someone. A spatial database is for data that is queried, joined and edited concurrently.
- 6.
An analyst tells you the area totals from your pipeline do not match what their desktop GIS reports. How do you handle it?
Why they ask it: Behavioural and technical at once. GIS developers sit between engineering and analysts, and mismatched numbers are a trust problem as much as a bug.
A strong answer: Take the report seriously, get the exact features and method they used, compare the projection each side calculated area in, check for invalid or overlapping geometries and whether one side dissolved them, agree on the correct method together, fix or document the pipeline, and add a validation check so the same mismatch is caught automatically next time.
- 7.
How do you deal with invalid geometries coming from an external source?
Why they ask it: Real spatial data is messy. Self-intersecting polygons and ring orientation problems break operations quietly.
A strong answer: Detect with a validity check and record the reason, repair with a make-valid operation or a zero-width buffer only when you understand what it will do to the shape, quarantine features that cannot be repaired sensibly, and report back to the data owner rather than silently fixing their data forever.
How the GIS Developer interview runs
Usually a recruiter screen, then a technical conversation with a senior GIS or backend engineer about coordinate systems, spatial data formats and spatial databases. Many teams set a practical exercise: write PostGIS queries against a sample dataset, or build a small map that loads and styles vector data. A final round covers how you would design a spatial service or pipeline and how you work with analysts and field teams who consume the data.
What the panel scores
Spatial fundamentals
Whether you reason correctly about coordinate systems, projections and measurement.
- Checks CRS and datum before anything else when data misaligns
- Knows when degrees cannot be used as distance
- Names the distortion tradeoffs of common projections
Spatial database skill
Whether you can write and tune spatial queries at production scale.
- Uses index-friendly predicates such as ST_DWithin
- Reads query plans rather than guessing
- Handles invalid geometry deliberately
Web mapping and delivery
Whether you can get large spatial data to users quickly.
- Proposes tiling and simplification for large datasets
- Thinks about cache invalidation when data changes
- Separates rendering from feature detail queries
Working with data consumers
Whether analysts and field teams can trust what you produce.
- Investigates discrepancies without getting defensive
- Documents methods and assumptions
- Adds validation so errors do not recur
Common questions in every interview
These come up in almost every GIS Developer interview regardless of the company or the round.
- 8.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 9.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 10.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 11.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 12.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 13.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 14.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 15.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 16.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 17.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 18.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 19.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Every round ends in a scorecard like this
Your GIS Developer answers, quoted back, scored on what this role is judged on, with the line to say instead.
Real screen from the app. Sample from a product design round.
Related roles
All Engineering →No spam. Unsubscribe anytime.
Ready to practice as a GIS Developer?
Sign up free, no card. 30 voice minutes and unlimited typed interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 888+ roles to choose from
Questions & answers
- Is the GIS Developer mock interview free?
- Yes. 30 voice minutes and unlimited typed GIS Developer interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic GIS Developer job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a GIS Developer job description first, then practice the interview with the same JD for a tighter loop.