Nearshore GIS Analysts from Latin America

Most candidates we place have ArcGIS Pro and ArcGIS Enterprise as their primary platforms, with QGIS used alongside them. ArcGIS Online and Experience Builder proficiency is common at the mid and senior levels. For scripting, ArcPy is the most widely held automation skill, with Python libraries like GeoPandas and Shapely following closely. We screen specifically for the tools your environment uses before submitting candidates, so you’re not filtering through resumes from people who know QGIS when your shop runs ArcGIS Enterprise exclusively.

Colombia and Costa Rica are US Eastern and Central time, no offset or one hour depending on DST. Mexico City is US Central. Argentina is ET plus one hour in summer, no offset in winter. For the core hours that matter, 9 AM to 5 PM ET, all four countries overlap completely. If your standups or data reviews happen outside those hours, Colombia is the tightest fit. Three of our last five GIS engagements have been clients in Pacific time zones who said the Colombia-based analysts were more reachable during overlap hours than contractors they’d previously hired in Eastern Europe.

Short answer: yes, the ones we place do. Understanding US state plane coordinate systems, NAD83, WGS84, NLCD land cover classifications, Census TIGER data, and federal spatial data standards like NSDI is part of our technical screening. Analysts who’ve worked on US government or infrastructure projects specifically have direct experience with those data sources. We don’t submit candidates who’ve only worked with European or local national spatial frameworks when the client’s work is US-specific. That mismatch gets caught at the portfolio review stage.

Esri certifications are globally available and not tied to US geography. Candidates who don’t yet hold a certification can pursue it after placement. Whether the client or Kore BPO funds that certification is a conversation we have at the offer stage. What we don’t do is count a stated intent to certify as equivalent to existing certification in our screening. If your role requires a current ArcGIS Desktop Associate or Professional certification, we verify it before submission. See our GIS hiring guide for what to prioritize.

Three different roles, easily conflated. The GIS analyst runs spatial queries, builds maps, writes Python automation, and delivers analysis outputs to stakeholders. GIS developers build web applications, typically in ArcGIS Online, Leaflet, or Mapbox, where the end user interacts with a spatial interface. Spatial data engineers build and maintain the data pipelines that feed both. Analyst is the most common hire. Developer becomes necessary when you’re building a public-facing map application or an internal spatial dashboard. Engineer is the role when you have large-volume spatial ETL requirements. We staff all three, and we’ll help you figure out which one you actually need before we start the search.

90-day replacement guarantee on all placements. If the hire isn’t working within the first 90 days, we find a replacement at no additional placement fee. The cases where this comes up are almost always role-scope mismatches that happened upstream, the job description said analyst but the work was developer-level, or the team structure changed after the hire was made. We do a project kickoff call before every search specifically to catch those gaps before they become 90-day problems.

Probably not. We’re better suited to ongoing or at-least-12-month engagements than to a discrete 6-week data processing project. For a one-time task, a freelance GIS consultant or a project-based Esri partner makes more sense. We’re the right fit when you need a GIS analyst embedded in your team for the long term, whether that’s a direct hire, a year-long contract, or a role that started project-based and evolved into something permanent. If your timeline is genuinely short and bounded, we’ll tell you that upfront rather than try to staff it anyway.