Create core building blocks for AI product concepts at Wispr Flow, shaping reference architecture and shared platform primitives.
Posted by employer 1 day ago
First seen on Joblaze 15 hours ago
Last verified on the company career page 15 hours ago
Skills & Technologies
What you'll build
Must have
AI in the day-to-day
Wispr is building an AI voice interface for computing, focusing on natural interaction and context management.
Requirements
Not disclosed in this posting: compensation, years of experience, work arrangement.
Joblaze summary
In this role, the System Architect will focus on developing foundational components for AI products, ensuring they are robust and ready for production use. Key skills include expertise in backend and distributed systems, as well as experience in creating shared platform primitives that enhance developer experience. This position is ideal for someone with a strong background in system design and architecture, particularly in greenfield projects, who can effectively communicate and align cross-functional teams. Wispr Flow is a talent-dense company that values quick testing of ideas and prioritizes user experience in its innovative approach to AI.
Joblaze insights
Quick facts
From the original posting
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’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.
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.
Standard company text repeated across Wispr Flow's postings is omitted here.