Integration Embedded Engineer - Backfill
You'd join Embedded Platform, the team inside Samba's TV engineering org that turns Samba's ACR technology - audio, video, and TV signal capture - into something that actually runs on hardware.
That means writing to spec, working directly with OEM and SOC engineering teams, and validating what partners ship back before Samba can use any of it. This is about as upstream as it gets: if the signal doesn't get captured off the device, there's no TV data downstream, and TV data is the base layer Samba's whole business is built on. Beyond the core ACR work, the team also powers mobile apps that use TV viewership data and an edge AI feature that recognizes video game titles and shoppable items showing up on screen.
Q4 brings a new OEM project live - Sony's audio ACR work and the Titan OS integration are both active right now. Whether that runs in parallel with everything else already on the team's plate, or reshuffles who's working on what, depends on who's in this seat.
What you'd actually do
Write C++ applications that run inside Linux TV and Android TV environments, pulling video frame buffers and audio PCM data straight out of the hardware pipeline and turning them into the content-recognition fingerprints Samba's algorithms need.
Work hand-in-hand with TV engineering teams at partners like Sony, TCL, and Titan OS - hand them Samba's SDK and spec, then check what they build against it actually holds up.
Deploy and debug on real devices, not simulators: over network, USB, or serial cable, working directly at the embedded Linux OS level.
What you need to already be good at
High-level, hands-on C++ - this is an L3 seat, not one you grow into.
Embedded device development: you've deployed code from a laptop onto a real device over network, USB, or serial before, ideally from time at a TV OEM/ODM, a TV SOC company, or a mobile hardware company, as a systems engineer, not a driver- or firmware-only one.
Comfortable at the Linux command line
Video or audio frame processing - you know how to pull frame buffers and PCM audio out of a hardware video pipeline and do something with them.
A communicator, not just a coder. Code review carries real weight on this team, and you're expected to be able to explain what you're doing clearly enough that people who didn't build it can follow along - especially in a Taipei office culture where people can default to staying quiet rather than pushing back.
Real ownership. Nobody's handing you a finished roadmap or standing over your shoulder - you know what needs to get done and you put in the effort to get it done.
You need a senior person to lean on - there's no one else in this Taipei seat right now, and you're it.
You've worked at the driver or firmware level but never the system layer above it.
Code review is where you go quiet - this role runs on being able to walk people through your reasoning, not just your conclusion.
Not for you if
Why now
We're Series D, ~$100M raised, pre-IPO, growing 30% YoY, 18 years connecting TV and digital data. This specific seat opened because the person who held it, isn't returning after parental leave.
We hire asap - a new OEM integration project is ramping for Q4, and whether the team can run it alongside everything else already in flight depends on this hire.