> Markdown version of [/jobs/ext/3584369-system-architect](https://www.wearedevelopers.com/jobs/ext/3584369-system-architect). 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).

---

# System Architect

- **Company:** Wispr Flow
- **Location:** San Francisco, CA, United States
- **Contract:** Permanent contract
- **Skills:** Programming Tools, Distributed Systems, Backend, Low Latency
- **Published:** October 4, 2026
- **Apply:** https://startup.jobs/system-architect-new-products-wispr-flow-10268264

## About the Role

You do not need to have trained foundation models, built a low-level inference stack, or worked in every domain above. Exceptional depth in backend and platform systems, the ability to learn adjacent areas quickly, and demonstrated architecture-level ownership are what matter.

## Description

You'll create core building blocks for AI product concepts that the team can dogfood and build on. You'll shape a reference architecture around models, live context, memory, tools, agent harnesses, and durable execution, making crisp calls about what belongs in each layer. You'll decide which components should become general platform primitives that other teams can adopt., * Build shared platform primitives for agentic systems development, such as memory, context management, tools, and background execution.

 * Create infrastructure for prototyping, training, and evaluating models, with reusable environments and developer tooling.
 * Develop systems for triggers and context capture across devices, surfaces, and modalities.
 * Design harnesses and primitives for coordination and execution handoff between models.
 * Make these systems reliable and production-ready through observability, recovery, security, and latency and cost controls.

You may be a fit if

 * You've designed and shipped a significant greenfield system from an ambiguous problem through production use, then evolved it based on real failures and usage.
 * You've built shared primitives that multiple teams adopted and made deliberate choices about abstraction boundaries and developer experience.
 * You've owned backend or distributed systems with critical scaling and reliability requirements.
 * You start design from the user experience and its latency, quality, privacy, and trust requirements.
 * You've created alignment across product, ML, client, and infrastructure teams, communicated architecture and tradeoffs clearly, and driven decisions to closure.