Mashgin powers the world's best checkout experience for over 40 million users. Customers just place their items on our kiosks and our AI rings up their entire order in less than a second. With Mashgin, lines are now optional.

Mashgin's technology powers over 1 billion transactions at your favorite locations, including over half of all US professional sports teams, 4,000 convenience stores, major airports, universities, and more.

We’re not just building cutting-edge AI—we’re creating real-world impact and unforgettable experiences. Backed by a well-funded Series B, we’re also one of the rare AI startups that’s already profitable.

Our secret? A culture of extreme ownership, autonomy, and customer obsession. At Mashgin, we are building something extraordinary by challenging conventional wisdom. We’ve thrown out the old rules to focus on what truly matters: creating a kickass product that makes people say, 'Wow'. We don’t care about short-term wins; we build systems that stand the test of time. If you thrive in a culture of excellence without compromise and want to see your work have an immediate, remarkable impact, you’re in the right place.

We're looking for an engineer to join a new team building features on top of in-store camera feeds (not the kiosk's own sensors, but the store's security/overhead cameras). Today that footage mostly just sits on-site, unused. This team will build the pipeline to get value out of it, whether that means analyzing it where it lives or pulling it into the cloud, across thousands of stores each with its own network constraints and camera hardware.

You'll be an early member of the team. That means writing the capture/ingestion code, dealing with real codec and streaming decisions (what to encode in, how to transport and play back efficiently over constrained store networks), figuring out what stays on-site versus what moves to the cloud, and getting the first features hooked up. This has a lot in common with building a video player/streaming stack. We need someone who's comfortable with some ambiguity: requirements that aren't fully defined yet, tooling you may need to build yourself, and a willingness to just build the thing rather than wait for a full spec. This is a hands-on coding role first, an infrastructure-design role second.

We maintain a flat, high-impact engineering culture where every engineer who joins our team carries the title of Member of Technical Staff.