How long does the Nothing interview process take?

Most candidates spend between 4 and 8 weeks from recruiter screen to offer. The onsite loop itself runs in a single day or is split across two half-days, with debrief and offer typically within 5 business days after.

How should I prepare specifically for Nothing?

Focus on three things: (1) the company DNA shown above — what they actually grade for, (2) the rounds in your loop, especially the round most candidates underestimate, and (3) drilling on the question types in this guide using a structured framework like CIRCLES or STAR.

Does this apply to engineering or design roles at Nothing?

The DNA stays the same — what changes is the round mix. SWE candidates face coding screens instead of Product Sense; designers face portfolio reviews and design exercises. The "what they value" and behavioral signals carry across all functions.

Other roles at Nothing:Product Manager Software Engineer Marketing Sales Brand Manager Supply Chain

Growth · Software Engineer Interview Guide

Applies via Greenhouse

How to Pass the Nothing Software Engineer Interview in 2026

The Nothing DNA (TL;DR)

Nothing values candidates embodying their design-led, transparent, and community-focused ethos. They seek innovation, adaptability, and a disruptive mindset, emphasizing problem-solving and a clear vision for future tech in a fast-paced, growth-stage environment.

The Nothing Interview Loop

Your onsite loop will typically consist of 5 rounds.

1
Round 1
Recruiter Screen
Motivation, role fit, logistics.
2
Round 2
Coding Screen
LeetCode-medium algorithmic problems under time pressure.
3
Round 3
System Design
Distributed systems, trade-offs at scale, architecture under constraints.
4
Round 4
Onsite Coding
LeetCode-hard, debugging, code clarity, edge cases.
5
Round 5
Behavioral / Leadership
Past evidence of ownership, influence, resolving conflict.

The Danger Zone: Top Reasons Candidates Fail

Based on our database of Nothing interview outcomes, avoid these common traps:

Incorrectly handling the representation of preference combinations (e.g., treating ['a', 'b'] as different from ['b', 'a']).
Not mentioning the positive impact or learning from the experience.
Focusing only on software without considering potential hardware interactions or misconfigurations.
Making superficial changes without addressing the underlying structural issues.

Test Yourself: Real Nothing Questions

Three real prompts pulled from our database.

Type · Collaboration

Tell me about a time you had a technical disagreement with a colleague or team lead regarding a design decision or implementation approach. How did you handle it, and what was the outcome?

Type · Data Structures & Algorithms

Given a stream of user interactions with Nothing products (e.g., button presses, screen touches, audio playback events), design a system to detect and report anomalous patterns in real-time. Assume events have timestamps and user IDs. What data structures would you use to efficiently track recent activity per user?

Type · Ownership

Tell me about a time you took ownership of a project or initiative that was outside your defined responsibilities. What was the situation, what did you do, and what was the outcome?

+ many more questions, signals, and worked examples

Unlock the rubric →

Nothing Interview Question Bank

A sample from our database, grouped by round. Sign up to see the full set.

9 of 23 questions shown

Recruiter Screen

1
Type · Motivation
What interests you about working at Nothing, specifically in a software engineering role, compared to other tech companies?

Coding Screen

2
Type · Data Structures & Algorithms
Given a stream of user interactions with Nothing products (e.g., button presses, screen touches, audio playback events), design a system to detect and report anomalous patterns in real-time. Assume events have timestamps and user IDs. What data structures would you use to efficiently track recent activity per user?
3
Type · Algorithms
Implement a function that takes a list of audio playback events (each with a start time, end time, and device ID) and returns the total unique listening time per device, ensuring no overlapping intervals are double-counted. For example, if device A plays from 10:00-10:30 and then 10:15-10:45, the total time is 45 minutes, not 60.
+ 1 more questions in this round (sign up to unlock)

System Design

4
Type · API Design
Design a RESTful API for controlling basic functionalities of Nothing audio products (e.g., play/pause, volume control, EQ settings) that can be accessed by a companion mobile app. Consider authentication, error handling, and versioning.
5
Type · Scalability
Imagine Nothing launches a new feature allowing users to share audio playback status (e.g., 'Listening to X on Nothing Ear (2)') to social media. Design a scalable system to handle potentially millions of users updating their status concurrently. Consider the backend infrastructure, data storage, and potential bottlenecks.
+ 2 more questions in this round (sign up to unlock)

Onsite Coding

6
Type · Algorithms
Given a list of user preferences for audio profiles (e.g., {'user1': ['bass-boost', 'noise-cancellation'], 'user2': ['bass-boost'], 'user3': ['noise-cancellation', 'spatial-audio']}), implement a function to find the most popular combination of preferences. If there's a tie, return any one of the most popular combinations.
7
Type · Code Clarity & Design
Refactor the following Python code snippet (which simulates a simplified audio device state machine) to improve its readability, maintainability, and extensibility. Consider using classes, enums, or other design patterns. [Provide a moderately complex, procedural code snippet with magic numbers and unclear state transitions].
+ 1 more questions in this round (sign up to unlock)

Behavioral / Leadership

8
Type · Past Experience
Tell me about a time you had to influence a stakeholder (e.g., engineer, designer, executive) who had a different opinion or priority than yours. How did you approach it, and what was the outcome?
9
Type · Adaptability
Tell me about a time when project requirements or priorities changed suddenly. How did you adapt, and what was the impact on your work?
+ 10 more questions in this round (sign up to unlock)

Unlock the full Nothing question bank

Free signup, no credit card. You get every question + the framework, grading signals, and worked answer for each.

Unlock all questions →

Interview tracks at Nothing

How Nothing's DNA translates across functions. Pick your role.

Nothing SWEs build robust, efficient, and aesthetically integrated software. Interviewers assess problem-solving, scalability for their ecosystem, and ability to contribute to unique UX features like the Glyph Interface, ensuring seamless hardware-software integration.

Collaboration

Tell me about a time you had a technical disagreement with a colleague or team lead regarding a design decision or implementation approach. How did you handle it, and what was the outcome?

Data Structures & Algorithms

+ 1 more

Unlock the Software Engineer grading rubric for Nothing

See full Software Engineer guide