Πόσο διαρκεί η διαδικασία συνέντευξης της Nothing;

Οι περισσότεροι υποψήφιοι ξοδεύουν 4 έως 8 εβδομάδες από το screen recruiter μέχρι την προσφορά. Το ίδιο το onsite loop τρέχει σε μία μέρα ή χωρίζεται σε δύο μισές ημέρες, με debrief και προσφορά τυπικά μέσα σε 5 εργάσιμες ημέρες μετά.

Πώς πρέπει να προετοιμαστώ ειδικά για την Nothing;

Εστιάστε σε τρία πράγματα: (1) στο DNA της εταιρείας που δείχνεται παραπάνω — τι βαθμολογούν πραγματικά, (2) στους γύρους του loop σας, ειδικά τον γύρο που οι περισσότεροι υποψήφιοι υποτιμούν, και (3) σε εξάσκηση στους τύπους ερωτήσεων αυτού του οδηγού χρησιμοποιώντας ένα δομημένο πλαίσιο όπως CIRCLES ή STAR.

Ισχύει αυτό για ρόλους engineering ή design στην Nothing;

Το DNA παραμένει το ίδιο — αυτό που αλλάζει είναι ο συνδυασμός γύρων. Οι υποψήφιοι SWE αντιμετωπίζουν coding screens αντί για Product Sense· οι designers αντιμετωπίζουν portfolio reviews και ασκήσεις σχεδιασμού. Το «τι εκτιμούν» και τα συμπεριφορικά σήματα μεταφέρονται σε όλες τις λειτουργίες.

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

Growth · Οδηγός συνέντευξης Software Engineer

Applies via Greenhouse

Πώς να περάσετε τη συνέντευξη Software Engineer της Nothing το 2026

Το DNA της Nothing (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.

Οι συνεντεύξεις tech διεξάγονται στα αγγλικά

Ακόμη κι όταν κάνετε αίτηση τοπικά, η ίδια η συνέντευξη γίνεται σχεδόν πάντα στα αγγλικά. Σας δείχνουμε κάθε ερώτηση και prompt πρώτα στα αγγλικά — τη γλώσσα στην οποία θα γίνει η συνέντευξη — με μετάφραση από κάτω για να προετοιμαστείτε στην ισχυρότερη γλώσσα σας.

Το Interview Loop της Nothing

Το onsite loop σας θα αποτελείται τυπικά από 5 γύρους.

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

Η ζώνη κινδύνου: Κορυφαίοι λόγοι που οι υποψήφιοι αποτυγχάνουν

Με βάση τη βάση δεδομένων μας με αποτελέσματα συνεντεύξεων Nothing, αποφύγετε αυτές τις συνηθισμένες παγίδες:

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.

Δοκιμάστε τον εαυτό σας: Πραγματικές ερωτήσεις Nothing

Τρία πραγματικά prompts τραβηγμένα από τη βάση δεδομένων μας.

Τύπος · 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

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?

Τύπος · 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?

+ πολλές ακόμη ερωτήσεις, σήματα και επεξεργασμένα παραδείγματα

Εγγραφείτε για να ξεκλειδώσετε τη ρουμπρίκα βαθμολόγησης JobMentis

Ξεκλειδώστε τη ρουμπρίκα →

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
Τύπος · Motivation
What interests you about working at Nothing, specifically in a software engineering role, compared to other tech companies?

Coding Screen

2
Τύπος · 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
Τύπος · 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
Τύπος · 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
Τύπος · 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
Τύπος · 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
Τύπος · 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
Τύπος · 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
Τύπος · 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