Sapiens logo

Sapiens Interview Questions
& Process

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

Based on 233 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
62.7% Positive experience

Which role are you interviewing for?

30 roles · 233 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Sapiens.

Showing 4 of 233
Sapiens logo
Sapiens

Full Stack Developer

Engineering · a year ago

Mid Difficult Positive experience Decline offer 3 rounds
Interview process
Technical screen Technical screen Onsite Background check
Interview formats
Technical Coding Behavioral

So the first thing was this 30-minute technical screening, just checking my knowledge on Java, Spring Boot, React, and some SQL. Pretty basic stuff to see if I knew the fundamentals. Then came the main technical deep-dive, about an hour long and way more intense. Started with a live coding challenge, an array question like on LeetCode. After that, we went deep into my ERP project, talking about why I picked certain tech and how I handled security using JWT. The last round was with a manager or HR person. It was mostly about my past experience, how I work with others, and why I wanted to join them. A good mix of behavioral stuff and talking about my career path.

Confirmed questions1 question
  • Can you trace the full flow from a React form's 'Save' button click all the way to the database and back?
Sapiens logo
Sapiens

C++ Developer

Engineering · a year ago

Mid Difficult Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding Other

The interview process kicked off with a recruiter call with an HR person who didn't seem to know much about the role and wasn't very engaged. After that, there was a timed, on-screen quiz using a platform called CoreSuiteLP, which required my webcam to be active. The questions on this quiz were quite odd – they included some very basic C/C++ questions that felt outdated, followed by questions about SQL even though my background isn't in SQL. Then, it moved on to gotcha-style IQ logic puzzles that involved shapes, chickens, and weights. I decided to stop the test because it felt like a waste of my time, and frankly, any company that handles candidates this way isn't a place I'm interested in working for.

Confirmed questions1 question
  • Could you explain the weights of shapes?
Sapiens logo
Sapiens

Sales Development Representative

Sales · a year ago

Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Presentation Group
Interview formats
Behavioral Technical Presentation Case

So, the first step was with recruiters who weren't even from the company, they did the initial screening. Then, I had about three or four chats with different people and decision-makers inside. Each chat was about different things, like my background, my skills, and if I fit what the company is looking for. Later on, I had to do a short presentation, I guess to see if I could explain stuff clearly. I also did a couple of quick exercises to check my problem-solving, how much I know about the industry, or if I could do the job stuff. Oh, and there were also a couple of casual chats with account executives. Those were pretty chill and a good way to get a feel for the team, how things work there, and what's expected.

Confirmed questions2 questions
  • What's your strategy for finding and vetting new potential clients?
  • Can you put together and give a brief presentation explaining how you'd sell our product to a potential customer?
Sapiens logo
Sapiens

Business Analyst

Analytics · a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Case

The initial HR part went fine, but the technical interview was really bad. They first got someone on who seemed totally clueless about the meeting and my resume. I think she was a delivery or technology manager. She was super unprofessional during the whole interview. She seemed bored and kept rolling her eyes like she didn't want to be there. It was obvious they cared a lot about insurance knowledge, which I told them twice I don't have. But she acted like anyone with a degree should know about insurance, its types, and terms. After I said again I don't have insurance experience, they just cut the interview short and sent me an assessment case. I decided not to continue after that.

Confirmed questions1 question
  • Can you describe the different types of insurance and key metrics used in the insurance industry?

Sapiens Interview Questions

Quoted word for word from Sapiens interview reports.

Given a list of strings, how can you return a string containing all anagrams?

Read reports

What is the method to determine if two given strings are anagrams?

Read reports

Implement a function to reverse a linked list between two given intervals.

Read reports

What's the difference between a synchronized HashMap and a Concurrent HashMap?

Read reports

For a given integer, what is a valid number of parentheses combinations?

Read report

What is a virtual destructor, and what is the order of destructors called in inheritance?

Read report

What's the difference between Get and Load in Hibernate's first and second level caching?

Read report

How would you find the sum of all digits in a given number?

Read report

How would you find the number of occurrences of a character in a String?

Read report

Formats, difficulty and experience

Across all 233 Sapiens interview reports.

Interview formats

Technical 41.6%
Behavioral 31.1%
Coding 17.3%
Presentation 3.3%
Other 2.4%

Interview difficulty

Easy 18%
Average 66.1%
Difficult 15.9%

Candidate experience

Positive 62.7%
Negative 25.8%
Neutral 11.6%

Reports by job function

Engineering 164
Analytics 27
Operations 17
Consulting 11
Finance 6
Sales 3