<\/p>\n
Most hiring managers we talk to describe the same problem in the same way. The role has been open for months. The applicants who apply aren’t qualified, and the people who are qualified aren’t applying. The conclusion follows quickly: there’s nobody out there.<\/p>\n
There usually is. The candidate pool and the capability pool are two different things, and the gap between them is where a lot of good hires are sitting.<\/p>\n
The pool is smaller than the capability<\/strong><\/p>\n Geospatial is a specialized field, and the people who carry a GIS, surveying, or remote sensing job title are a finite group. When every employer in the sector targets that same group with the same keywords, the math gets ugly. You’re not competing on compensation or culture at that point. You’re competing for attention from a few hundred people who already have jobs.<\/p>\n Meanwhile, there are professionals in engineering, utilities, defense, agriculture, environmental consulting, and software who do work that overlaps heavily with what you need \u2014 and who never appear in your search because their title and skill section say something else.<\/p>\n That’s transferrable experience: skills and experience that can be applied successfully in a different industry, market, or role. It’s a term we use with clients constantly, because it’s usually the difference between a role that fills and a role that doesn’t.<\/p>\n What actually transfers<\/strong><\/p>\n Some capability moves cleanly across industry lines. In our placements, the things that travel best are:<\/p>\n Spatial reasoning.<\/strong> Someone who has spent years working with coordinate systems, datums, projections, and accuracy standards understands the fundamentals no matter which industry taught them. Civil engineers, cartographers, environmental scientists, and military imagery analysts all arrive with this.<\/p>\n Field discipline.<\/strong> Data collection in the field is its own skill \u2014 weather, equipment, site access, and the judgment to know when a reading is wrong. Utility locators, construction survey crews, forestry technicians, and precision agriculture operators have it.<\/p>\n Data engineering fundamentals.<\/strong> SQL, Python, database design, and ETL work don’t change much when the data gains a geometry column. Software and data professionals often pick up spatial databases faster than a GIS specialist picks up production-grade engineering.<\/p>\n Domain knowledge of your customer.<\/strong> A candidate who spent six years inside a utility, a DOT, or an insurance carrier already understands your client’s regulatory environment, asset lifecycle, and internal politics. That knowledge takes a long time to teach and it’s frequently more valuable than tool fluency.<\/p>\n Imagery interpretation.<\/strong> Remote sensing skills built in defense, intelligence, or agriculture apply directly to commercial work. Transitioning military personnel are one of the most consistently overlooked groups in the market.<\/p>\n What doesn’t transfer<\/strong><\/p>\n We’d be doing you a disservice if we pretended everything crosses over.<\/p>\n Licensure doesn’t.<\/strong> A Professional Land Surveyor license requires time under a licensed surveyor and is jurisdiction-specific. No amount of adjacent experience shortcuts it. If the role requires a PLS, it requires a PLS.<\/p>\n Clearance is portable, but not instantly.<\/strong> Prior clearance helps significantly. It still isn’t the same as an active, transferable one, and reciprocity varies by agency.<\/p>\n Specific software takes real hours.<\/strong> Someone with an adjacent background can learn the Esri stack, Trimble Business Center, or FME. They can’t learn it in the first week, and pretending otherwise sets everyone up to fail.<\/p>\n Accuracy standards and deliverable norms take time.<\/strong> ASPRS specifications, survey deliverable conventions, and QA expectations are learned on the job. A capable hire will absorb them, but there needs to be time to do so.<\/p>\n The honest framing is this: transferrable experience shortens your search, not your onboarding.<\/p>\n Rewrite the requirements before you rewrite the search<\/strong><\/p>\n Most job descriptions in this industry are written as a list of tools. That list is what filters out the adjacent candidates before anyone reads their r\u00e9sum\u00e9.<\/p>\n Try splitting your requirements into two columns. In the first, put what someone must arrive with \u2014 licensure, clearance, a specific certification, the judgment that only comes from years of doing the work. In the second, put what a capable person could learn in 90 days with support.<\/p>\n Most lists shrink dramatically. When they do, the search widens on its own.<\/p>\n Then write the posting around outcomes rather than software. “You’ll build and maintain the spatial data model behind our asset management program” attracts a different and larger group than “5+ years ArcGIS Pro, ArcGIS Enterprise, FME, SQL.”<\/p>\n Screen for capability, not vocabulary<\/strong><\/p>\n Adjacent candidates interview differently. They won’t use your internal shorthand and they may not name your tools. That’s not the same as not being able to do the work.<\/p>\n Ask them to walk through a spatial problem they’ve solved end to end \u2014 how they got the data, what they did about the parts that were wrong, and how they knew the answer was right. Ask what happens when two datasets disagree. Ask how they’d explain a confidence interval to a client who doesn’t want to hear about one.<\/p>\n Someone who can answer those questions well will learn your software. Someone who can only name your software may not be able to answer them at all.<\/p>\n Budget the ramp, and say so out loud<\/strong><\/p>\n The most common failure we see isn’t a bad hire. It’s a good hire dropped into a role with no plan for the gap everyone knew existed.<\/p>\n Make the plan before you make the offer. Who’s training them, on what, over how long, and what does month three look like compared to month one. Put it in the offer conversation. Candidates coming from adjacent fields are usually more committed than internal hires precisely because they’re making a deliberate move \u2014 but they need to know you’ve thought it through.<\/p>\n One more thing: transferrable experience is not a discount. If you’re hiring someone with 10 years of relevant capability and a different job title, you’re hiring 10 years of capability. Pricing the role as entry-level because the title doesn’t match is the fastest way to lose the hire in week six.<\/p>\n When not to do this<\/strong><\/p>\n If the role is a single-person function with nobody available to train, hire someone who’s done exactly the job. If the timeline is genuinely immovable, hire for immediate fit and pay for it. If licensure or active clearance is a hard gate, the gate is real.<\/p>\n Everywhere else, the wider search is usually the faster one.<\/p>\n","protected":false},"excerpt":{"rendered":" Most hiring managers we talk to describe the same problem in the same way. The role has been open for months. The applicants who apply aren’t qualified, and the people who are qualified aren’t applying. The conclusion follows quickly: there’s nobody out there. There usually is. The candidate pool and the capability pool are…<\/p>\n","protected":false},"author":13,"featured_media":19176,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"none","footnotes":""},"categories":[7],"tags":[],"class_list":["post-19173","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-employer-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19173","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=19173"}],"version-history":[{"count":3,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19173\/revisions"}],"predecessor-version":[{"id":19179,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/posts\/19173\/revisions\/19179"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/media\/19176"}],"wp:attachment":[{"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/media?parent=19173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/categories?post=19173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/geosearch.com\/af-api\/wp\/v2\/tags?post=19173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}