Michiel De Backker is a hands-on CTO and former co-creator of the Pion WebRTC project with eight years of experience building real-time, low-level networking systems and product-led consumer experiences. Based in Belgium, he blends deep protocol expertise—DTLS, SRTP, STUN/TURN and custom media engines implemented in Go—with product ownership skills from leading Twintag’s frictionless physical-to-digital communication platform. He’s comfortable moving between core backend engineering (contributing to widely used open-source repos like pion/webrtc and pion/turn) and shaping product strategy that drives adoption. Notably, Michiel has a track record of implementing cryptographic handshakes, codec management and WASM-enabled media flows, showing both security-minded engineering and modern web integration.
8 years of coding experience
1 year of employment as a software developer
Master of Science Industrial Sciences: Electronics-ICT (specialization ICT), Master of Science Industrial Sciences: Electronics-ICT (specialization ICT) at Thomas More University of Applied Sciences
Bachelor of Science Industrial Sciences: Electronics-ICT, Bachelor of Science Industrial Sciences: Electronics-ICT at Katholieke Hogeschool Kempen
TSO Industrial Sciences Industriële wetenschappen, TSO Industrial Sciences Industriële wetenschappen at Vrije Technische Scholen van Turnhout
Contributions:39 commits, 15 PRs, 42 pushes in 1 year 8 months
Contributions summary:Michiel implemented core functionality for a DTLS 1.2 server/client implementation in Go. They focused on the internal workings of the DTLS protocol, including handshake messages, encryption, and decryption. Key contributions include adding support for server key exchange signatures, updating encryption to use the correct IVs, and improving client and server handshake handling.
Contributions:2 reviews, 94 commits, 109 PRs in 9 months
Contributions summary:Michiel primarily focused on implementing core features within the WebRTC API implemented in Go. Their contributions included adding support for a custom media engine, allowing for the registration and management of different codecs. They also modified existing files like `rtcpeerconnection.go`, `signaling.go`, and `media.go`, suggesting they were involved in integrating the new media engine and codec handling throughout the project's architecture and functionality. Further adjustments to error handling and SDP generation, with the addition of a data channel API, indicate an effort towards building out the core functionality of the WebRTC implementation.
webrtcpure-gogovideowebrtc-api
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.