About the Software Engineer, UI Role at Wispr Flow

Wispr Flow is building the first voice dictation platform people use more than their keyboards, and in 2026 the team is expanding into native actions, an agentic framework that understands users and works reliably. As a UI Engineer on the Engineering team in San Francisco, you own the craft layer of the product: the surfaces, interactions, and details that turn a capable tool into one people love. You will work directly with product and design to prototype, build, and ship polished interfaces across the voice platform and native actions framework.

This is a role for someone who treats visual and interaction quality as a first-class engineering concern. The posting is explicit about what matters: exceptional UI/UX taste, deep empathy for how people actually use software, and fluency in TypeScript, React, and CSS. Wispr Flow wants high-agency engineers who sweat the details, notice when something feels off, and fix it, backed by a portfolio or body of work that shows real visual craft.

Quick Stats

* Typical process: 4 to 5 rounds, roughly 2 to 4 weeks

* Format: Recruiter phone screen, then video technical and portfolio rounds, likely a final onsite or virtual onsite in San Francisco

* Core focus: UI/UX taste, TypeScript, React, CSS, animation systems (Framer Motion, CSS transitions), interaction fidelity, portfolio craft, product empathy

* Difficulty: Hard, because the bar is not just working code but pixel-level polish, timing and feel of animations, and defending strong opinions on interface design

What Wispr Flow Looks For

* Exceptional UI/UX taste with strong, defensible opinions on what makes an interface feel right

* Fluency in TypeScript, React, and CSS with expressive, maintainable, detail-oriented code

* Incredible attention to detail on design, animations, and interaction fidelity, plus experience with animation systems like Framer Motion and CSS transitions

* A portfolio of side projects, open source, or shipped products with a clear point of view, ideally paired with founding or startup experience

Round 1: Recruiter Screen (~30 minutes)

What to Expect

A recruiter or hiring manager kicks off with a phone or video call to understand your background, motivation, and fit for a fast-moving, high-agency startup. Expect questions about why voice interfaces and Wispr Flow specifically excite you, your experience shipping polished UI, and a walkthrough of the portfolio work you submitted. Because the posting asks you to "send your best," be ready to point to specific projects that show visual craft and a clear point of view.

Example Questions

* "What draws you to Wispr Flow and the idea of rethinking human-computer interaction through voice?"

* "Walk me through the project in your portfolio you are most proud of and why."

* "Tell me about a time you shipped an interface that people genuinely loved."

* "What does startup or founding experience look like on your resume, and how do you operate with high agency?"

Tips

* Have a crisp two-minute pitch on your background and why voice-first interfaces matter to you.

* Pick one or two portfolio pieces you can narrate end to end, focusing on the craft decisions and the user impact.

* Practice this conversational mix with Nora AI's Standard Mode so your motivation and portfolio story sound natural and confident.

Round 2: Portfolio and Craft Review (~45 to 60 minutes)

What to Expect

Given how heavily the posting weights "a portfolio or body of work that demonstrates visual craft," expect a dedicated round where you present your work to engineers and designers. You will walk through shipped products, side projects, or open source, and defend your interaction and animation choices. Interviewers will probe your eye for timing and feel, your attention to detail, and whether you notice and fix things that feel off. This round is as much about taste and communication as it is about code.

Example Questions

* "Show us an interaction or animation you built and explain the timing and easing choices you made."

* "Where in this project did something feel off, and how did you fix it?"

* "How did you decide what to polish versus what to ship as good enough?"

* "Defend a design opinion you hold that others on your past teams disagreed with."

Tips

* Come with live demos or screen recordings so interviewers can feel the interactions, not just see static screenshots.

* Be specific about animation systems you used (Framer Motion, CSS transitions) and articulate why the timing feels right.

* Rehearse defending your taste out loud with Nora AI's Behavioral Mode so you can explain and justify craft decisions under questioning.

Round 3: Frontend Technical and Build (~60 to 90 minutes)

What to Expect

