Hexagon logo

Hexagon Software Engineer Interview Questions
& Process

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

Based on 95 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
71.6% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Hexagon.

Showing 3 of 95
Hexagon logo
Hexagon

Software Engineer

Engineering · nearly a year ago

Entry Difficult Neutral experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Background check Onsite
Interview formats
Coding Technical Behavioral

First, there's a screening call with HR. If you pass that, they'll send you an online coding test. If you clear that, you'll have a technical interview. If you pass that, they do a reference check. Then, if everything went well, there's a final interview with the manager/HR.

Confirmed questions3 questions
  • Can you tell me about a recent project you worked on?
  • What is Incapsulation?
  • What's your background with C++?
Hexagon logo
Hexagon

Software Engineer Intern

Engineering · nearly a year ago

Intern Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Recruiter call Technical screen Technical screen
Interview formats
Technical Coding Behavioral

Had 2 HR interviews, one with an HR person who is abroad, and another one with HR in Israel. Then, there were two technical interviews with the team manager. You should have a solid understanding of object-oriented programming, specifically in C#, TypeScript, or JavaScript.

Confirmed questions5 questions
  • Had to answer 3-4 pages of basic OOP questions in the first interview.
  • For the second interview, I had to implement an interface for a button that can be used by various classes.
  • What types of serialization are you familiar with?
Hexagon logo
Hexagon

Software Engineer

Engineering · a year ago

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

So at Hexagon, the first thing they did was really dig into my resume, looking for actual projects, clear results, and how I presented my tech stack. Then there was a technical interview that pretty much covered all of full-stack, but they really honed in on backend stuff like Spring Boot, designing APIs, using Jenkins and Docker for CI/CD, and writing unit tests with Mockito. They also threw in some Leetcode-style problems to see how I'd approach them and if I could explain my thinking clearly. After that, the behavioral part was all about ownership, teamwork, and how I handle problems in real life, like when I told them about setting up CI/CD from scratch to cut down on urgent fixes. Basically, Hexagon seems to want engineers who are practical, focused on making an impact, and can totally own their systems from start to finish.

Confirmed questions2 questions
  • Can you share an instance where you exceeded expectations?
  • Tell me about a time you went above and beyond.

Hexagon Software Engineer Interview Questions

Quoted word for word from Hexagon interview reports.

When rolling two dice, what is the probability of obtaining a sum of 9?

Read reports

Write a function in a language you prefer that finds the midpoint of a line given two endpoints.

Read reports

How do you divide a circular shape into 8 equal parts using only 3 straight cuts?

Read reports

Can you write code to verify if a string contains balanced parentheses?

Read reports

Can you explain the functionality of this C++ code: `I = 1; j = 0; for (I++ I++ I++) j++;`?

Read report

Given a square pond with trees at each corner, how can you double its area without the water touching the trees and maintaining a square shape?

Read report

How do you think we can divide a round cake into 8 equal pieces using only 3 cuts?

Read report

Could you reverse the words in a given line of string?

Read report

Manhole covers are round, made of metal, and heavy. Can you think of three reasons why they are designed to be round, and which reason do you find most significant?

Read report

Formats, difficulty and experience

Across all 95 Hexagon interview reports.

Interview formats

Technical 43.2%
Behavioral 27%
Coding 24.1%
Presentation 2.9%
Group 1.2%

Interview difficulty

Easy 24.2%
Average 57.9%
Difficult 17.9%

Candidate experience

Positive 71.6%
Neutral 15.8%
Negative 12.6%