> Markdown version of [/jobs/ext/3824260-design-engineer](https://www.wearedevelopers.com/jobs/ext/3824260-design-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Design Engineer

- **Company:** SAGEOX INC.
- **Location:** Seattle, WA, United States
- **Experience:** Expert
- **Contract:** Temporary contract
- **Skills:** Computer Animation, Artificial Intelligence, Claude Code, Front End Software Development, Claude
- **Published:** October 18, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=48a9a359a87990d7

## About the Role

We're not optimizing for pedigree. We're looking for builders with design judgment - and we want to see what you've built., * An engineering background, or time at a developer-tools company.

 * Growth or onboarding experience - designing education and activation.
 * Founder or early-employee experience somewhere that grew fast.

## Description

* Ambient coordination. Murmurs - small signals from your coworkers, human and AI, that reach you without becoming another notification you resent.
 * How people grow into SageOx. We're breaking trail on human-AI collaboration, so the learning curve is part of the product: how people start, what nudges them next, and how they get more value over time.
 * Talk to users, and use SageOx daily. Everyone here does. Design from lived use., * A room, cast to a screen. A live conversation on the TV everyone is already looking at, legible from across the room. Different rules than anything designed for arm's length.
 * A living mural. A meeting draws itself as it happens, in front of everyone in the room. What should a thought look like thirty seconds after someone says it? Nobody knows yet.
 * The room as a surface. What a meeting room becomes when a team's memory and its AI coworkers are present in it, and how everyone in it can see and steer what's happening., * A tinkerer who builds things, not just designs them. Apps, tools, side projects, a home-lab rig, a device you hacked together on your bench - things you made yourself, end to end. We don't care whether any of it succeeded; we care that you couldn't stop building.
 * 5+ years in product design, design engineering, industrial design, design systems, or front-end engineering. Long enough to know the design rules, and when to break them. The title matters less than the evidence: what you built, and what happened to the product after.
 * AI-pilled, for real. Claude Code, Claude Design, or your own stack is already your daily practice. You've built something AI coworkers use - a skill, an MCP server, a lint rule, a generator. Show us.
 * Technically fluent, with craft. At home in a codebase and in the terminal. You notice the empty state, the focus ring, and the error message. No CS degree required.
 * Working software over polished mockups. You balance speed with taste. In an age of AI slop, that often means editing and systematizing rather than producing more.
 * Curious sideways. Why a mic distorts, how an index works, what makes an animation feel expensive.
 * Ownership, low ego. You own outcomes, make things happen with limited resources, and find direction in early-stage ambiguity. Strong opinions in crit, open to new perspectives.
 * You believe in what we're building. A world where people and AI coworkers work as one team - and you want to be the one designing it.