Engineering minds meet
clean code and clear data.
Flytkjær Consult is an independent practice bridging software, data, and mechanical engineering — helping teams build the right tool, understand their data, and solve the technical problem in front of them.
Three disciplines, one practical toolkit
Most problems don't respect category boundaries. Neither does this practice.
Programming
Custom scripts, tools, and applications built around how you actually work — automation, internal tools, and full web apps.
Data Analysis
Turning raw, messy data into clear, decision-ready insight — analysis, modeling, and dashboards that hold up under scrutiny.
Mechanical Engineering
Design, simulation, and hands-on technical problem-solving grounded in mechanical engineering fundamentals.
MSc mechanical engineer, self-taught coder
Grounded in offshore energy engineering, built up through data-driven thesis work, and put into practice writing Python tools ever since.
-
Global S&OP Process Optimization & Digitalization Expert · ECCO 2026 – Present
Optimizing and digitalizing global sales & operations planning processes.
-
Engineer · COWI 2025 – 2026
Offshore wind turbine foundation design and integrated load analysis, alongside building internal software tools.
-
Graduate Consultant · COWI 2022 – 2025
Wind Energy and Renewables Management department — three years across engineering and consulting on renewable energy projects.
-
MSc, Mechanical Engineering · Aarhus University 2020 – 2022
Specialised in renewable energy. Thesis: modeled interannual weather variation and extreme weather impact across a 30-country European energy system using PyPSA (Python for Power System Analysis), then analyzed the results with statistical models and machine learning.
-
Student Worker / Intern · Teknologisk Institut 2018 – 2021
Mechanical engineering work centered on additive manufacturing (3D printing) at Denmark's Center for Industrial 3D Printing.
-
Braking System Head Engineer · ASE Racing 2017 – 2018
Designed and developed the braking system for the Formula Student race car during the BSc in Mechanical Engineering.
Cross-disciplinary by design
A mechanical engineering background plus hands-on software and data work means fewer handoffs and fewer things lost in translation.
-
01
Start from the real problem
Every engagement starts with understanding what's actually broken or missing — not which tool to reach for first.
-
02
Work across the stack
From physical systems to the data they produce to the software that runs on top — one point of contact, not three specialists.
-
03
Ship something that lasts
Practical, well-documented outcomes over impressive but fragile ones — built to be handed off and maintained.
Have a problem that crosses disciplines?
Let's talk about what you're building, analyzing, or trying to fix.
xxxx@gmail.com