This is the core technical round, tied directly to the posting's requirement of fluency in TypeScript, React, and CSS. Expect a hands-on exercise: building or extending a small component, implementing a polished interaction or animation, and debugging or refactoring existing frontend code. Interviewers will watch for expressive, maintainable code, strong programming practices, and high throughput, along with the interaction fidelity the role demands. Some prompts may connect to real product surfaces like a voice dictation UI or the native actions framework.

Example Questions

* "Build a React component with a smooth open and close animation, and explain your easing and duration choices."

* "Here is a piece of TypeScript and CSS that feels janky. How would you refactor it for maintainability and feel?"

* "How would you structure state and components for a real-time, context-aware voice input surface?"

* "Implement this interaction with Framer Motion and walk us through how you tune the timing."

Tips

* Write clean, typed, readable code and narrate your decisions; the role treats code quality and UX as equally important.

* Do not just make it work, make it feel right; pay attention to animation timing, transitions, and edge cases.

Round 4: Team Fit and Values (~45 minutes)

What to Expect

Wispr Flow describes a culture of spirited debate, truth-seeking, open communication, and obsessing over users. This round, often with the hiring manager and future teammates, digs into how you collaborate with product and design, handle disagreement, and operate as a high-agency, detail-obsessed engineer. Expect behavioral and situational questions grounded in the posting's emphasis on being an outstanding team player and communicator with deep empathy for users.

Example Questions

* "Tell me about a time you disagreed with a designer or PM and how you resolved it."

* "Describe a situation where you had to make a fast decision with incomplete information."

* "How do you balance code velocity with the level of polish this role expects?"

* "Give an example of when deep empathy for a user changed how you built something."

Tips

* Prepare STAR stories that show high agency, open communication, and attention to detail under real constraints.

* Lean into examples of collaborating tightly with design and defending user-first decisions.

* Rehearse these stories with Nora AI's Behavioral Mode so your answers stay structured and specific.

Round 5: Offer and Salary Negotiation (~30 minutes)

What to Expect

If things go well, the recruiter returns with an offer conversation. The posted range is $180K to $325K with equity, which is a wide band that leaves real room to negotiate based on your level, portfolio strength, and prior startup or founding experience. Expect discussion of base, equity, start date, and expectations for the role.

Example Questions

* "What are your compensation expectations for this role?"

* "How do you think about base salary versus equity at an early-stage, high-growth company?"

* "Do you have competing offers or timelines we should know about?"

* "What would make this the clear choice for you?"

Tips

* Anchor your ask with market data and the strength of your portfolio and shipped work.

* Weigh equity seriously given Wispr Flow's +150% quarterly revenue growth and $81M raised, but do not undersell your base.

* Practice the back-and-forth with Nora AI's Salary Negotiation Mode so you can advocate for your number calmly and clearly.

Frequently Asked Questions (FAQ)

1) How many rounds are there?

Expect roughly 4 to 5 rounds: a recruiter screen, a portfolio and craft review, a hands-on frontend technical round, a team fit and values round, and an offer and negotiation conversation. Wispr Flow has not published its exact process, so this reflects the typical structure for a UI Engineer role at a startup of this stage.

2) What topics are most common?

* TypeScript, React, and CSS fluency, plus animation systems like Framer Motion and CSS transitions with a focus on timing and feel

* UI/UX taste, interaction fidelity, portfolio craft, product empathy, and collaboration with product and design

3) How long does the process take?

Usually about 2 to 4 weeks from the recruiter screen to an offer, depending on scheduling and how quickly the portfolio and technical rounds are arranged.

4) How should I prepare?

* Curate a portfolio that shows visual craft and a clear point of view, with live demos of your best interactions and animations.

* Sharpen your TypeScript, React, and CSS skills, and practice building polished, well-timed animated components.

* Prepare STAR stories that demonstrate high agency, detail obsession, and strong collaboration with design and product.

* Use Nora AI to rehearse: Standard Mode for the recruiter screen, Technical Mode for the frontend build round, Behavioral Mode for the portfolio and values rounds, and Salary Negotiation Mode for the offer conversation.