Skip to content
EngineerAdvisory
Menu
Design
English

Engineer / Advisory / Services

A senior engineer in the room

Somebody on your side of the table when a supplier, a budget or an architecture decision needs a second informed opinion.

  1. One infrastructure plan for 14 departments

    Designed a comprehensive infrastructure framework for a research institute impacting 14 departments, featuring flexible modules, unified data pipelines, and structured support strategies for long‑term adoption.

    Designed a comprehensive infrastructure framework for a research institute across 14 departments — modular, with unified data pipelines and support strategies.

  2. Led a GIS map application to 10x revenue growth

    Led the software development of a GIS map application, driving revenue growth by 10x and positioning the product as a primary data asset.

    Led development of a GIS map application that became a platform cornerstone, driving a 10x revenue increase via upsells and data licensing.

  3. Directed full‑stack GIS map development

    Directed full‑stack GIS map development, overseeing PostgreSQL, Mapbox, ReactJS, and NodeJS to deliver an integrated solution.

    Directed full-stack GIS map development (PostgreSQL, Mapbox, React, Node.js), delivering one integrated, extensible core of the platform.

  4. Estimated 4,000 hours saved, team from 2 to 18

    Estimated 4,000 hours saved while mentoring a team that grew from 2 to 18 members, improving workflows and cross‑departmental coordination.

    Estimated 4,000 hours saved while mentoring a team that grew from 2 to 18, with improved workflows and cross-departmental coordination.

  5. Wrote 50,000 words of software documentation

    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.

    Wrote 50,000 words of software documentation in GitHub, Craft and Confluence, making knowledge durable, transparent and auditable.

  6. Led company growth from 4 to 14 employees

    Led company growth from 4 to 14 employees by employing Agile methodologies and effective project management practices.

    Led company growth from 4 to 14 employees with Agile practices, scaling the team without losing quality or cohesion.

  7. Led 30+ GIS projects from build to support

    Led the development, deployment, and support of over 30 GIS projects, demonstrating expertise in PostgreSQL, Bash, Python, JavaScript, GDAL, ArcGIS, PostGIS, and Mapbox technologies.

    Led development, deployment and support of 30+ GIS projects with PostgreSQL, Python, GDAL, ArcGIS, PostGIS and Mapbox across the lifecycle.

  8. Guided company projects through development

    Guided the execution of numerous company projects, offering expert support in the software development phases.

    Guided execution of many company projects with expert support through the hardest software-development phases, steadying delivery.

  9. Overhauled internal processes, saving 8,000 hours

    Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.

    Overhauled internal processes to save ~8,000 hours, improving software architecture, systems and scheduling efficiency.

  10. Streamlined CI/CD processes, saving 4,000 hours

    Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines.

    Streamlined CI/CD to save ~4,000 hours, making releases faster and more reliable so the team could ship with confidence.

  11. Set a zero‑warnings bar across six languages

    Set a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.

    Set a zero-warnings quality bar across Go, TypeScript, SQL, Python, Shell and Markdown, enforced by pre-commit hooks.

  12. Set the platform's founding technical decisions

    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.

    Set the platform's founding decisions in November 2025 — the layering, database-first data access and the zero-warnings bar — and they still hold.

  13. Delivered analysis and regular progress reports

    Delivered analysis and regular progress reports to the CEO, translating engineering KPIs and delivery status into decisions.

    Delivered analysis and regular progress reports to the CEO, translating engineering metrics and delivery status into confident decisions.

  14. Built a test suite across Go, SQL and browser

    Built a layered automated test suite — 981 Go tests, 543 frontend and browser specs, 494 SQL behavioural tests — with mutation testing, property‑based tests and an accessibility gate.

    Built a layered automated test suite — 981 Go tests, 543 frontend specs and 494 SQL behavioural tests — with mutation, property and accessibility gates.

  15. Built a 268‑check guard engine for the repo

    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.

    Built a guard engine of 268 registered commit checks, 277 lint rules and 15 custom ESLint rules, with 146 tests of the guards themselves.

  16. A safety net that no longer costs half an hour

    Cut the site's browser‑driven quality gate from 1,636 seconds to 615 by scheduling its checks longest‑first through a worker pool bounded to four lanes, after measuring that alphabetical order cost 320 seconds against 224.

    The gate went from 1,636 seconds to 615, while the checks got broader rather than thinner — the serial cost went up and the wall clock came down.

  17. Ran development as 51 written initiatives

    Ran the site's development as 51 written initiatives across 54 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.

    Fifty-one decisions with their reasoning attached, roughly three-quarters closed, and the declined ones are as retrievable as the accepted ones.

  18. Put the documentation under its own linter

    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.

    Twenty-six documents totalling about 2,666 effective lines, each under a budget that cannot grow, with every path and symbol they name checked against the…

  19. Linted the 10,242‑line quality gate itself

    Brought 10,242 lines of quality‑gate JavaScript under a formatter and a linter after establishing it was the largest body of code in the repository and the only one nothing read, fixing 13 findings and suppressing none.

    The largest and most load-bearing code in the repository is now formatted, linted and type-checked, with thirteen findings fixed and zero suppressions.

  20. Held the generator to 981 tests and 92% coverage

    Held the generator to 981 test cases at a 92% branch‑coverage floor with warnings treated as failures, and asserted idempotence by running the whole build pipeline twice from an empty file and requiring the second pass to change nothing.

    The pipeline can be re-run against a live database without fear, which is what makes incremental content work possible at all.

  21. Enabled every linter rule as an error

    Selected every rule the Python linter has as an error, working through 1,815 findings to reach zero, with each of the few exemptions carrying a written reason and two of them backed by a checker instead of a comment.

    The linter runs at full strength with zero findings, and every deviation is documented at the line where it is taken.

  22. Wrote tests for the checkers themselves

    Wrote tests for the checkers themselves after establishing that a checker fed only clean input will one day report clean because it read nothing — planting a misspelling to confirm the spell‑check finds it, and taking an id range from the database rather than from a number in the test.

    Every checker in the project now has a test that proves it fails on bad input, and the range assertions read from the source of truth.

  23. Found the hooks and the gate disagreeing

    Found the commit hooks and the quality gate running different checks while a document promised they were the same, by comparing the two lists in a test — the five that only ever ran by hand were the ones reading the CV prose.

    The hook and the gate provably run the same checks, and the prose checks now run on every commit.

  24. Adopted Swift 6 strict concurrency over C

    Adopted Swift 6 complete strict concurrency with no actors, bridging a blocking C event loop to the main actor through one producer, one consumer and one ordering — after establishing that a task per event loses the ordering the interface depends on.

    The application compiles under complete strict concurrency with no suppressions, and event ordering is a structural property rather than a hope.

  25. Took the test suite to 8.9 seconds

    Took the test suite from six tests over a sixty‑second limit to 135 passing in 8.9 seconds by profiling the main thread and removing the two calls it sat inside for 3,989 samples out of 4,017.

    The suite went from six tests over sixty seconds — 74 seconds of wall clock — to 135 tests passing in 8.9, which puts it inside the window where it runs on…

  26. Held 4 repositories to one history standard

    Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 48 instruction documents that govern how the work is done.

    Four repositories share one history format and one instruction structure, both enforced by hooks rather than by discipline.

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark