From the outside, video conferencing looks solved. Anyone who's worked on it knows better. At a big company, that work gets split a hundred ways, and you'd own a slice of it. At a company our size, it's one person's call, and it would be yours.
We're around 55 people, headquartered in Copenhagen, and you'd work from there or remotely from within the EU. We build the hardware and the software that runs on it, so the conferencing you'd work on runs on the device in the meeting room.
Year one outcomes
• Put the telemetry in. Conferencing quality is hard to see without the right instrumentation, so you'd build it: latency, quality, and resource use on the device, visible and tracked. Once it's there, a bad call comes with the data to explain it.
• Move the metrics. Better audio and video, lower latency, lighter load on the device. Agree on the handful that matter most, and show clear movement within the year.
• Take on the problems that need a specialist. Some conferencing issues need someone who's solved them before. You'd own those from diagnosis to fix, and the recurring ones stop recurring.
• Raise the team's game. Share what you know so the team's calls on real-time media get sharper, and flag the wrong turns before they cost months. The bar you set becomes the team's default.
Who You Are
•
You've lived in real-time media. Years of it: WebRTC, codecs, the media server and its tricks, why a call holds together on one network and falls apart on another. You know the caveats because you've hit them. And the brand names sit on the same ideas underneath, so where you learned it matters less to us than that you did.
•
You reach for data. When something's off, you measure before you theorise. You've built or leaned on telemetry to find what's going on in a messy…