Skip to content
EngineerSoftware
Menu
Design
English

Engineer / Software / Categories

Data Governance

  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. Made a geographical data pipeline 50x faster

    Recorded a 50x geographical data‑pipeline improvement in the founder’s Utiligize work through SQL and data‑model changes across PostgreSQL, MS SQL and Google Cloud BigQuery.

    The founder records a 50x geographical pipeline improvement at Utiligize through SQL and data-model work across PostgreSQL, MS SQL and BigQuery.

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

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

  5. Ran 100 PostgreSQL, MS SQL, BigQuery warehouses

    Architected, created, and managed 100 PostgreSQL, MS SQL, and Google BigQuery data warehouse databases with primarily GIS and time‑series data, optimizing performance and scalability.

    Architected and ran 100 PostgreSQL, MS SQL and BigQuery data-warehouse databases for GIS and time-series data — query times down 40–60%.

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

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

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

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

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

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