Product Engineer, Full Stack

Product Engineer, Full Stack | SageOxPRODUCTBLOGJOIN OUR TEAMDOCSABOUTGet Started Back to Join Our Team Location Seattle , WA

Employment Type

Full-time

Compensation

Competitive salary + equity# Product Engineer, Full Stack Sage Ox  is a well-funded, early-stage startup at the frontier of how AI is shaping the world. At Sage Ox, we believe the future of work is deeply human and collaborative. As agents take on execution, coordination, and routine work, people gain space for what only humans do well: creativity, judgment, relationships, the work of imagining, deciding, and creating together.

Humans become not only more productive individually, but better at working with each other, leaning on their AI coworkers to carry out execution and raise the quality of how they collaborate.

We're looking for strategic hires - fearless, creative, independent thinkers - that will shape the future of the company, and how work is done in the modern world.

There's no trail yet. Pioneering and breaking trails is one of our company's core values. You're one of the first ten people cutting it.## What You'll Actually Ship Everyone touches all layers. That's not a slogan. It's the actual job. Full-stack at Sage Ox really means the whole stack: hardware firmware sitting in the room, mobile/desktop apps, cloud services, Temporal workflows, web frontend, real-time streaming, CLI, and file systems.

At the speed at which we're moving, we believe being in person and collaborating closely is essential. This is an in-person, Seattle-based role. We strongly believe that magic happens when people are in the flow together working on ambitious problems.

Pick a week at random and you might be:
* Researching and building out episodic and semantic memory systems that deviate from the standard mental models everyone else is chasing.
* Chasing a lock-free ring-buffer bug in the Ox Dot hardware firmware that silently caps every recording at twenty minutes.
* Hardening a Temporal workflow that's processing recordings at 2am so it survives a pod eviction without losing a byte of audio. Recordings don't get a second take.
* Fixing mobile audio pipelines so flaky hotel WiFi can't quietly drop a recording that nobody notices is gone until the meeting's long over.
* Exploring real-time audio processing and speaker identification improvements to ensure every captured nuance is correctly attributed for agents to really know the team.
* Writing native macOS/Windows code that lets a desktop app capture both sides of a call with no virtual audio driver.
* Shipping a new feature defined yesterday into the web product that a user starts working with minutes later and never thinks about the complexity underneath.

If "that's not my code" is a sentence you reach for often, the day-to-day here will grate. If you don't understand why anyone would say it, you'll probably feel  have some peculiar tendencies, which make our work far more impactful, fast, and joyful, but they are not for everyone. Radical transparency isn't a value on a poster: it's how we work.

We record the entire engineering journey: every coding session, every AI conversation, every wrong assumption, every rabbit hole, every breakthrough. We don't hide unfinished work because that's where the learning lives.

Roughly:
Go/Rust/Swift, Type Script/Next.js, React Native/Expo/Electron, Postgres, Temporal, AWS/K8s, embedded C/C++, MoQ. You won't touch all of it your first week, but nothing here is permanently someone else's problem.## Taste, Not Just Throughput We ship fast, but speed was never the actual bar. Taste is. That's the bar, both halves at once: architectural taste (reach for the fix that makes the bug structurally impossible, not the patch) and product taste (care about the four seconds nobody will ever thank you for).##

What We're Looking For We're not optimizing for a particular pedigree. We're looking for entrepreneurial builders with systems-first thinking, AI chops, and product judgment. The rest is just evidence.
* ** AI-pilled, for real.
** Agentic coding — Claude Code, Codex, Open Code, whichever tool — is already your daily practice, not something you tried once. We won't teach you…