Skip to content
EngineerSoftware
Menu
Design
English

Engineer / Software / 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. A mapping product, carried end to end

    Architected, developed and supported infrastructure, data processing and a map application over 2 years, covering both software delivery and operational maintenance.

    Architected, built and supported infrastructure, data processing and a map application over two years, covering delivery and operational maintenance.

  5. Infrastructure simplified beyond AWS

    Reworked an international client’s infrastructure by removing unused services, adjusting capacity and moving workloads away from AWS. The founder reports a 10x reduction in cloud costs with no loss of productivity.

    Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.

  6. A maritime platform with clear system boundaries

    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.

    Architected a layered maritime platform — Next.js PWA, a Go (Huma/Fiber) API and a PostgreSQL function layer holding all business logic.

  7. Designed a JSON passthrough from Postgres to API

    Designed a JSON passthrough architecture where PostgreSQL functions return complete JSON forwarded verbatim by the Go API, eliminating intermediate unmarshalling and decoupling the frontend from schema changes.

    Designed a JSON passthrough where PostgreSQL functions return complete JSON forwarded verbatim by the Go API, decoupling the frontend from schema.

  8. Built organization context switching for users

    Designed an organization context‑switching system with client localStorage and server‑side cookie mirroring, letting users act as managed organizations while enforcing least‑privilege authorization.

    Built organization context-switching with localStorage and server cookie mirroring, letting users act as managed orgs under least-privilege auth.

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

  10. Designed a function‑first PostgreSQL data layer

    Designed a PostgreSQL function‑first data layer — 1,275 stored functions across 34 schemas — so every read and write goes through a function the database can grant, rather than through a table.

    Designed a PostgreSQL function-first data layer — 1,275 stored functions across 34 schemas — with the access boundary enforced by the database itself.

  11. Modeled 348 tables across 34 Postgres schemas

    Modeled the maritime domain into 348 normalized tables across 34 PostgreSQL schemas — professionals, companies, ships, jobs, reviews and the rest — with SMALLINT lookups and UUID v7 keys.

    Modeled the maritime domain into 348 normalized tables across 34 PostgreSQL schemas, with SMALLINT lookups, UUID v7 keys and one naming convention.

  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. Built infrastructure that still runs years later

    Planned and implemented new infrastructure functionality for internal and external systems, building solutions durable enough to still run years later with minimal change.

    Planned and built infrastructure for internal and external systems durable enough to still run years later with minimal change.

  14. Built the entire core infrastructure from scratch

    As one of the first hires, designed and built the entire core infrastructure and supporting processes from scratch for a green‑energy SaaS startup, laying the foundation for rapid growth.

    As one of the first hires, designed and built a green-energy SaaS startup's entire core infrastructure from scratch, enabling rapid growth.

  15. Public services on a small server

    Hosted the company’s public services on a single‑core 512 MB host — a git forge, a web server for seven domains, Tor, two alternative‑protocol servers and intrusion banning — treating 464 MB of usable memory as the design constraint; backup automation is a separate implementation.

    The recorded public-service setup ran on a machine that cost less per month than a lunch, and the design is better for the discipline rather than merely…

  16. Built a database‑driven CV generator

    Built a database‑driven CV, references, portfolio and cover‑letter generator in Python — 41 modules, 10,580 lines — rendering six output formats from one 23‑table SQLite source assembled by a 19‑step idempotent pipeline.

    Six formats, three languages and five themes come out of one database, and a corrected sentence is corrected once.

  17. Vendored a QR encoder in 522 lines

    Vendored a QR encoder — Reed‑Solomon over GF(256), fixed module layout, eight mask patterns — in 522 lines rather than take a third runtime dependency, and verified it by reading the finished matrix back with an independently written decoder.

    The runtime dependency count stayed at two, and the encoder is the only vendored component in the project.

  18. Built a native macOS client in Swift 6

    Built a native macOS messaging client in Swift 6 and SwiftUI — 11,141 lines across 53 files — over the C interface of a Rust core linked as a static archive from a pinned revision.

    A native client that starts as a Mac application, uses the platform's own materials and controls, and carries no embedded browser.

  19. A bounded event pipeline for a macOS app

    Bounded event buffers and logging after a recorded macOS incident with 41 MB per second growth and 111 GB of compressed pages on a 36 GB machine; a recorded full test run reduced core log lines from 610,996 to 1,411.

    The incident record documents a full test-run comparison: core log lines fell from 610,996 to 1,411, and captured log size from 63 MB to 388 KB.

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