Frederik Wallner is a versatile engineering leader and VP of Engineering based in Stockholm with 13 years of professional experience and a 7+ year focus on mobile apps and systems. He has progressed from founding web projects to hands-on mobile development and product leadership roles, most recently steering engineering at Done. Frederik blends product sensibility from his Product Owner and Head of Mobile tenures with practical DevOps and QA contributions in open-source projects—improving CI/CD for the well-known danger/danger repo and enhancing XCTestHTMLReport’s test artifacts. Comfortable shipping both iOS features and robust infrastructure, he’s known for pragmatic problem solving, test-driven improvements, and an appetite for learning new tooling. Colleagues would describe him as a systems-minded leader who still dives into code to improve reliability and developer experience.
12 years of coding experience
15 years of employment as a software developer
Web design, Photography, TV-production, Radio channel production, Web design, Photography, TV-production, Radio channel production at Täby Mediagymnasium
System development, System development at Nackademin
🚫 Stop saying "you forgot to …" in code review (in Ruby)
Role in this project:
DevOps Engineer
Contributions:9 commits, 3 PRs, 28 comments in 1 year 6 months
Contributions summary:Frederik primarily focused on enhancing the CI/CD pipeline and supporting infrastructure for the `danger/danger` repository. They implemented Jenkins pipeline support, including configuration for GitLab and Bitbucket, and added tests for the Jenkins CI source. The user also addressed a code vulnerability in the request source for GitHub and improved code maintainability through test refactoring. Their contributions suggest a focus on ensuring smooth and reliable integration and deployment processes.
Contributions:5 commits, 3 PRs, 4 comments in 14 days
Contributions summary:Frederik's contributions primarily focused on enhancing the XCTestHTMLReport project by improving the attachment handling and reporting functionality. They introduced the ability to include attachment names in the HTML reports and refined how attachments are displayed. The user modified both the Swift code, specifically within the `Attachment` model, and the HTML templates to accommodate these changes. Furthermore, they made improvements to the code's robustness by adding missing returns and refactoring with guard statements.
xctestreportunithtml-reportswift
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.