At a big company, the platform layer is a hundred engineers, and you own a slice of it. A driver. A subsystem. A corner of the release pipeline. You go deep, but you rarely get to hold the whole thing. With us you will. One team owns the entire layer: the operating system and firmware on every Airtame, the streaming stack underneath it, the releases that reach devices in the field, and the work of turning new hardware into a shipping product.
The role is roughly 60% hands-on the hardest problems and 40% growing the engineers who work on them.
About Airtame
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 change you make to the firmware ships to every Airtame in the field. The team is cross-functional and spread across Europe, and it reaches a global market from a small base.
Year one outcomes
Take AirPlay and Miracast from beta to default. They're in beta today. A year from now they should be solid enough to ship on by default across the Airtame product line, so customers get them without opting in and never have to think about which protocol they're using. Judge it by connection success rates on the fleet, and by how many customers rely on them day to day.
Make firmware releases boring. The best release is the one nobody has to think about: a predictable cadence, an automated quality bar, and shipping to the whole fleet as routine. A year from now, cutting a release should be a low-drama process the team trusts, and that should let you ship improvements more often. Judge it by release frequency, and by the confidence behind each one.
Turn the next board into a shipping Airtame. New silicon has to boot, hold a network, manage its heat, and…