Skip to content
EngineerData
Menu
Design
English

Engineer / Data / Categories

PostgreSQL

  1. 30 days of electricity data in 180 ms

    Engineered hourly electricity‑consumption aggregation variants in Python, SQL and Bash + Jq, with the Python benchmark processing one 30‑day JSONL dataset in 180ms.

    Built and benchmarked electricity-consumption aggregation in Python, SQL and Bash + Jq; Python processed a 30-day JSONL dataset in 180 ms.

  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. Improved GIS map performance 10x on PostgreSQL

    Improved geographical map application performance by 10x through strategic database transition from MSSQL to PostgreSQL, including the data cutover, optimizing processing and data security.

    Improved a GIS map application 10x by migrating MSSQL to PostgreSQL — spatial queries dropped from 2.5s to under 250ms.

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

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

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

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

  8. Ran 10 PostgreSQL and MS SQL servers on Ubuntu

    Designed, deployed, and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS, ensuring optimal server performance and reliability.

    Designed and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS at 99.9% uptime, with 30% faster queries via tuning.

  9. Accelerated PostgreSQL performance by 10x

    Accelerated PostgreSQL performance by 10x via strategic indexing, partitioning, and query optimization, enhancing database efficiency for user, tenant, geospatial, and time‑series electrical data.

    Accelerated PostgreSQL 10x via indexing, partitioning and query tuning for user, tenant, geospatial and time-series data — resource use down 40%.

  10. Automated 100 critical data backups using Barman

    Automated 100 critical data backups using Barman, Google Cloud, Bash, and Python, ensuring data integrity across databases.

    Automated 100 critical database backups with Barman, Google Cloud, Bash and Python — turning data recoverability into a tested fact.

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

  12. Automated data processing in Python and PL/pgSQL

    Automated data processing tasks using Shell scripting, PL/pgSQL, Python, and Transact‑SQL, increasing productivity and efficiency.

    Automated data-processing tasks with Shell, PL/pgSQL, Python and Transact-SQL, lifting productivity and ending small recurring errors.

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

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

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

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

  17. Time‑ordered keys for a growing data model

    Adopted UUID v7 time‑ordered identifiers (PostgreSQL 18) as entity keys to reduce B‑tree index fragmentation and speed up queries.

    Adopted UUID v7 time-ordered keys in PostgreSQL 18, aiming to reduce B-tree fragmentation and improve inserts and range queries for entity tables.

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

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

  20. Implemented backups and disaster recovery as code

    Configured database backup retention as infrastructure‑as‑code, then audited the recovery position and documented the restore procedure — naming the remaining gaps rather than leaving them to be found during an incident.

    Configured database backup retention as infrastructure-as-code, audited the recovery position and documented the restore procedure and remaining gaps.

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

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

  23. 1,022 migrations behind a schema drift gate

    Kept the schema honest across 1,022 migrations with a CI gate that builds the database both ways — a fresh install, and an install plus every migration — and fails when the two disagree.

    Kept the schema honest across 1,022 migrations with a CI gate that builds the database both ways and fails when the two disagree.

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

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

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

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