Engineer / Data
Cases
Selected engineering work in plain language, with delivery context and links to the full record behind each case.
Engineer ApS was registered in 2025. These cases include company projects and work our founder carried out in client teams and as an employee, dating back to 2003. Each case explains the role and working arrangement.
One infrastructure plan for 14 departments
Designed a shared framework for a research institute that 14 departments could run on together, each keeping the things that make it different.
Read the case study30 days of electricity data in 180 ms
Implemented Python, JQ and SQL variants for hourly electricity aggregation. In the recorded benchmark, Python processed one dataset covering 30 days in 180 ms.
Read the case studyA maritime platform with clear system boundaries
The founder’s work for NextMariner separates a Next.js interface, a Go API and PostgreSQL business rules. Each layer has a defined responsibility.
Read the case studyA mapping product, carried end to end
Infrastructure, data processing and the map application itself, built and kept running for two years.
Read the case studyTime-ordered keys for a growing data model
Configured UUID v7 as the platform’s identifier convention to keep new keys ordered by time.
Read the case studyBrand communication informed by audience response
Used market research and audience feedback to shape Engineer ApS content and outreach.
Read the case studyKnow the licence of everything you ship
Put a licence check on 644 third-party components that runs on every build, and proved it fires by breaking it on purpose.
Read the case study
These cases introduce selected engineering work in plain language. Each links to the full record: the situation, the contribution and the result. Use the examples to judge relevance to your project, then ask about the scope and supporting evidence.