NW logo

How to Pass the NW Software Engineer Interview in 2026

Growth · Software Engineer Interview Guide

Sign up to see ATSHeadquartered in France

Interview language: English

The NW DNA (TL;DR)

Engineering and operations interviews for IECharge and JBox systems scrutinize a candidate's capacity to optimize grid-scale electricity storage while navigating French energy regulations.
Interviews inPythonTypeScript

The NW 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 problems, reasoning about defects, 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 NW interview outcomes, avoid these common traps:

  • Not demonstrating any understanding of NWG's specific business or the energy industry challenges.
  • Inefficiently calculating standard deviation or averages for each meter on every incoming data point.
  • Not considering potential bottlenecks in both the application code and the underlying infrastructure (Redis, PostgreSQL).
  • Focusing on the interpersonal conflict rather than the technical trade-off evaluation

Test Yourself: Real NW Questions

Three real prompts pulled from our database.

Type · system-design

Design a system to predict energy demand for a city at hourly intervals for the next 7 days. The system should ingest data from various sources: historical consumption, weather forecasts (temperature, humidity, cloud cover), calendar events (holidays, major local events), and real-time grid status. Consider scalability, accuracy, and maintainability.

Type · debugging

A microservice responsible for calculating dynamic electricity pricing based on grid load and demand is experiencing intermittent latency spikes and occasional 5xx errors. The service uses a Redis cache for recent load data and a PostgreSQL DB for historical trends. How would you approach debugging this issue?

Type · past-experience

Tell me about a time you identified a potential issue or inefficiency in a system or process that others had overlooked. What did you do about it, and what was the result?

+ many more questions, signals, and worked examples

Sign up to unlock the full NW grading rubric

Unlock the NW rubric, free

NW Interview Question Bank

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

9 of 13 questions shown

1

Recruiter Screen

1
  1. 1

    Type · motivation

    NWG is a leader in the energy sector, focusing on sustainable solutions and grid modernization. What specifically about our mission and technology in areas like smart grids or renewable energy integration excites you as a software engineer?
2

Coding Screen

3
  1. 2

    Type · algorithmic

    Given a stream of real-time energy consumption data from smart meters (timestamp, meter_id, kwh_consumed), design a system to detect anomalous consumption patterns for a given region. You need to return meter_ids with consumption deviating significantly (e.g., > 3 standard deviations) from the historical average for that meter, within a 5-minute window. Assume data arrives out-of-order.
  2. 3

    Type · algorithmic

    You are given a list of energy generation sources (e.g., solar farms, wind turbines) with their current output, capacity, and a forecast for the next hour. You also have a list of demand points with their current load and priority. Design an algorithm to optimally allocate generation to meet demand, minimizing unmet demand and prioritizing high-priority points, while respecting generation capacities and forecasts. Return the allocation plan.
  3. + 1 more questions in this round (sign up to unlock)
3

System Design

3
  1. 4

    Type · system-design

    Design a system to predict energy demand for a city at hourly intervals for the next 7 days. The system should ingest data from various sources: historical consumption, weather forecasts (temperature, humidity, cloud cover), calendar events (holidays, major local events), and real-time grid status. Consider scalability, accuracy, and maintainability.
  2. 5

    Type · system-design

    Design a distributed system for managing and optimizing the charging of a fleet of electric vehicles (EVs) for a utility company. The system needs to schedule charging times based on grid load, electricity prices (time-of-use), vehicle availability, and user preferences. Consider how to handle thousands of vehicles and real-time updates.
  3. + 1 more questions in this round (sign up to unlock)
4

Onsite Coding

3
  1. 6

    Type · algorithmic

    Implement a function that takes a list of energy grid nodes, their connections (representing power lines), and the current power flow on each line. The function should identify any nodes that are currently overloaded (power flow exceeds line capacity) or under-utilized (power flow is significantly below capacity for extended periods). Return a list of affected nodes and the nature of the issue (overloaded/under-utilized).
  2. 7

    Type · coding

    Write a function to simulate the impact of a distributed renewable energy source (like rooftop solar) on the local grid. The function should take current grid load, the capacity of the renewable source, and its intermittent output (e.g., a list of power values over time). It should return the net load on the grid at each time step, considering potential grid stabilization mechanisms (e.g., battery storage). Ensure the code is clean, well-commented, and handles potential errors.
  3. + 1 more questions in this round (sign up to unlock)
5

Behavioral / Leadership

3
  1. 8

    Type · past-experience

    Tell me about a time you had to work with a legacy system or codebase that was difficult to understand or modify. What steps did you take to gain understanding and make your changes successfully?
  2. 9

    Type · past-experience

    At NW, we often balance the need for rapid digital innovation with the extreme reliability requirements of the French energy grid. Describe a specific project where you had to advocate for a trade-off between introducing a cutting-edge technology and maintaining the stability of a mission-critical system. How did you validate your approach to ensure it met our Fiable Des principles?
  3. + 1 more questions in this round (sign up to unlock)

Unlock all 13 NW questions, free

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

Unlock all 13 NW questions

Interview tracks at NW

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

Compare NW with similar employers

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

Practice NW interviews end-to-end

Sample answers

What a strong answer to these NW interview questions shows.

Design a system to predict energy demand for a city at hourly intervals for the next 7 days. The system should ingest data from various sources: historical consumption, weather forecasts (temperature, humidity, cloud cover), calendar events (holidays, major local events), and real-time grid status. Consider scalability, accuracy, and maintainability.

A strong answer shows: Understanding of data pipelines and ETL.; Knowledge of time-series forecasting techniques and machine learning.; Consideration of scalability, fault tolerance, and monitoring..

A microservice responsible for calculating dynamic electricity pricing based on grid load and demand is experiencing intermittent latency spikes and occasional 5xx errors. The service uses a Redis cache for recent load data and a PostgreSQL DB for historical trends. How would you approach debugging this issue?

A strong answer shows: Structured debugging methodology.; Understanding of distributed system components (microservices, cache, DB).; Ability to identify potential performance bottlenecks..

Frequently asked questions

How long does the NW 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 NW?

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 NW?

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.

WorkfiveExplore careers on Workfive

Unlock the free NW interview guide

Sign up