Nothing logo

Growth · Software Engineer Interview Guide

Sign up to see ATSHeadquartered in United Kingdom

Interview language: English

How to Pass the Nothing Software Engineer Interview in 2026

The Nothing DNA (TL;DR)

Nothing seeks individuals who can articulate their design rationale, especially regarding the user experience of products like Phone (2) and Ear (2). They look for candidates who can clearly explain the "why" behind their decisions, demonstrating a deep understanding of the brand's aesthetic and functional principles.
Interviews inJavaKotlinC++

The Nothing Interview Loop

Your onsite loop will typically consist of 5 rounds.

  1. 1

    Round 1

    Recruiter Screen
    Motivation, role fit, logistics.
  2. 2

    Round 2

    Coding Screen
    LeetCode-medium algorithmic problems under time pressure.
  3. 3

    Round 3

    System Design
    Distributed systems, trade-offs at scale, architecture under constraints.
  4. 4

    Round 4

    Onsite Coding
    LeetCode-hard, debugging, code clarity, edge cases.
  5. 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:

  • Ignoring security aspects of firmware delivery.
  • Not using mocking or stubbing effectively for dependencies.
  • Failing to handle all states and transitions correctly after refactoring.
  • Choosing a data structure that doesn't scale well with the number of users or events (e.g., a simple list for each user's history).

Test Yourself: Real Nothing Questions

Three real prompts pulled from our database.

Type · Edge Cases & Testing

You've written a function that calculates the optimal audio output level based on ambient noise and user settings. Write unit tests for this function, focusing on edge cases and potential failure points. Consider scenarios like extreme noise levels, invalid user inputs, and device limitations.

Type · Ownership

Describe a situation where you encountered a significant technical challenge or bug in a project that was not initially your responsibility. What did you do, and what was the impact of your involvement?

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].

+ many more questions, signals, and worked examples

Sign up to unlock the full Nothing grading rubric

Unlock the Nothing rubric, free

Nothing Interview Question Bank

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

9 of 14 questions shown

1

Recruiter Screen

1
  1. 1

    Type · Motivation

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

Coding Screen

3
  1. 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?
  2. 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.
  3. + 1 more questions in this round (sign up to unlock)
3

System Design

4
  1. 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.
  2. 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.
  3. + 2 more questions in this round (sign up to unlock)
4

Onsite Coding

3
  1. 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.
  2. 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].
  3. + 1 more questions in this round (sign up to unlock)
5

Behavioral / Leadership

3
  1. 8

    Type · Collaboration

    At Nothing, we prioritize a minimalist, functional aesthetic. Describe a time you advocated for removing a complex technical feature or UI element because it compromised the product's simplicity, despite pushback from stakeholders who wanted to include it for feature parity.
  2. 9

    Type · Ownership

    Describe a situation where you encountered a significant technical challenge or bug in a project that was not initially your responsibility. What did you do, and what was the impact of your involvement?
  3. + 1 more questions in this round (sign up to unlock)

Unlock all 14 Nothing questions, free

No credit card. Every question with its framework, the grading signals interviewers score against, and a worked answer for each.

Unlock all 14 Nothing questions

Interview tracks at Nothing

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

Compare Nothing with similar employers

Same DNA, different bar. Browse the closest companies in our database and see how their loops differ.

Practice Nothing interviews end-to-end

Sample answers

What a strong answer to these Nothing interview questions shows.

You've written a function that calculates the optimal audio output level based on ambient noise and user settings. Write unit tests for this function, focusing on edge cases and potential failure points. Consider scenarios like extreme noise levels, invalid user inputs, and device limitations.

A strong answer shows: Strong understanding of unit testing principles.; Ability to identify and test critical edge cases.; Proficiency with a testing framework.; Focus on robustness and reliability..

Describe a situation where you encountered a significant technical challenge or bug in a project that was not initially your responsibility. What did you do, and what was the impact of your involvement?

A strong answer shows: Proactiveness and initiative.; Strong sense of ownership and accountability.; Problem-solving skills beyond assigned tasks.; Commitment to product quality and team success..

Frequently asked questions

WorkfiveExplore careers on Workfive

Unlock the free Nothing interview guide

Sign up