NODAL EXCHANGE logo

NODAL EXCHANGE Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 9 interview experiences · FREE TO READ

2.9 Rounds average
Difficult Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at NODAL EXCHANGE.

Showing 3 of 9
NODAL EXCHANGE logo
NODAL EXCHANGE

Software Engineer

Engineering · a year ago

Entry Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding Behavioral

A recruiter messaged me on LinkedIn, and instead of scheduling a recruiter screen, they tried to call me randomly for three days straight, or would say they would call and then not. Eventually, the hiring manager was interested, so we set up a technical interview. The recruiter sent a list of times, I picked one that worked, and they scheduled it for a time they hadn't even offered. The technical interview was super technical and hard. The interviewer seemed condescending. She asked about hashmap time complexity, and when I guessed, she sounded skeptical, making me feel dumb. Then she asked about my undergrad and if they taught me data structures. After, I checked and wasn't wrong, so I don't know why she doubted me. There was live coding, not LeetCode style. I followed up after 1.5 weeks and the recruiter said they wanted another interview and sent times. I replied with my availability, and then heard nothing back.

Confirmed questions3 questions
  • Could you tell me the time complexity for getting an element from a hashmap?
  • And what about the time complexity if the element is not found?
  • Can you discuss your undergraduate studies and how your computer science program covered data structures?
NODAL EXCHANGE logo
NODAL EXCHANGE

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral Technical

It kicked off with an online problem-solving test that was pretty abstract. Then, there was a coding challenge in Java where I had to implement an elevator system, aiming to get the cycle rate below their threshold. After that, I was invited onsite for a four-hour stretch of in-person interviews. I met with several team members who asked a mix of brain teasers and detailed questions about Java and my past work. The CIO, who initially contacted me, was really open about the team's current challenges and the state of their tech stack. He did mention that, given my background, I might be a bit junior for the position. The rest of the team seemed focused on their standard, routine questions.

Confirmed questions3 questions
  • What are the key differences and use cases between Java interfaces and abstract classes?
  • Consider the classic problem: if x number of people are shutting doors, how many doors will be shut at the end?
  • Could you outline the core principles of Java?
NODAL EXCHANGE logo
NODAL EXCHANGE

Software Engineer

Engineering

Entry Difficult Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Technical screen Technical screen Background check
Interview formats
Technical Coding System Design Behavioral

It was a two-round interview process. The first was an on-campus thing with the CTO, which was pretty chill, with some brain teasers and good talk about the company. I thought it was a great place for new grads. Then I had an onsite interview that went from around 10 am to 3 pm, which included lunch. The first part of the onsite was with a team lead, and there were some coding questions about linked lists, graphs, and hashmaps – tough but doable. After that, I met with a Business Analyst for a design round where we had to figure out a customer solution based on a prompt. The interview got harder with the third round, focusing on OOP and requiring me to whiteboard two pretty tough coding questions. I managed to get through those first three parts. The fourth and last round, though, was a disaster. The interviewer was really rude and arrogant, hitting me with obscure edge case questions and then nitpicking my resume. It felt hostile, especially since it was about 4.5 hours in with no breaks. They kept asking these cynical questions about graphs and even why 2+2=4. It ended abruptly, and the promised lunch never happened. I was told I'd get an email about the outcome, but after chasing it, I still haven't heard anything.

Confirmed questions3 questions
  • What's your approach to inserting and deleting an item in a linked list?
  • Can you explain how you would solve a maze?
  • How many 1X1 cubes are contained within an Nth Cube?

NODAL EXCHANGE Software Engineer Interview Questions

Quoted word for word from NODAL EXCHANGE interview reports.

And what about the time complexity if the element is not found?

Read reports

Could you tell me the time complexity for getting an element from a hashmap?

Read reports

What are the key differences and use cases between Java interfaces and abstract classes?

Read report

Consider the classic problem: if x number of people are shutting doors, how many doors will be shut at the end?

Read report

What's your approach to inserting and deleting an item in a linked list?

Read report

Can you write merge sort and explain its complexity and applications?

Read report

Formats, difficulty and experience

Across all 9 NODAL EXCHANGE interview reports.

Interview formats

Technical 32.1%
Coding 32.1%
Behavioral 25%
System Design 7.1%
Other 3.6%

Interview difficulty

Easy 0%
Average 44.4%
Difficult 55.6%

Candidate experience

Negative 44.4%
Positive 33.3%
Neutral 22.2%