N

How to Pass the Nelly Software Engineer Interview in 2026

Growth · Software Engineer Interview Guide

Sign up to see ATSHeadquartered in Germany

Interview language: English

The Nelly DNA (TL;DR)

Patient intake workflows and practice management integrations anchor Nelly's evaluation. Interviewers probe how candidates handle strict DSGVO compliance and medical practice cash flow workflows.
Interviews inTypeScriptGo

The Nelly 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 Nelly interview outcomes, avoid these common traps:

  • Checking overlapping intervals with O(N^2) pairwise comparisons
  • Unbounded retry loops under high lock contention causing resource exhaustion
  • Forgetting to update heap positions when priorities change
  • Assuming event logs are strictly ordered across different practice accounts without verifying timestamps

Test Yourself: Real Nelly Questions

Three real prompts pulled from our database.

Type · motivation-fit

Why are you interested in building payment and patient intake infrastructure for medical practices at Nelly, and how does your engineering background prepare you for strict compliance fintech environments?

Type · privacy-architecture

Design a storage and audit logging engine for patient copay transactions that complies strictly with DSGVO/GDPR requirements while allowing medical practices to generate real-time financial reconciliation reports.

Type · string-manipulation

Given a sequence of payment status events (such as PENDING, AUTHORIZED, CAPTURED, REFUNDED), walk through how you would detect invalid state transition sequences and identify the transaction ID with the earliest violation.

+ many more questions, signals, and worked examples

Sign up to unlock the full Nelly grading rubric

Unlock the Nelly rubric, free

Nelly Interview Question Bank

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

7 of 15 questions shown

1

Recruiter Screen

1
  1. 1

    Type · motivation-fit

    Why are you interested in building payment and patient intake infrastructure for medical practices at Nelly, and how does your engineering background prepare you for strict compliance fintech environments?
2

Coding Screen

4
  1. 2

    Type · algorithmic

    Given an array of patient payment transactions containing timestamps and amounts, describe an algorithm to find the maximum sum of transactions that occur within any rolling 24-hour window.
  2. 3

    Type · data-structures

    Design a data structure that supports inserting medical payout transaction IDs with priority scores, updating existing priority scores in real time, and retrieving the top K highest priority pending payouts efficiently.
  3. + 2 more questions in this round (sign up to unlock)
3

System Design

5
  1. 4

    Type · distributed-systems

    Design a high-throughput payment processing engine for medical practices that guarantees exactly-once payment execution, even when payment gateway webhooks are delayed, duplicated, or delivered out of order.
  2. 5

    Type · privacy-architecture

    Design a storage and audit logging engine for patient copay transactions that complies strictly with DSGVO/GDPR requirements while allowing medical practices to generate real-time financial reconciliation reports.
  3. + 3 more questions in this round (sign up to unlock)
4

Onsite Coding

5
  1. 6

    Type · data-structures

    Explain how you would design a memory-efficient structure to detect duplicate patient payment attempts submitted within a rolling 5-minute window across distributed payment nodes without storing every full transaction in memory.
  2. 7

    Type · problem-solving

    Walk through an algorithm to merge overlapping patient installment payment schedules while maintaining accurate remaining balances, original due date structures, and strict audit provenance.
  3. + 3 more questions in this round (sign up to unlock)

Unlock all 15 Nelly questions, free

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

Unlock all 15 Nelly questions

Interview tracks at Nelly

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

Compare Nelly with similar employers

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

Practice Nelly interviews end-to-end

Sample answers

What a strong answer to these Nelly interview questions shows.

Why are you interested in building payment and patient intake infrastructure for medical practices at Nelly, and how does your engineering background prepare you for strict compliance fintech environments?

A strong answer shows: Alignment with Nelly mission in healthtech fintech; Understanding of high-stakes financial data handling.

Design a storage and audit logging engine for patient copay transactions that complies strictly with DSGVO/GDPR requirements while allowing medical practices to generate real-time financial reconciliation reports.

A strong answer shows: Knowledge of data privacy laws and cryptographic tokenization; Designing for compliance without sacrificing reporting query latency.

Frequently asked questions

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

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

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 Nelly interview guide

Sign up