Skip to content
EngineerAdvisory
Menu
Design
English

Engineer / Advisory / Services

Deciding how the whole thing should be built

The shape of a system worked out on paper first, so the parts fit and the cost is known before anyone writes code.

  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. 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.

  4. Migrated the API to Huma v2 at 100% parity

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths and 760 operations — reaching and holding 100% parity between the routes the server registers and the OpenAPI description it publishes.

    Migrated the HTTP API from Fiber to Huma v2 — 649 paths, 760 operations — at 100% parity between registered routes and the published OpenAPI description.

  5. 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.

  6. 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.

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