Questions to Ask in a GIS Interview
For candidates interviewing for a GIS analyst, technician or specialist job and deciding what to ask when the interviewer hands the conversation over. The questions run in six groups: what the work is, the data underneath it, the tools and scripting, the people who request maps and analysis, the team and where the role leads, then the steps before an offer. Those three titles are used loosely from one employer to the next, so most of the questions are built to find out which job is really behind the posting.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The Work
How does the job split between making maps, running analysis and maintaining data?
Why ask it
Rough shares of an ordinary week are enough: half editing, a third maps, the rest analysis. A job titled analyst can turn out to be mostly parcel edits, and a technician post can carry real modeling. If the split is not the one you hoped for, find out whether it shifts with experience or stays that way.
What does a typical week look like for the person in this role?
Why ask it
Good answers come with named tasks in them: the address points updated every Tuesday, the map book for the monthly board meeting, the layer a field crew needs before it goes out. If you are told every week is different, ask what the last person in the seat was working on in their final month.
Why is the position open, and who has been covering the GIS work in the meantime?
Why ask it
A backfill leaves you a database, a folder of map documents and someone's habits to inherit, so ask whether they left notes. If an engineer or a planner has been making maps on the side, expect them to keep opinions about how it is done. A brand new position usually means building the structure before producing much from it.
Which layers, maps or projects would be mine by the end of the first three months?
Why ask it
Ownership in GIS is concrete: the street centerlines, the zoning map, the web app the public opens. A named list tells you what you would be answerable for when a phone call comes about an error. 'Getting familiar with the data' with nothing after it suggests the handover has not been planned.
What kind of spatial analysis does the office get asked for, and how often?
Why ask it
Buffers and overlays for a site search, network routing, suitability models and hot spot work sit at different levels of the craft. Ask for the most recent example and how long it took. If nobody can recall one, the job is probably map production and data upkeep, whatever the posting calls it.
Is the GIS work done for the organization's own departments, or for outside clients on billed projects?
Why ask it
In-house GIS serves the same few departments for years, so you get to know one area and its data deeply. At a consultancy or an engineering firm the place, the client and the deliverable change with each contract, and hours are usually charged to a project number. If it is client work, the thing to find out is what happens to your time between projects.
What is the first project waiting for whoever takes this job?
Why ask it
Something specific, such as a utility inventory, a redistricting map set or a move to a new database, tells you what to read up on before day one. It is also the piece of work your first review is likely to turn on, so ask when it is due and who is waiting for it.
What leaves this desk as a finished product: printed maps, web maps, dashboards, reports or data deliveries?
Why ask it
Each output needs a different skill. Print work rewards layout and typography, web maps reward knowing how services and pop-ups behave, and data deliveries reward tidy schemas. Bring portfolio pieces that match whichever they name first.
Is the work steady production with volumes and deadlines, or projects that change from month to month?
Why ask it
Production roles, such as digitizing for a utility or processing parcels after each recording, often come with a count per day and a quality check. Project roles have less routine and more ambiguity. If there is a quota, ask what it is and how a new person is eased up to it.
How much field work comes with the job, and what does a day in the field involve?
Why ask it
Field work can mean an occasional afternoon checking hydrant locations or weeks of walking survey lines with a receiver on a pole. The details that matter are the season, the driving and whether you would go out alone. For someone set on a desk job, or on an outdoor one, this answer can settle the decision by itself.
The Data
Where does the data come from: collected in house, bought from a vendor, sent over by other departments, or pulled from public sources?
Why ask it
Data the team collects can be fixed at the source. Data that arrives from a vendor or another department comes on their schedule and in their format, and much of the job becomes loading and reconciling it. Listen for the source they sigh about, because its files are the ones you would be repairing.
Who is responsible for keeping each layer current and correct?
Why ask it
You are listening for names or job titles attached to layers. Where every layer has a steward, an error has somewhere to go. Where the answer is 'GIS does', you would be correcting records for departments that know the ground better than you do, so ask how they tell you something has changed.
How is the data stored: an enterprise geodatabase, file geodatabases on a shared drive, shapefiles, or a mix?
Why ask it
The storage says how mature the program is. A managed enterprise database with a person looking after it makes for a different working day from a shared drive holding six copies of the roads layer with dates in the file names. If it is the shared drive, ask whether cleaning that up is part of the job or only a wish.
How do several people edit the same layer without overwriting each other's work?
Why ask it
Versioning, check-out replicas or a plain rule that one person edits at a time: any of them can work if everyone follows it. The useful follow-up is who reconciles conflicts and how often. A blank look may only mean one person does all the editing, but in a shop with several editors it suggests lost edits go unnoticed.
How much metadata is there, and could I tell where a layer came from and when it was last updated?
Why ask it
Without it you spend your first months asking colleagues which roads file is the real one. If documentation is thin, ask whether writing it would count as real work in a review or be something to fit in around requests.
Which coordinate system does the office standardize on, and how often does incoming data arrive in something else?
Why ask it
A quick, exact answer is a sign that somebody is minding the fundamentals. Hesitation is worth noting, because projection and datum mismatches are a common reason features land a few feet from where they belong. Look up the system they name before a technical round.
Which dataset does everybody here know has problems?
Why ask it
Asked with a smile, this usually gets an honest laugh and a specific layer. Find out whether fixing it is funded, planned or simply lived with. An interviewer who claims everything is clean either has an unusually good program or does not open the attribute tables.
How does data collected in the field get checked before it goes into the main database?
Why ask it
Some teams load field edits into a review version and have someone approve them. Others let the tablet write straight to the live layer. If there is no check, ask who notices a point collected in the wrong place, and how long that usually takes.
When someone reports an error in a published map or layer, how does the correction get made?
Why ask it
Follow the path: who receives the report, who edits, and how long before the public map or the printed copy reflects it. A short path means the data is treated as a living record. If corrections wait for an annual update, people outside the team will have stopped reporting them.
Is any of the data shared with the public or partner agencies, and who decides what can be released?
Why ask it
Open data portals, data requests and sharing agreements all add work that rarely appears in a posting. The rules on releasing records about people, utilities or protected sites depend on the employer and where it operates, so ask how it is handled there and whether requests would come to you.
How much of the work involves imagery, lidar or other raster data alongside the vector layers?
Why ask it
Raster work calls for different tools, more storage and more patience with processing time. If remote sensing is why you studied GIS, the last project that relied on it is the thing to hear about. If you have done little of it, say so now, which is easier than being handed a lidar tile in your second week.
Is there a backlog of paper maps, CAD drawings or old records still waiting to be converted?
Why ask it
Conversion work is slow and careful, and it tends to be handed to the newest person. That is not a reason to walk away, since it teaches you the history of the place faster than anything else. Do ask what share of the week it would take and whether it has an end date.
Tools
Which GIS software and version would I be working in every day?
Why ask it
Get the product name and the version, whether that is ArcGIS Pro, QGIS or something built in house, then check your own experience against it honestly. An office still on a desktop product its vendor has stopped developing is likely facing a move, and you could arrive in the middle of it. Naming the version in a later round shows you were paying attention.
Which license level and extensions would I have, and would I share them with other staff?
Why ask it
The tools open to you depend on the license tier and on add-ons such as spatial or network analysis, and those are a budget decision. A shared pool of licenses can mean waiting for a colleague to close the program before you can run a tool. Ask what happens when you need an extension the office does not own.
Is there a web GIS side, such as a portal or an online organization, and who administers it?
Why ask it
If nobody is named, the administration may be part of the job you are interviewing for: users, groups, services that stop working overnight. Some people want that responsibility and some want to stay in the map. The number of live web maps and apps, and who built them, tells you how big that side already is.
How much scripting or automation is expected in this role, and in which language?
Why ask it
Python is a common answer, with SQL or JavaScript behind it in some shops, but do not assume. 'It would be nice' and 'we need it from the first week' are different jobs. If you are still learning, the best news is a colleague whose scripts you could read.
Which recurring tasks are still done by hand that you would like to see automated?
Why ask it
The answer is a ready list of early wins: the nightly export, the monthly map series, the quality checks someone runs by eye. It also tells you whether you would be given time to build those tools or expected to write them between requests.
Is a migration or major upgrade planned, and would I be part of it?
Why ask it
Moving to a new desktop product, a new database or a utility network model can take over a team for a year or more. For some candidates that is the best experience on offer. Ask who is leading it and whether a consultant is involved, so you know if you would be doing the work or watching it.
Does the team use open source tools such as QGIS or PostGIS alongside commercial software?
Why ask it
This shows how the office feels about tools from outside its main vendor. Some IT departments block anything not on an approved list, so a follow-up is whether you could install a package or a plugin yourself. If your background is mostly open source, say so here and hear how they think it carries over.
What other systems does the GIS connect to: CAD, asset management, permitting, dispatch?
Why ask it
Each connection is a place where the map and another department's records can disagree. Ask which integration breaks most often and who gets the call when it does. A GIS with no connections at all is simpler to run and easier for the organization to overlook.
Where do scripts, models and map templates live, and is any of it under version control?
Why ask it
With a shared repository you can see how things were built and change them without fear. Tools kept on one person's desktop leave with that person. If nothing is organized yet, offering to set it up is a reasonable thing to mention, briefly.
How much database work falls to this role: writing SQL, managing users, running backups?
Why ask it
In a large organization a database administrator handles this and you never see it. In a small one the GIS person is the database administrator by default. Say plainly what you have done before, because being left alone with a production database you do not understand is a hard way to learn.
What field equipment does the team use: GPS receivers, tablets, drones?
Why ask it
Receiver accuracy tells you what the data is good for: mapping grade suits an inventory, survey grade is for work where small distances matter. Whoever maintains the gear and builds the collection forms may turn out to be you. Flying a drone for work may need a license or permit depending on where you are, so ask how they handle that.
Requests
Who asks for GIS work here, and how does a request reach me?
Why ask it
A ticket queue, a shared inbox or a manager who hands out the work all give you a record and a way to say when. Requests made in a hallway or by a director's text message do not. Find out which department asks most, and whether members of the public can call or walk in with requests as well.
How well do the people asking understand what GIS can and cannot do?
Why ask it
Requesters who know the data ask sharper questions and accept that an analysis takes time. Those who think of GIS as 'the map people' need more explaining and tend to request a map when they need an answer. Some teams close that gap with short trainings for other staff, and running them can become part of this job.
Are there cartographic standards and templates, or would I set the look of the maps myself?
Why ask it
A style guide saves time and keeps a hundred maps looking like one organization made them. Its absence is freedom if you care about design and a burden if you do not. Ask to see a recent map either way, since it shows the standard better than any description.
Does anyone review a map or an analysis before it goes out?
Why ask it
Review catches the misspelled street and the legend that does not match the layer. Without it, your mistakes go straight into a council packet or a client's inbox. The story of the last map that went out with an error on it tells you how the place treats one.
Is there a viewer app where other staff can look up a parcel or an address without calling GIS?
Why ask it
With a good viewer the simple lookups never reach you, and what is left is the work that needs a person. Without one, expect a stream of 'can you tell me who owns this lot'. Find out which lookup comes in most and whether anyone has tried to build an app for it.
Which map or analysis from this team do people still talk about, and what did it lead to?
Why ask it
If a story comes readily, a site chosen or a route changed or a grant won, the work reaches decisions. A long silence suggests maps here illustrate choices already made. Either way you learn what the organization counts as GIS at its best.
How often does something urgent come in, such as an emergency, a public meeting or a legal deadline?
Why ask it
Some GIS desks support emergency operations and are called in during storms or fires. Others see nothing more pressing than a board meeting on Thursday. Ask whether out-of-hours work is expected and how it is made up, because that is set by the employer and varies widely.
Team and Growth
How many people do GIS work here, and would I be the only one?
Why ask it
Being the only GIS person means freedom and nobody to ask. On a team there is review, cover when you are on vacation, and people to learn from. If you would be alone, ask who you could call with a technical question: a vendor contact, a regional user group, a counterpart in a neighboring organization.
Who would I report to, and do they have a GIS background themselves?
Why ask it
A manager who has edited a geodatabase knows why a 'quick map' took two days. One from planning, engineering or IT may be an excellent boss and still need the work explained before they can defend it. With that kind of manager, expect to write short plain-language accounts of what you did and why it took the time it did.
Where does the GIS group sit in the organization: IT, planning, engineering, or a unit of its own?
Why ask it
The home department shapes the work. Under IT it leans toward systems and services, under planning toward maps and public meetings, under engineering or public works toward assets and CAD. Ask whether other departments treat the group as theirs to call on or as someone else's staff.
A year in, what would tell you this hire had worked out?
Why ask it
Listen for whether the measure is something you can count, such as a backlog cleared or a layer brought up to date, or something softer, such as departments that have stopped complaining. GIS work is hard to see when it goes right, so a manager with a ready answer has thought about how to notice it. Keep the answer and bring it to your first review.
How would I learn the local data and the area it covers in the first weeks?
Why ask it
Much of GIS competence is local: which road has two names, why the parcel layer stops at the river, who to phone about addresses. A handover with the person leaving, a ride-along with a field crew or a written guide would each shorten that. If none exists, plan on keeping your own notes from day one.
Does the organization pay for training, a user conference or a certification such as the GISP?
Why ask it
What was approved for the team in the past year is the real answer, since a policy on paper and a signed travel request are different things. Whether a certification changes pay or grade depends on the employer, so ask how it is treated there before you spend your own money on one.
What is the next step up from this job here, and has anyone on the team taken it?
Why ask it
Senior analyst, developer, database administrator and GIS coordinator are the usual directions, and each needs different experience from this seat. In a small shop the honest answer may be that the next step is the manager's job or another employer, which is worth knowing early. Where there are levels, the gap between this one and the next should be described in skills, not years.
How is the GIS program funded, and is this position permanent or tied to a grant or a project?
Why ask it
A position paid from a grant or a single contract can end when the money does, however good the work. Ask what happened to the last such role when its funding ran out. Arrangements differ from one employer to the next, so get the answer from them directly and do not guess from the posting.
Is the work on site, hybrid or remote, and do the data or the licenses limit where I can work from?
Why ask it
GIS has practical ties to the office: a license server, large files on a local network, a plotter, field gear. How the team works from home in practice matters more than the written policy, since a slow remote connection to a geodatabase can turn editing into waiting.
Next Steps
Does the hiring process include a hands-on GIS test, and which software is it in?
Why ask it
Some GIS hiring includes a practical task: make a map from supplied data, fix a broken layer, answer a spatial question. Knowing the software and whether it is timed lets you practice on the right thing. Ask whether you may bring notes or open the help documentation.
Would you like to see two or three maps from my portfolio?
Why ask it
Maps persuade better than a list of tools on a resume. Pick pieces that match what they said the job produces, and be ready to say which decisions in each were yours. If earlier work belongs to a past employer, show only what you are free to share.
Is there a part of this job, such as the scripting or the database side, where you are not sure my experience is enough?
Why ask it
It is a direct question, and it is your one chance to answer a doubt before the panel talks you over without you in the room. If they name a tool, say what you have done that comes nearest and how you would close the gap, without overstating. Leave it out if the interview has run long or they have already told you.
Will I meet others on the GIS team, or someone from a department it serves, before a decision is made?
Why ask it
The manager describes the job as planned. An analyst down the hall, or a planner who sends in map requests, describes it as it runs. If a meeting can be arranged, repeat the question about how the week splits between maps, analysis and data, and compare the two answers.
What is the pay range, and how are the technician, analyst and specialist titles ranked here?
Why ask it
Titles do not line up across employers: a technician in one place does what an analyst does in another. Ask what distinguishes the levels and which one this posting is. In a first interview, keep it for the recruiter or the end of the conversation unless they bring it up.
When do you expect to decide, and who should I follow up with?
Why ask it
Write down the date and the name. Public agencies and large firms can take weeks between an interview and an offer, so ask what the usual wait is there before reading anything into silence.
How to ask a GIS interviewer about the job
Practical guidance for the conversation itself
Getting your questions ready
Read the posting for its verbs
GIS postings list software, but the verbs say more about the job. Maintain, update and digitize describe a data role. Analyze, model and recommend describe an analysis role. Design, publish and configure point to cartography or web work. Mark which verbs dominate, then put the first question under The Work to the interviewer to test your reading.
Open what they have already published
Many organizations have a public map gallery, an open data site or a viewer app. Spend ten minutes in one before the interview. 'I looked at your zoning viewer. How often is that layer refreshed?' gets a fuller answer than a general question about data maintenance, and it shows you did the looking.
Save the technical ones for someone who edits
A GIS manager can answer everything under The Data and Tools. A planning director, an engineer or an HR officer may not know the license level or how edits are versioned. With them, lean on The Work, Requests and Team and Growth, and ask who could answer the technical ones later.
Decide your own split first
Before the interview, write down the week you would want: how much editing, how much cartography, how much analysis, how much scripting, how much time outdoors. What you hear only means something measured against that. Then mark the four or five questions whose answers could move the job toward it or away from it, and keep everything else as spare.
During the conversation
Trade questions as you go
When they ask about your editing or scripting experience, answer, then ask the matching question back: how edits are managed here, or what they would like automated. It turns the technical portion into a conversation, and you do not have to hold everything for the end.
Follow one layer from source to map
Pick a dataset they mention, parcels or water mains or trails, and trace it: where it originates, who edits it, how it is checked, where it is published. One thread followed all the way shows more about the program than five separate general questions.
Ask to see something
A map on the wall, the web viewer, the folder tree, a look at the plotter room. Most GIS people enjoy showing their work, and what they choose to show is what they are proud of. In a video interview, ask whether they could share a screen for a minute.
Check what a word means in this office
'Analysis' can mean a suitability model or a count of parcels inside a buffer. 'Web GIS' can mean one embedded map or a portal with hundreds of users. 'Database work' can mean a query now and then or being the only person who can restore a backup. When one of these comes up, ask for the most recent example before you take the word at your own meaning.
Making sense of what you hear
Three jobs share the titles
Put the answers together and one of three pictures usually appears. A production job has volumes, checks and a steady queue. An analysis job has questions, requesters and time to think. A one-person program has everything, including the server. No one of the three is the better job in general. What matters is which you want next.
A rough database is not a deal breaker
Untidy data with a plan and a budget to fix it can be the most instructive place to work, because you learn why the rules exist. Untidy data that nobody intends to fix means doing the same repairs every year. Listen for the direction more than the current state.
Count the people who understand the work
If your manager, a colleague and at least one requester know what good GIS looks like, your work will be seen. If nobody does, you would need to explain and advocate as well as produce. Some people thrive on that and build a program from it.
Weigh it against where you are
In a first GIS job, someone who reviews your edits and a colleague whose scripts you can read are worth a great deal. Later on, owning the schema, choosing the tools and designing the web maps your way may count for more. The same set of answers can add up to a different verdict depending on which of those you need now.
What to steer clear of
Sounding above the editing
Most GIS jobs include data maintenance, and the people interviewing you probably did years of it. Ask how much there is without implying it is beneath you. Curiosity about how to do it well goes over better than relief when the share is small.
Critiquing their setup
You may think shapefiles on a shared drive are behind the times. The person describing them knows the history and the budget. Ask what they would change if they could, and keep your verdict for your own decision.
Assuming it works like your last office
License arrangements, who may edit, what can be released and how titles are graded all differ between employers. Ask how it is done in this office and listen before comparing.
Letting a friendly interview skip the money questions
Whether the position is permanent or tied to a grant is under Team and Growth, and the pay range and title level are under Next Steps. Both are easier to raise before an offer than after it, and a conversation that has gone well is the one where they get forgotten.