Theodoros Mangas
Licensed surveyor turned Python/Django engineer — I build the tooling for the industry I came from.
Geospatial pipelines, validation-heavy workflows, and web apps that hold up in the field.
Python Django REST APIs PostgreSQL JavaScript HTML/CSS Git Docker System Design GIS
I spent a decade as a licensed surveying and geoinformatics engineer before moving into software. That path is the point: I write software for workflows I used to do by hand, so I know where the data goes wrong and what the field actually needs.
Backend Python/Django is my core — API design, data modeling, and application structure. Most of my work involves geospatial pipelines (DXF/KML/KMZ/TXT/JSON), where bad input is the norm and predictable output is the whole job, so I design validation first and fail loudly rather than silently.
I care most about systems that stay maintainable after launch: reusable patterns over one-off code, and interfaces that make user error hard.
Status: Live and in daily use by a working technical office, with a public toolbox of 10+ engineering utilities.
Architecture: A shared component layer with standardized patterns, so each new tool reuses the existing converters, validation, and UI instead of rebuilding them. Currently supports 5+ engineering utilities.
Status: Built and deployment-ready; not yet running with live users. Designed so multiple volunteer teams can work the same map without duplicating or overwriting each other's records.
Backend & APIs
GIS & Data Processing
Frontend & Tools
Methodologies & Soft Skills
Each one takes messy real-world input, validates it hard, and returns a predictable file — that validation-first approach is the common thread across everything here.
A note on source: these are client and business codebases, so the repositories are private rather than public. I'm happy to walk through the code, architecture decisions, or a specific module on a call.
Build full-stack web applications in Python/Django, taking projects from concept to deployment. Most of the work sits where software meets surveying: geospatial integrations, file-conversion pipelines, and internal tools for technical offices — the problems I used to hit from the other side.
Ran field surveys and data collection, then moved into geospatial processing: vector formats, coordinate systems, and quality control on spatial deliverables. Repeatedly hit the same gap — the tooling for this work was manual, brittle, or didn't exist — which is what pushed me into software. That domain knowledge still drives what I build.
Let's connect! I’m always open to discussing new opportunities, collaborations, or challenging projects across Python development, backend systems, and modern web applications.