Henrik Friedrichsen is a Technical Lead based in Hamburg with 13 years of software engineering experience and deep expertise in Linux/*BSD and open-source development. At MOIA he progressed from full-stack engineer to technical lead, shipping cloud-native services primarily in the AWS ecosystem using Kotlin, TypeScript and Python. He contributes to notable Rust open-source projects—implementing core features and robust error handling for Spotify clients—demonstrating a pragmatic focus on reliability, concurrency, and API integration. Comfortable across backend systems, GraphQL, serverless patterns and front-end React, he pairs hands-on coding with team leadership and delivery ownership. Fluent in German and experienced with an exchange semester in China, he brings both technical breadth and cross-cultural curiosity to engineering challenges.
12 years of coding experience
8 years of employment as a software developer
Bachelor of Science (B.Sc.), Computer Science, Bachelor of Science (B.Sc.), Computer Science at University of Hamburg
Language Program / Exchange Semester, Chinese Language, Language Program / Exchange Semester, Chinese Language at Fudan University
Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.
Role in this project:
Back-end Developer
Contributions:70 releases, 96 reviews, 582 commits in 4 years 2 months
Contributions summary:Henrik implemented core features and facilities for a cross-platform ncurses Spotify client. This involved adding web API integration, enabling track searching, and handling track playback. They also implemented thread-safe logging for a log window, and improved functionality by incorporating track queue management and applying a more user-friendly interface with features like showing album art and the currently playing track.
Contributions:10 commits, 3 PRs, 18 comments in 3 years 3 months
Contributions summary:Henrik primarily focused on improving the error handling and data structures within the Spotify API client library. They added detailed error information, fixed issues with data deserialization, and addressed potential problems with local tracks by adapting structures to handle null values. The user also corrected a typo and made the available markets field optional. These changes indicate a focus on code quality and robustness of the Spotify API integration.
apirustapi-sdksdkspotify
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.