Skip to content
Engineer
Menu
Design
English

Engineer / Services

The engine behind your app or website

The part users never see: where the data lives, what the rules are, and how other systems are allowed to talk to it.

  1. Designed and ran 6 ETL/ELT pipelines

    Designed, implemented, and administered 6 ETL/ELT pipelines, utilizing Google BigQuery, MSSQL, PostgreSQL, Shell scripting, PL/pgSQL, and Transact‑SQL, integrating data for efficient Python API processing.

    Designed and ran 6 ETL/ELT pipelines (BigQuery, MSSQL, PostgreSQL), cutting a 3-hour manual job to under 20 minutes with daily syncs.

  2. Delivered 8 Power BI projects with manuals

    Delivered 8 Power BI projects with comprehensive manuals, integrating Microsoft Power BI tools with NodeJS API and Python FastAPI for effective data analytics and visualization.

    Delivered 8 Power BI analytics projects (Node.js API, Python FastAPI) with full manuals, improving report generation efficiency by 60%.

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

  5. Developed a Data Analytics reporting system

    Developed a Data Analytics reporting system, increasing quarterly software revenue by 400% through Python‑based PDF reports.

    Built a Python data-analytics reporting system that raised quarterly software revenue by 400% with clear, timely PDF reports.

  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. Generated the API contract from the database out

    Generated the API contract outward from the database — OpenAPI, a 44,076‑line typed TypeScript client, 61 mock handlers and the limits the UI enforces — with a guard at every hop that fails on drift.

    Generated the API contract from the database outward — OpenAPI, a typed TypeScript client, mock handlers and UI limits — with a guard at every hop.

  11. Built email with failover and delivery logging

    Built email as a platform capability — three providers with failover, delivery webhooks, send and delivery logging, templating and campaigns — behind a startup check that will not boot without one.

    Built email as a platform capability: three providers with failover, delivery webhooks, send and delivery logging, templating and campaign broadcasts.

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

  13. Implemented a catalogue‑driven deep‑merge

    Implemented a catalogue‑driven deep‑merge for stored JSON preferences, preventing missing‑key crashes as the schema evolves.

    Implemented a catalogue-driven deep-merge for stored JSON preferences, preventing missing-key crashes as the schema evolves.

  14. Hardened the application with nonce‑based CSP

    Hardened the application with nonce‑based CSP, HSTS, SameSite cookies, least‑privilege database roles and server‑side entitlement re‑checks.

    Hardened the app with nonce-based CSP, HSTS, SameSite cookies, least-privilege database roles and server-side entitlement re-checks.

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

  16. Built and maintained Django apps for IPTV

    Developed and maintained Django web applications for the IPTV platform, shipping new features and improving performance and stability.

    Developed and maintained Django web applications for an IPTV platform, shipping features while improving performance and stability.

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

  18. Built Stripe and in‑app purchase entitlements

    Built the payments and entitlements layer — Stripe alongside Apple and Google in‑app purchase — gating the directory, search and export through an 11‑table access model checked on the server.

    Built the payments and entitlements layer — Stripe with Apple and Google in-app purchase — gating directory, search and export from an access model.

  19. Moved slow work onto a River job queue

    Moved slow work off the request path onto a River job queue — 15 worker modules, 8 scheduled tasks and 20 pg_cron jobs — so a request returns while the work behind it carries on.

    Moved slow work off the request path onto a River job queue: 15 worker modules, 8 scheduled tasks and 20 pg_cron maintenance jobs.

  20. Built first‑party error monitoring and tracing

    Built first‑party error monitoring and OpenTelemetry tracing rather than buying them — payload sanitising, spike and regression detection, symbolication and a synthetic heartbeat — behind 11 operator views.

    Built first-party error monitoring and OpenTelemetry tracing — sanitising, spike detection, symbolication and a heartbeat — behind 11 operator views.

  21. Built fail‑closed rate limiting and anti‑abuse

    Built fail‑closed abuse controls — 22 Redis‑backed rate limiters, Cloudflare Turnstile, request idempotency and an origin lock — so the platform sheds bots and floods instead of trusting its callers.

    Built fail-closed abuse controls: 22 Redis-backed rate limiters, Cloudflare Turnstile, request idempotency and an origin lock on the front door.

  22. Built a loyalty wallet, leagues and badges

    Built the loyalty and reputation system — 67 functions over a 31‑table ledger, with leagues, badges and a redemption shop — taking a row lock on the balance to close the double‑spend window.

    Built the loyalty and reputation system — 67 functions over a 31-table ledger, leagues, badges and a shop — with row locking on the balance.

  23. Built the social layer: posts, feed and groups

    Built the platform's social layer — posts, feed, groups, mentions, a follower graph and an occasions digest — on the same function‑first data layer as the rest of the product.

    Built the platform's social layer — posts, feed, groups, mentions, a follower graph and an occasions digest — on the same function-first data layer.

  24. Built the hiring and seafarer career workspaces

    Built hiring and seafarer career workspaces; the recorded implementation snapshot contains 151 stored functions across 48 tables for vacancies, applications, certificates, rank progression and sea time.

    Built hiring and seafarer career workspaces, with 151 functions across 48 tables in the recorded implementation snapshot.

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

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

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

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

  29. Moved every string into a content tree

    Moved every user‑facing string out of Python into a content tree of 874 files across three languages, after finding dead translations nobody could see were dead and a check silently grading a third of the achievements.

    The prose is now editable without touching code and comparable across languages by counting. The cost is that adding a language is now unambiguous rather than…

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

  31. Wrote a parser verifying every FFI call

    Wrote a parser that reads the real 7,308‑line C header and verifies every call site, every enum constant and that every pointer‑owning class is final, after a hand‑written placeholder header let calls to three removed functions compile, link and crash.

    The class of defect that produced the original crash cannot recur, because a stale reference is now a build failure rather than a runtime one.

  32. Reached the unused half of the core

    Reached the half of the messaging core the application had never used — backup transfer, disappearing messages, message editing and resending, verified invitations, proxies and encryption policy — driving every test against the real library with no mocks.

    The previously unreached half of the core is driven by tests against the real library, and the wrapper carries the highest floor in the project.

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