Most interviews end the same way.<\/p>\n
\u201cDo you have any questions for us?\u201d<\/strong><\/p>\n Forty minutes into proving you\u2019re qualified, most candidates ask something safe about company culture, benefits, or what a typical day looks like.<\/p>\n There\u2019s nothing wrong with those questions. But this is also your opportunity to find out whether the job is actually worth taking.<\/p>\n You\u2019re being evaluated throughout the interview\u2014but you\u2019re evaluating the company, too.<\/p>\n And you probably won\u2019t have another chance to sit across from the hiring manager with this level of access before you have to make a decision.<\/p>\n So skip the questions that produce polished answers.<\/p>\n Ask the ones that produce information<\/strong>.<\/p>\n Ask this early, ideally during the first conversation.<\/p>\n There are plenty of legitimate reasons a geospatial position might be open: the company is growing, someone was promoted, a new client created demand, or someone left.<\/p>\n Those answers tell you very different things about the opportunity.<\/p>\n If it\u2019s a replacement, ask how long the previous person was in the role.<\/p>\n Eleven months is worth understanding.<\/p>\n Six years is a pretty good sign.<\/p>\n You\u2019re not looking for a perfect answer. You\u2019re looking for a clear one<\/strong>.<\/p>\n Hesitation or a vague explanation doesn\u2019t automatically mean something is wrong, but it may mean the story is more complicated than the job posting suggests.<\/p>\n That\u2019s useful information, too.<\/p>\n This might be the single most useful question on the list\u2014and it\u2019s one candidates ask surprisingly rarely.<\/p>\n You want to understand the shape of the team<\/strong>, not just the headcount.<\/p>\n How many people are there? What levels are they? Who does what?<\/p>\n Is there someone senior you can learn from?<\/p>\n Are there peers at your level?<\/p>\n Will you be the only person doing GIS?<\/p>\n Is there dedicated database or data engineering support, or will you be responsible for your own plumbing?<\/p>\n The same job title can mean completely different things depending on the answers.<\/p>\n A GIS Analyst on a team of eight with a senior GIS specialist, database administrator, and GIS manager has a very different job from a GIS Analyst who is the GIS department<\/strong>.<\/p>\n The second role may be significantly more demanding than the job posting makes it sound.<\/p>\n Then ask:<\/p>\n \u201cHow long has the manager been in the role, and how long have the current team members been here?\u201d<\/strong><\/p>\n If a team of five has three open positions, you’ve learned something important.<\/p>\n Every organization does geospatial work a little differently.<\/p>\n Different naming conventions. Different QA standards. Different deliverable formats. Different workflows that somehow everyone knows but nobody ever documented.<\/p>\n You may have years of GIS, surveying, LiDAR, photogrammetry, or remote sensing experience and still have a lot to learn when you walk into a new organization.<\/p>\n So ask what the first 30, 60, and 90 days are expected to look like.<\/p>\n Who will you learn from?<\/p>\n What are you expected to produce in your first month versus your third?<\/p>\n Will you be working on live client deliverables immediately?<\/p>\n Small companies often don’t have formal onboarding programs\u2014and that’s okay.<\/p>\n What matters is whether they’ve thought about how you’re going to get up to speed.<\/p>\n \u201cYou’ll work alongside our senior analyst for the first six weeks, and we don’t put new employees on client work until month two\u201d<\/strong> is a good answer from a company of twelve people.<\/p>\n \u201cYou’ll pick it up as you go. We move fast here.\u201d<\/strong><\/p>\n That’s a very different answer.<\/p>\n Ask this instead of:<\/p>\n \u201cIs there room for growth?\u201d<\/strong><\/p>\n Everyone can say yes to that question.<\/p>\n Asking about a specific person requires evidence.<\/p>\n Ask about someone who started at the level you’re considering and has since taken on more responsibility.<\/p>\n What did their career progression look like?<\/p>\n How long did it take?<\/p>\n What changed\u2014title, responsibilities, compensation, technical specialization, management?<\/p>\n If the hiring manager can immediately name someone, that’s a real data point.<\/p>\n And sometimes the honest answer is that growth at a small company doesn’t necessarily mean climbing a traditional corporate ladder.<\/p>\n It might mean becoming the technical expert, managing larger projects, working directly with clients, expanding into new technologies, or earning more without changing your title every two years.<\/p>\n That can be a great career path.<\/p>\n What should concern you is enthusiasm without evidence<\/strong>.<\/p>\n This is one of the details job postings get wrong most often.<\/p>\n And it isn’t always intentional.<\/p>\n Sometimes the person who wrote the posting simply didn’t know.<\/p>\n If travel matters to you, don’t settle for adjectives.<\/p>\n Ask for numbers.<\/p>\n How many days per month? Which months? Is travel seasonal? Are overnight trips common? How far in advance is travel scheduled?<\/strong><\/p>\n This is especially important for roles involving surveying, aerial acquisition, LiDAR, photogrammetry, field data collection, or other project-based work.<\/p>\n \u201cSome travel\u201d isn’t really an answer.<\/p>\n If you accept a position expecting occasional travel and discover that it means two weeks a month every spring, that’s a significant difference.<\/p>\n Get specific before you accept.<\/p>\n You don’t necessarily need to wait until the offer stage to understand the complete compensation picture.<\/p>\n In geospatial roles, compensation can include quite a bit more than base salary.<\/p>\n Ask about things like:<\/p>\n Some of these benefits can add thousands of dollars in value over the course of a year.<\/p>\n A base salary that initially looks a little low might be much more competitive when the complete package is considered.<\/p>\n And the reverse can be true, too.<\/p>\n A salary that looks great on paper may not be as attractive if you’re paying for certifications, conferences, travel expenses, or other professional costs out of your own pocket.<\/p>\n Look at the whole package\u2014not just the number.<\/strong><\/p>\n None of these questions are aggressive.<\/p>\n They only become uncomfortable if they’re delivered like an audit.<\/p>\n Frame them around your desire to understand the role and succeed in it.<\/p>\n Something as simple as:<\/p>\n \u201cI want to understand what I’d be walking into so I can be useful quickly.\u201d<\/strong><\/p>\n That changes the tone of the conversation.<\/p>\n You’re not looking for reasons to reject the company.<\/p>\n You’re trying to understand how you can contribute.<\/p>\n Good managers generally respond well to that. In fact, many hiring managers wish candidates asked better questions.<\/p>\n And don’t feel like you need to run through this entire list in one interview.<\/p>\n Ask two or three during the initial conversation and use later interviews to dig deeper.<\/p>\n You’ll often get better answers after you’ve met the team and established some rapport.<\/p>\n Here’s the important part:<\/p>\n Vagueness is data.<\/strong><\/p>\n An employer who can’t explain their team structure, name a single person who has progressed, or give you a realistic picture of travel is telling you something about how the role is managed.<\/p>\n That doesn’t automatically mean don’t take the job<\/strong>.<\/p>\n Plenty of good opportunities exist inside imperfect organizations.<\/p>\n In fact, a manager who says:<\/p>\n \u201cHonestly, it’s a bit of a mess right now\u2014and fixing it is part of the reason we’re hiring this position.\u201d<\/strong><\/p>\n may be giving you a much more valuable answer than someone with a perfectly polished response.<\/p>\n They’re being honest about the work.<\/p>\n And sometimes that’s exactly the opportunity you’re looking for.<\/p>\n The goal isn’t to find a perfect company.<\/p>\n The goal is to understand what you’re signing up for.<\/p>\n Because the best time to discover what a job is really like isn’t three months after you start.<\/p>\n It’s during the interview.<\/strong><\/p>\n Ask better questions. Get better information. Then decide whether the opportunity is right for you.<\/p>\n","protected":false},"excerpt":{"rendered":" Most interviews end the same way. \u201cDo you have any questions for us?\u201d Forty minutes into proving you\u2019re qualified, most candidates ask something safe about company culture, benefits, or what a typical day looks like. There\u2019s nothing wrong with those questions. But this is also your opportunity to find out whether the job is actually…<\/p>\n","protected":false},"author":13,"featured_media":19249,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"none","footnotes":""},"categories":[20],"tags":[],"class_list":["post-19246","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-job-search"],"acf":[],"_links":{"self":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19246","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/comments?post=19246"}],"version-history":[{"count":2,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19246\/revisions"}],"predecessor-version":[{"id":19251,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19246\/revisions\/19251"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/media\/19249"}],"wp:attachment":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/media?parent=19246"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/categories?post=19246"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/tags?post=19246"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}1. \u201cWhy is this role open?\u201d<\/h2>\n
2. \u201cHow is the team structured?\u201d<\/h2>\n
3. \u201cWhat does the first 90 days look like?\u201d<\/h2>\n
4. \u201cCan you tell me about someone who has grown in this role?\u201d<\/h2>\n
5. \u201cWhat is the actual field and travel split?\u201d<\/h2>\n
6. \u201cWhat sits around the base salary?\u201d<\/h2>\n
\n
How to Ask Without Sounding Difficult<\/h1>\n
What a Bad Answer Is Telling You<\/h1>\n