Most companies that do conferencing hand you one slice of it. The desktop app, or the media pipeline, or, maybe, the join flow. Everything else you pass over a wall to another team. Not in this case. One team owns the whole path across the Airtame platform: Airtame 3, Airtame Go, Virtual Airtame, and browser, desktop, and mobile apps that go with them. The bar remains at an effortless experience. Someone walks into a room, and starts sharing. No app to hunt for, no login to chase. The team is four engineers, and we're hiring their technical and people lead: someone who spends about 60% of time hands-on with the hardest problems, and the rest growing the engineers around them. <h3>About Airtame</h3> We're around 55 people, headquartered in Copenhagen, and you'd work from there or remotely from within the EU. We make the hardware and the software that runs on it, so a call you make about the streaming stack ends up in a product bolted to a wall in meeting rooms around the world. The team is small, works across disciplines, and reaches a global market from a small base. <h3>Year one outcomes</h3> Make joining a call one step that works. Today, getting an authenticated meeting started from a room takes too many turns: personal logins, manual entry, a different quirk on every platform. A year from now, starting a scheduled call on Teams, Zoom, Google Meet, or Webex should be something a room just does. Judge it by how often it works on the first try, and how rarely it reaches support. Take the friction out of screen sharing. The browser path loses first-time users: too many clicks, not enough signposting. You'll own getting a newcomer from a short code to their screen on the wall without a stumble, and getting Miracast and AirPlay stable enough to turn on by default. Make it behave the same everywhere. The experience varies between Airtame 3, Virtual Airtame, browser, desktop, and mobile today. By year-end, sharing and calling should feel like one product no matter which surface you're on, with real-time quality that holds up on whatever network the room happens to have. Lead the team. You'll run the 1:1s, set the technical bar, and support team members' growth. The measure is simple: a year in, the team runs on your leadership day to day. Push AI-assisted development further. The team already builds with AI daily. You'll lead the next step: sharper workflows, better tooling choices, new patterns that make the whole group faster. By year-end, the team's AI practices should be visibly ahead of where they started. <h3>Who you are</h3> <ul> <li>The player-coach. You've owned a team's technical direction: the architecture calls, the reviews where the hard problems get caught. And you want the people side too. Growing engineers, running 1:1s, hiring. You're not looking to trade one for the other. Maybe you've been a staff engineer or tech lead ready to own a team, or a manager who never stopped building. Either way, 60/40 sounds about right to you.</li> <li>Comfortable across the stack. Real-time media is second nature to you: WebRTC, streaming, the way audio and video behave over a network you don't control. You've gone deep somewhere, whether a media pipeline, native protocols, or a cross-platform client, and you can hold your own everywhere else, on browser, desktop, and mobile.</li> <li>You've made stubborn systems cooperate. Half this job is getting software to play nicely with platforms you don't own: Teams, Zoom, Meet, Webex, the operating system's own media APIs, each with its

Tech Lead, Video Conferencing & Screen Sharing

Job Description