20 tasks, each one witnessed by the sources that watched the job — and behind every one, a prompt you can use tonight.
You usually split time between coding, data work, and meetings. Mornings often start with a stand-up in JIRA to track tasks and bugs; then you write or review C# scripts, SDK code, or AWS Lambda functions that serve map services.
Afternoons go to data checks: reviewing incoming survey or aerial data for accuracy, processing collected survey data into GIS layers, or producing thematic maps in ArcGIS-compatible formats. You also meet stakeholders to confirm cartographic choices and run quick performance checks on map servers or cloud resources like AWS.
Start with the systems you’ll touch every day: a GIS desktop (ArcGIS or QGIS) for mapping and geoprocessing, and a vector CAD tool like Autodesk AutoCAD or Bentley MicroStation for working with survey and engineering drawings. Learn basic cartography: selecting symbols, color ramps, and scales for thematic maps.
Also pick up C# for custom tools or plugins and basic AWS concepts (S3, EC2, Lambda) to deploy map services. Familiarity with JIRA helps you follow tasks and coordinate with clients. Apple iOS is useful if you’ll support mobile field apps.
Use AI for repetitive tasks: auto-classifying land-cover from aerial imagery, extracting features, or cleaning attributes. But always validate: review AI outputs against ground-truth survey data or ortho photographs and keep a manual QC step. Document any AI model, dataset, and version so others can reproduce results.
Never let automation overwrite original data without backups. For critical use—surveys or geological mapping—keep human review and maintain compliance with industry standards and client requirements. Log decisions in JIRA and keep retrainable workflows in AWS or your build system.
According to the U.S. Bureau of Labor Statistics (BLS) for related GIS and mapping occupations, about 435,370 people were employed; the median wage was $116,580 per year, the lowest tenth earned $55,940, and the top tenth earned $188,470. These numbers give a broad band: entry roles or local government jobs often sit near the lower end; experienced developers or cloud-focused specialists move toward the top.
Your pay also depends on skills—C#, cloud experience (AWS), CAD (AutoCAD or MicroStation), and domain knowledge like surveying or geological mapping usually raise offers. Cite BLS when negotiating.
You inspect metadata and run checks for currency, accuracy, and completeness: look at timestamps, coordinate systems, point density, and attribute completeness. Convert technical file formats into your GIS project CRS and flag missing or inconsistent attributes.
Then process collected survey data—apply surveying calculations, filter noise, and optionally use control points from known sources. For aerials, interpret ortho photos to confirm features. Log issues in JIRA and coordinate with the data provider or client to fix or document limitations.
A surveyor collects raw field measurements, performs precise surveying calculations, and certifies control points. A CAD drafter creates engineering drawings in AutoCAD or MicroStation. A GIS developer converts technical info into digital map products, writes code (often C#), builds spatial databases, and deploys map services (often on AWS).
GIS developers work more with analysis, thematic mapping, and web/mobile delivery. You’ll often take survey or CAD outputs, clean and georeference them, then produce maps or APIs that stakeholders use. Collaboration with surveyors and drafters is routine.