Skip to content
EngineerAdvisory
Menu
Design
English

Engineer / Advisory

Portfolio

Engineer ApS was registered in 2025. Most of the work shown here was delivered before that by our founder inside client teams; some has been delivered by the company itself, and some since in employment. The same hands and the same standards — we say which is which rather than blurring it.

  1. A consistent identity across channels

    Developed Engineer ApS brand identity across offline and online material, connecting the presentation with its engineering portfolio. The founder reports a 200x increase in brand recognition from this work.

    Developed Engineer ApS branding across offline and online material, linking a consistent visual identity to its engineering portfolio.

  2. Brand communication informed by audience response

    Used market research and audience feedback to shape Engineer ApS brand communication and outreach.

    Used market research and audience feedback to shape Engineer ApS brand communication, content and outreach across its channels.

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

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

  5. Led a GIS map application to 10x revenue growth

    Led the software development of a GIS map application, driving revenue growth by 10x and positioning the product as a primary data asset.

    Led development of a GIS map application that became a platform cornerstone, driving a 10x revenue increase via upsells and data licensing.

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

  7. Estimated 4,000 hours saved, team from 2 to 18

    Estimated 4,000 hours saved while mentoring a team that grew from 2 to 18 members, improving workflows and cross‑departmental coordination.

    Estimated 4,000 hours saved while mentoring a team that grew from 2 to 18, with improved workflows and cross-departmental coordination.

  8. Optimized forecasting and investment strategies

    Optimized forecasting and investment strategies for 11 electricity grid operators, driving operational efficiency through data‑driven GIS solutions.

    Optimised forecasting and investment strategy for 11 electricity grid operators with data-driven GIS — trustworthy, targeted planning.

  9. Presented 200 UI/UX improvements

    Presented 200 UI/UX improvements for the GIS map application, boosting revenue by 10x through enhanced software features.

    Delivered 200 UI/UX improvements to a GIS map application, contributing to a 10x rise in revenue — careful UX as a commercial driver.

  10. Managed 5,000 hours of map development

    Designed and managed 5,000 hours of map development, using Scrum and Jira for effective project management.

    Planned and ran 5,000 hours of map development with Scrum and Jira, keeping work visible and aligned to the roadmap.

  11. Wrote 50,000 words of software documentation

    Wrote 50,000 words of comprehensive software documentation utilizing Markdown in GitHub, Craft, and Confluence, thereby ensuring the retention of knowledge and the transparency of the process.

    Wrote 50,000 words of software documentation in GitHub, Craft and Confluence, making knowledge durable, transparent and auditable.

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

  13. Managed 30 successful GIS projects to delivery

    Managed the execution of 30 successful GIS projects, demonstrating leadership in delivering innovative solutions across the field.

    Delivered 30 successful GIS projects — a track record of consistent, innovative delivery that earned lasting client trust.

  14. Led company growth from 4 to 14 employees

    Led company growth from 4 to 14 employees by employing Agile methodologies and effective project management practices.

    Led company growth from 4 to 14 employees with Agile practices, scaling the team without losing quality or cohesion.

  15. Improved team communication and collaboration

    Improved team communication and collaboration by implementing Slack, Mattermost, 1Password, and Jira, saving 8,000 hours of labor.

    Saved ~8,000 hours by rolling out Slack, Mattermost, 1Password and Jira, turning chased information and redone work into real delivery.

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

  17. Guided company projects through development

    Guided the execution of numerous company projects, offering expert support in the software development phases.

    Guided execution of many company projects with expert support through the hardest software-development phases, steadying delivery.

  18. Overhauled internal processes, saving 8,000 hours

    Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.

    Overhauled internal processes to save ~8,000 hours, improving software architecture, systems and scheduling efficiency.

  19. Established a Technical Support department

    Established a Technical Support department, servicing over 10,000 clients with IT support and troubleshooting solutions, tracking client requests in a CRM.

    Established a Technical Support department serving 10,000+ clients, turning support from reactive fixes into a scalable company strength.

  20. Streamlined CI/CD processes, saving 4,000 hours

    Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines.

    Streamlined CI/CD to save ~4,000 hours, making releases faster and more reliable so the team could ship with confidence.

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

  22. Saved 150 hours a month across 30 projects

    Enhanced project efficiency, saving 150 hours per month across 30 projects by optimizing workflows and resource management.

    Saved ~150 hours per month across 30 projects by optimising workflows and resource management — a recurring, portfolio-wide gain.

  23. Managed a team delivering IT support

    Managed a team delivering IT support, data recovery, and hardware repair services to over 1,000 clients, ensuring high‑quality service.

    Led a team delivering IT support, data recovery and hardware repair to 1,000+ clients, building a reputation for reliable service.

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

  25. Authored 578 go‑task automation targets

    Authored 578 go‑task automation targets spanning native, Docker and HTTPS dev modes, linting, testing, database and deployment.

    Authored 578 go-task automation targets across native, Docker and HTTPS modes — linting, testing, database and deployment behind one toolchain.

  26. Designed the product's UI and UX end to end

    Designed the product's UI and UX end to end — directory grids, dual card/table views, live requirement validators and breadcrumb navigation.

    Designed the product's UI/UX end to end — directory grids, card/table views, live validators and breadcrumbs — for dense maritime data.

  27. Set a zero‑warnings bar across six languages

    Set a zero‑warnings quality bar across six languages — Go, TypeScript, SQL, Python, Shell and Markdown — enforced by pre‑commit hooks.

    Set a zero-warnings quality bar across Go, TypeScript, SQL, Python, Shell and Markdown, enforced by pre-commit hooks.

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

  29. Delivered analysis and regular progress reports

    Delivered analysis and regular progress reports to the CEO, translating engineering KPIs and delivery status into decisions.

    Delivered analysis and regular progress reports to the CEO, translating engineering metrics and delivery status into confident decisions.

  30. Designed a time‑management and reporting system

    Designed a time‑management and reporting system that remained in production use for years without significant modification.

    Designed a time-management and reporting system that stayed in production for years without significant modification.

  31. Automated team collaboration

    Automated team collaboration, password management, task and time management, and built a semi‑automatic project‑showcase system, raising team productivity.

    Automated collaboration, password, task and time management and built a semi-automatic project-showcase system, raising team productivity.

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

  33. Built a 268‑check guard engine for the repo

    Built the repository's guard engine — 268 registered commit checks, 277 lint rules and 15 custom ESLint rules — plus 146 tests of the guards themselves, so the build holds the standard, not review.

    Built a guard engine of 268 registered commit checks, 277 lint rules and 15 custom ESLint rules, with 146 tests of the guards themselves.

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

  35. Built the operator back‑office for the platform

    Built the operator back‑office — around 40 admin routes and 128 components covering claims, moderation, feature flags, cache and diagnostics — so the platform can be run without database access.

    Built the operator back-office — around 40 admin routes and 128 components for claims, moderation, feature flags, cache and diagnostics.

  36. Built company ownership claims and adjudication

    Built company ownership claims end to end — a user claims a company, an administrator adjudicates, and an approval rewrites the authorization graph that decides who is allowed to edit what.

    Built company ownership claims end to end: a user claims, an administrator adjudicates, and approval rewrites the authorization graph.

  37. Ran a continuous security scanning programme

    Established a continuous security programme — code scanning, DAST, dependency and vulnerability checks, SBOM generation, secret scanning and SHA‑pinned actions — alongside 21 written security audits.

    Established a continuous security programme — code scanning, DAST, dependency checks, SBOM, secret scanning and pinned actions — plus 21 audits.

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

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

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

  41. Built 7 read‑only host reporting roles

    Built seven read‑only reporting roles that render a live host to Markdown — facts, access, git, metrics, traffic, security and provider inventory — under a rule that no number is printed the run did not measure.

    The estate can be described from the repository on demand, and the reports have found real things: the two dead security controls, an undeclared listening…

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

  43. Built a 22‑linter commit gate

    Built a commit gate of 22 one‑line linters plus five that earn a paragraph, with no warning tier and no inline suppressions permitted, covering HTML, CSS, JavaScript, Python, YAML, Markdown, shell, links, spelling, secrets and typography.

    Mechanical objections are made by a machine before a commit exists, and the gate is the only reviewer this project has.

  44. A safety net that no longer costs half an hour

    Cut the site's browser‑driven quality gate from 1,636 seconds to 615 by scheduling its checks longest‑first through a worker pool bounded to four lanes, after measuring that alphabetical order cost 320 seconds against 224.

    The gate went from 1,636 seconds to 615, while the checks got broader rather than thinner — the serial cost went up and the wall clock came down.

  45. Ran development as 51 written initiatives

    Ran the site's development as 51 written initiatives across 54 plan documents, each carrying its open boxes, its measurements and the decisions it declined — including six of eight agent‑readiness findings refused with the reason recorded.

    Fifty-one decisions with their reasoning attached, roughly three-quarters closed, and the declined ones are as retrievable as the accepted ones.

  46. Put the documentation under its own linter

    Put the documentation under its own linter — a per‑file line budget that only ratchets down, an index requirement and a real‑path check — which found six of nine plans marked done while carrying unchecked boxes, and fourteen commit‑gating tasks named in no document.

    Twenty-six documents totalling about 2,666 effective lines, each under a budget that cannot grow, with every path and symbol they name checked against the…

  47. Linted the 10,242‑line quality gate itself

    Brought 10,242 lines of quality‑gate JavaScript under a formatter and a linter after establishing it was the largest body of code in the repository and the only one nothing read, fixing 13 findings and suppressing none.

    The largest and most load-bearing code in the repository is now formatted, linted and type-checked, with thirteen findings fixed and zero suppressions.

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

  49. Passed 106 of 106 PDF/UA‑1 profile checks

    Recorded PDF/UA‑1 validation across nine documents with 106 of 106 configured accessibility‑profile checks passing, while the archival variant failed one of 146 rules.

    All configured accessibility-profile checks passed. The archival claim is stated honestly as a near-miss with the specific gap named.

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

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

  52. Found the hooks and the gate disagreeing

    Found the commit hooks and the quality gate running different checks while a document promised they were the same, by comparing the two lists in a test — the five that only ever ran by hand were the ones reading the CV prose.

    The hook and the gate provably run the same checks, and the prose checks now run on every commit.

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

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

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

  56. Took the test suite to 8.9 seconds

    Took the test suite from six tests over a sixty‑second limit to 135 passing in 8.9 seconds by profiling the main thread and removing the two calls it sat inside for 3,989 samples out of 4,017.

    The suite went from six tests over sixty seconds — 74 seconds of wall clock — to 135 tests passing in 8.9, which puts it inside the window where it runs on…

  57. Rewrote error messages to stop blaming users

    Rewrote the application's error messages against a written tone standard after a refused sign‑in blamed the user for mistyping when the provider actually required an app‑specific password, and covered it with a test that names the provider.

    The error surface follows a stated standard and the case that prompted it is covered by a test that fails on the old text.

  58. Held 4 repositories to one history standard

    Held four repositories to one history standard — conventional, emoji‑free, no attribution trailers, enforced by a commit‑message hook — alongside 48 instruction documents that govern how the work is done.

    Four repositories share one history format and one instruction structure, both enforced by hooks rather than by discipline.

  59. Made six collectors state what they skipped

    Made six reporting collectors state the part of their input they never read — files that stayed shut, probes not installed, journal lines unrecognised — and fitted thresholds to 116 measured samples, after establishing that a blind collection and a healthy host render the same page.

    A page of this platform's numbers now carries its own blind spots beside its findings. None of the self-measurement is a gate, and that is stated rather than…

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