Tool library — category filters and live search across the modular toolbox
Modular platform architecture with reusable components, shared UI components, and standardized patterns for converters, utilities, and geospatial helpers.
Software engineer (Python/Django) who ships full-stack platforms for real clients - from custom-CMS websites to geospatial data pipelines.
A decade as a licensed surveyor before that: I design for how field data actually breaks — validation-first, fail loud, never silently wrong.
Tool library — category filters and live search across the modular toolbox
Modular platform architecture with reusable components, shared UI components, and standardized patterns for converters, utilities, and geospatial helpers.
Public toolbox — searchable engineering utilities, free to use
Full-stack Django platform I built and operate for my own technical-office practice, combining dynamic service pages, project showcases, multilingual content (Greek/English), team profiles, and secure customer management.
Public site — bilingual (EL/EN) with staff-managed carousel and announcements
Full-stack Django site built for a museum client in place of an off-the-shelf CMS, so every part of the site — exhibits, events, pages, team, media — is editable by their own staff through a purpose-built moderator dashboard with role-based access and soft-delete recovery.
Live city map — volunteer actions logged against real locations
A web application that lets volunteer teams record and manage real-world actions directly on a live city map — incidents, maintenance, field tasks, observations — with role-based workflows and location-linked records.
Backend Python/Django is my core - API design, data modeling, and application structure. I build full-stack platforms for real clients: custom CMS-driven sites and 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.
Before software, I spent a decade as a licensed surveying and geoinformatics engineer. That background is why I build this way: I used to do these workflows by hand, so I know exactly where the data goes wrong and what the field actually needs.
I care most about systems that stay maintainable after launch: reusable patterns over one-off code, and interfaces that make user error hard.
Build full-stack web applications in Python/Django, both as part of an in-house engineering team and through independent client contracts. On the freelance side, I deliver platforms end to end - architecture, build, deployment, and ongoing maintenance - and have shipped 3 client platforms this way, including a bilingual museum CMS built solo in ~3 months and a volunteer operations platform with live city mapping.
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.
Open to Python/Django roles and contract work — backend systems, full-stack platforms, and geospatial tooling. The fastest way to reach me is email.