Geospatial Developer | Backend Developer

I have spent 20+ years working where the real world meets technical systems: land survey, CAD production, civil design, LiDAR, Trimble workflows, Carlson, Civil 3D, QGIS, field-to-finish data, deliverables, and the messy production problems that never show up in a tutorial.

Now I’m turning that experience into software.

My focus is backend and geospatial development: Python, FastAPI, SQL, data processing, automation, APIs, Linux, Docker, and practical tools that help technical teams move faster with fewer mistakes.

I’m not trying to become a generic developer.

I’m building from a domain I actually know.

My target path is the overlap between:

• backend development
• geospatial software
• survey and CAD workflow automation
• data-heavy production systems
• APIs and internal business tools
• Linux, Docker, Git, CI/CD, and practical deployment workflows

The goal is simple: build software that solves real operational problems, especially in environments where accuracy, repeatability, documentation, and data integrity matter.

Best-fit roles I’m working toward:

• GIS / Geospatial Developer
• Backend Developer
• Automation / Workflow Developer
• Technical Systems Developer
• DevOps-aware Backend Developer

A company portal and workflow platform built around real land survey operations.

Survey work has its own rhythm: research, field work, CAD production, QA/QC, client communication, deliverables, revisions, and a lot of project knowledge scattered across people, folders, emails, and spreadsheets.

SurveyOS is aimed at bringing that workflow into one practical system.

Focus areas

• project information and production status
• survey operations workflows
• client-facing communication
• deliverable tracking
• backend and workflow logic
• usable systems for real office production

A Python-based backend application for survey and geospatial calculations.

This project is focused on reducing repetitive manual calculation steps and creating repeatable processing workflows for survey production.

Planned / active areas

• station and alignment data
• bearings, curves, and coordinate-related calculations
• CAD/GIS-compatible exports
• DXF and shapefile workflows
• practical geospatial data processing

I have worked inside technical production environments long enough to know where software helps and where it just gets in the way.

The useful tools are usually not the loudest ones.

They are the ones that:

• remove repeated manual steps
• make data easier to trust
• reduce rework
• keep workflows consistent
• make handoffs cleaner
• help people find the information they need
• turn tribal knowledge into repeatable systems

That is the kind of software I want to build.

I’m actively deepening my backend foundation through Boot.dev, with a focus on Python, Linux, Git, algorithms, data structures, backend development, and DevOps fundamentals.

I’m also continuing coursework through Coursera and Codecademy while building real projects around geospatial workflows, backend systems, and automation.

The point is not collecting course badges.

The point is doing the work consistently and turning it into practical software.

Email: hbabb@heath-babb.com

LinkedIn: linkedin.com/in/heath-babb
X: x.com/techsolvd

20+ years in land survey, civil design, CAD production, and technical workflows — now building backend and geospatial software from that foundation.