Skip to content
EngineerData
Menu
Design
English

Engineer / Data / Services

Trusting the numbers

Rules and checks that catch bad data on the way in, and a clear answer to who owns which figure and where it came from.

  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. Resolved 1,000 issues in geographical data

    Resolved 1,000 issues in geographical data and time‑series data, using GDAL, ArcGIS, PostGIS, Mapbox, QGIS, SQL (PL/pgSQL, Transact‑SQL), Bash, ensuring high‑quality big data processing.

    Resolved 1,000+ issues in geographic and time-series big data with GDAL, PostGIS, ArcGIS, Mapbox, QGIS and SQL — 35% faster queries.

  3. Released 500 electricity and GIS data reports

    Released 500 electricity and GIS data analysis reports, utilizing deep research and troubleshooting to ensure accurate geographic and time series big data insights.

    Published 500 electricity and GIS data-analysis reports — a cross-department reference for load balancing, efficiency and anomaly detection.

  4. Gathered and analyzed business requirements

    Gathered and analyzed business requirements to translate into actionable features and user stories aligned with data governance standards.

    Turned business requirements into clear features and user stories aligned with data-governance standards, cutting ambiguity and rework.

  5. Engineered 600 PL/pgSQL ETL/ELT pipelines

    Engineered 600 PL/pgSQL‑based ETL/ELT pipelines to streamline complex data processing workflows across multiple PostgreSQL development and production environments.

    Engineered a recorded 600 PL/pgSQL ETL/ELT pipelines across PostgreSQL development and production, including incremental loading and logging.

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

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

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

  9. Built first‑party analytics inside PostgreSQL

    Built first‑party product analytics in PostgreSQL — 47 functions over partitioned event tables that prune themselves — pseudonymised behind a rotating salt and gated on the visitor's consent.

    Built first-party product analytics in PostgreSQL — 47 functions over self-pruning partitioned tables — pseudonymised and gated on consent.

  10. Wrote a scope rule after a credential leak

    Wrote a scope rule into the repository after a restructure carried another company's inventory, firewall allowances and prose into it — and kept the quarantined residue under the secret scanner rather than excluding it.

    The scope boundary is a written rule with a stated test, the residue is visible rather than buried, and the specific shape of credential that got through now…

  11. Replaced 963 metadata blocks with one graph

    Replaced 963 anonymous structured‑data blocks that restated the company 1,671 times with one linked graph of 16 types minted from stable origin identifiers.

    One graph with stable identity replaces 963 anonymous restatements, and the pages carry less rather than more.

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

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

  14. Built a cross‑language figure check

    Built a cross‑language content check that fails when a translation drops a figure the English states, and when a language uses notation it does not use — finding two Danish descriptions missing a metric and sixteen Ukrainian spans quoting in the English style.

    Eighteen real defects closed and the class closed with them, since every future translation is compared to its English source before it can be committed.

  15. Know the licence of everything you ship

    Audited 644 Rust crates for licence compatibility on every build, and proved the check fires by rewriting one crate's licence and by moving the pinned core revision without regenerating.

    The distribution position is checked on every build, and the check is known to work because it was made to fail rather than because it has never spoken.

  16. Measured 13 addresses with no tracking

    Measured thirteen addresses from the web server's own access log alone — no cookie, no tracker and no third‑party service — masking the client network as each line is written, and folding the result into a permanent archive of 21 daily counts and 20 monthly facets.

    Thirteen addresses are measured this way, and the site ships no cookie, no tracker and no third-party request, so there is nothing to consent to and nothing…

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