Remote Ship Driver Jobs in Oregon (NOW HIRING)

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 run conferencing well enough to sell. By year-end there's a repeatable path from a board landing on a desk to a build QA can test, and you own it. Judge it by how long that path takes, and whether the thermal and acoustic targets hold.

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.

Who you are

• The player-coach. You've set 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 writing code. Either way, 60/40 sounds about right to you.

• At home where software meets hardware. Embedded Linux is your familiar ground: the kernel, the BSP, userspace, C and C++ running on the device itself. You've spent time close to the metal: wireless stacks, streaming protocols, drivers. You can reason about a bug whether it lives in the firmware, the network, or the silicon.

• You ship to hardware you can't reach. When it's firmware on a device mounted in someone's meeting room, a bad release doesn't just roll back with a hotfix. You've owned software that ships to the field, so staged rollouts, over-the-air updates, and testing on the devices themselves come naturally. "Works on my bench" isn't the finish line for you.

• You've turned new hardware into a product. Bare silicon arrives, and someone has to make it boot, talk to the network, manage its heat, and eventually stream. You've done that kind of bringup, or worked close enough to it to lead the people who do.

• You use AI as a daily tool. You write code with it, debug with it, prototype with it. You've formed your own view on where it speeds things up and where it gets in the way, and you help the people around you do the same.

Logistics
Location: Remote in Europe, or hybrid from our Copenhagen office.
Employment type: Full-time preferred. We're also open to a project-based contract scoped to delivering the native protocol implementations.