Hiring a GIS Developer in Turkey

Teams looking for a GIS developer in Turkey are usually not searching for a generic full-stack hire. They need someone who can own a map client, a spatial database, and the API in between — and who can invoice as a vendor or sit on a sprint board without a six-month relocation.

This note is written for product and engineering leads who are briefing a contractor or a small B2B engagement. It is the same split I use on services: contract capacity, scoped delivery, or architecture consulting.

What “GIS developer” actually means on a brief

The title is overloaded. In practice you are hiring one or more of:

A WebGIS engineer — OpenLayers, ArcGIS JS SDK, MapLibre, Cesium, editing tools, performance on large vector layers
A spatial backend engineer — PostGIS, GeoServer, OGC APIs (WMS/WFS), ETL, raster pipelines
A platform person — ArcGIS Enterprise, identity, symbology, interoperability, deployment

If the brief only says “we need a GIS developer,” ask whether the pain is the map UI, the data store, or the organisation of the GIS estate. Those are different weeks of work.

Stack that shows up on Turkish government, energy, and defence programmes is not exotic, but it is specific: ArcGIS, GeoServer, PostGIS, Angular or React, .NET or Node. I have written about two recurring failure modes: calling GeoServer from the browser and building a routing network in PostGIS.

Why Turkey (and Ankara) shows up in these searches

Ankara concentrates a lot of GIS software work: cadastre and land registry, energy infrastructure mapping, and defence C2 systems. That is why a search like “turkey gis developer” often means someone who has shipped national-scale or regulated spatial software, not only a Leaflet demo.

I am based in Ankara, Turkey, and work remotely with EU-timezone overlap. Typical buyers are product companies that need WebGIS without hiring a full geospatial team, and public-sector or defence suppliers that need extra senior capacity on an existing stack.

Examples of that environment are in the portfolio: NATO AirC2IS GIS modules, TKGM’s Webtapu platform, and energy/government GIS (EÜAŞ, MCBS, NEFES, TADLAB). Academic work such as flood susceptibility mapping for Ankara is useful proof of spatial methods; it is not a substitute for production delivery.

Contract, B2B project, or consulting

These are not the same purchase:

Contract engineering (T&M). You already have a codebase and a process. You need a senior GIS / full-stack engineer on the roster — map modules, spatial APIs, performance. You keep the product; they add capacity.

B2B project delivery. You need a vendor on a purchase order: data model, API, map UI, handover. Fixed-scope or milestones, NDA and IP as agreed.

Architecture consulting. The question is stack, symbology, OGC/NATO interoperability, or how to modernise a GIS estate. The output should be written, not only meetings.

If you are unsure which one you are buying, start with a short brief rather than a six-month seat. How that conversation runs is on the services page.

What to put in a brief

A useful first email is short:

Stack you already have (or are willing to adopt)
Whether this is a contractor on your team or a scoped delivery
Timeline and timezone constraints
Whether an NDA is required before architecture detail

I take that kind of brief at contact. Language is English or Turkish; invoicing is B2B through a sole proprietorship in Ankara.

What not to over-index on

A public GitHub demo is a good signal for craft. It is not the same as having shipped a closed cadastre or C2 system. Conversely, classified or government work will not have a live URL — look for role, duration, constraints (OGC, symbology, scale), and whether the person can talk about their slice of the system.

“Full-stack plus GIS” is a real combination; “full-stack, and we will add a map later” is how spatial debt starts. If the map is the product, hire for GIS first.

A realistic first month

On a contract engagement the first weeks are usually: access to the repo and GIS environment, a thin vertical slice (one layer, one API, one map interaction), then performance and data-volume checks before new features. On a B2B build the same month is discovery and a written scope — data sources, coordinate systems, edit vs view-only, who hosts GeoServer or ArcGIS Enterprise — so you are not paying for a rewrite of an undocumented CAD export.

Remote from Ankara works for EU stand-ups. What does not work is treating GIS as a weekend plugin: spatial indexes, SLD/symbology, and OGC service design show up late if nobody on the team has shipped them.

Defence and government programmes add constraints (network zones, standards, no public demo). Ask for that up front; it changes both the contract and the architecture note.

Hiring a GIS Developer in Turkey — WebGIS, ArcGIS, PostGIS