data engineer
problem solver who ended up in data engineering because pipelines are just puzzles with consequences. naturally curious, chronically tinkering – the type to rebuild something three times until it feels right. takes full ownership of what i build because half-done solutions are worse than no solution. drawn to data work because the feedback is honest: it works or it doesn't, no arguments.
treat code like craftsmanship – every pipeline should reflect care and intent. want to work with people who share that ambition, who see their work as more than just tickets to close. focused on enabling both stakeholders and peers to excel, because good solutions matter more when everyone can build on them.
volvo cars
knowit solutions cocreate
chalmers university of technology
the formulas are long gone, but the concepts stuck. what actually mattered wasn't memorizing how to calculate entropy or sizing bolts – it was learning how to break down problems logically and teach myself whatever i needed to know. turns out that's way more useful than any specific equation.
focus: mathematics, physics and programming