Technical Leadership

• Designed a comprehensive infrastructure framework for DTU impacting 14 departments, featuring flexible modules, unified data pipelines, and structured support strategies for long‑term adoption.
• Led the software development of a GIS map application, driving revenue growth by 10x and positioning the product as a primary data asset.
• Directed full‑stack GIS map development, overseeing PostgreSQL, Mapbox, ReactJS, and NodeJS to deliver an integrated solution.
• Saved 4,000 hours by mentoring and growing a team from 2 to 18 members, optimizing workflows and fostering cross‑departmental collaboration.
• Wrote 50,000 words of comprehensive software documentation utilizing Markdown in GitHub, Craft, and Confluence, thereby ensuring the retention of knowledge and the transparency of the process.
• Led company growth from 4 to 14 employees by employing Agile methodologies and effective project management practices.
• Led the development, deployment, and support of over 30 GIS projects, demonstrating expertise in PostgreSQL, Bash, Python, JavaScript, GDAL, ArcGIS, PostGIS, and Mapbox technologies.
• Guided the execution of numerous company projects, offering expert support in the software development phases.
• Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.
• Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines.
• Architected a layered maritime platform separating a Next.js PWA frontend, a Go (Huma/Fiber) API, and a PostgreSQL function layer, keeping all business logic in the database.
• Authored 578 go‑task automation targets spanning native, Docker and HTTPS dev modes, linting, testing, database and deployment.
• Set a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.
• Set the platform's founding decisions in the weeks after the repository opened in November 2025 — the layering, database‑first data access and the zero‑warnings bar — and they still hold nine months on.
• Delivered analysis and regular progress reports to the CEO, translating engineering metrics and delivery status into decisions.
• Designed a time‑management and reporting system that remained in production use for years without significant modification.
• Automated team collaboration, password management, task and time management, and built a semi‑automatic project‑showcase system, raising team productivity.
• Built the repository's guard engine — 268 registered commit checks, 277 lint rules and 15 custom ESLint rules — plus 146 tests of the guards themselves, so the build holds the standard, not review.
• Ran the site's development as 49 written initiatives across 52 plan documents, each carrying its open boxes, its measurements and the decisions it declined — including six of eight agent‑readiness findings refused with the reason recorded.
• Put the documentation under its own linter — a per‑file line budget that only ratchets down, an index requirement and a real‑path check — which found six of nine plans marked done while carrying unchecked boxes, and fourteen commit‑gating tasks named in no document.
• Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 46 instruction documents that govern how the work is done.

This work is part of what we offer as Technical Leadership & Consulting, Project Management (Agile), DevOps & CI/CD Automation, Technical Documentation, Full‑Stack Product Development, Platform & Solution Architecture, Backend & API Development and Frontend Development.

Building something that needs this? Get in touch.