Nakisa logo

Nakisa Software Engineer Interview Questions
& Process

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

Based on 17 interview experiences · FREE TO READ

2.5 Rounds average
Average Typical difficulty
64.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Nakisa.

Showing 3 of 17
Nakisa logo
Nakisa

Software Engineer

Engineering · a year ago

Intern Average Positive experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Technical Coding

For the first step, I had a take-home technical assessment. It included MCQs, coding challenges, and SQL questions. In total there were 64 questions covering Git, Spring, Hibernate, Vue.js, JavaScript, JDBC, and REST APIs. I also had to solve 2 Java programming problems and 1 SQL problem. After completing that, I was invited for a 1-hour technical interview with the Hiring Manager. The first 30 minutes were spent discussing my resume and past projects. For the last 25 minutes, I was given a code review task.

Confirmed questions4 questions
  • Can you introduce yourself?
  • Could you elaborate on Java Streams?
  • What is your understanding of DTOs?
Nakisa logo
Nakisa

Software Developer

Engineering

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

I first met the HR head at a campus recruitment fair. I emailed my resume and cover letter and then got called for an interview. The HR head interviewed me for about 30 minutes, asking about my past work experience and some behavioral questions, including salary expectations. She really pushed for numbers, and I wasn't great at avoiding it. After that, the head of Software R&D joined, and I discussed my Master's thesis. He then posed two technical questions: one about finding the 5th element from the end of a list in a single pass and another about designing a database schema for a library system that handles various media types. This was my first technical interview, and I admit I stumbled on a few parts. I also had no idea about Nakisa and just talked about what I saw on their website. For the technical question on list traversal, the easiest way is using a stack or two pointers, but I couldn't figure it out. The tech interviewer gave off a negative vibe, seeming a bit arrogant and unhelpful, just staring while I struggled. Oddly, they mentioned .Net & Java but asked about Flex programming first.

Confirmed questions2 questions
  • Could you state your salary expectations?
  • What information do you have regarding our company?
Nakisa logo
Nakisa

Software Engineer

Engineering

Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

The Montreal location is great and the people were super nice. I had two guys interview me in about an hour. It was a pretty standard difficulty, not too hard, not too easy. Some coding questions were straightforward, but the questions about the core of Java were a little tough. Be ready for anything.

Confirmed questions5 questions
  • Can you explain the difference between shallow and deep copy?
  • What distinguishes == from .equals()?
  • Could you describe the best project you've worked on?

Nakisa Software Engineer Interview Questions

Quoted word for word from Nakisa interview reports.

Can you explain the difference between shallow and deep copy?

Read reports

Could you explain the difference between Stack and Heap memory?

Read report

Describe a situation with two paint containers, one blue and one red.

Read report

Formats, difficulty and experience

Across all 17 Nakisa interview reports.

Interview formats

Technical 37.2%
Behavioral 30.2%
Coding 25.6%
Case 2.3%
Other 2.3%

Interview difficulty

Easy 11.8%
Average 82.4%
Difficult 5.9%

Candidate experience

Positive 64.7%
Neutral 5.9%
Negative 29.4%