Me postulé a través de una facultad o universidad. El proceso tomó 3 semanas. Acudí a una entrevista en Hexagon (Madison, AL) en sep 2017
Entrevista
Normally there would have been a phone interview followed by an in-person interview at the campus, but since I was given the option, I decided to skip straight to the in-person interview on campus. I met with project heads for two different positions, but both interviews had the same format. In each, I sat down the project head and one of their subordinates. First, we discussed my background and my school history. After that, they asked me some questions about basic programming principles that were pertinent to the type of work work I'd be doing such as inheritance, use of classes, SQL queries, etc. After the formal interviews, I was treated to lunch on campus with a group of employees who also attended my university who later also gave me a product demonstration and fielded any questions I had about the company, the job itself, the what the workday is like.
Preguntas de entrevista [2]
Pregunta 1
In the language of your choosing, write a method or function to, given two endpoints, determine the midpoint of a line.
Consider a manhole cover. All manhole covers are metal, really heavy, and round. Think of three reasons why manhole covers might be round by design, and explain which reason you think is the most important.
The assessment covers OOPS concepts, mathematics, basic coding, and database knowledge. Along with technical skills, evaluators also carefully observe your communication abilities, making it essential to balance subject expertise with clear, effective interaction.
Preguntas de entrevista [1]
Pregunta 1
oops concepts in much detail with lot of advance maths (geometry) & aptitude
My interview process at Hexagon started with a thorough resume screening that emphasized real-world projects, clear impact metrics, and clean tech stack presentation. The technical round focused on full-stack skills—especially backend systems using Spring Boot, API design, CI/CD pipelines with Jenkins and Docker, and writing effective unit tests with Mockito. I was also asked to solve a few Leetcode-style problems with a focus on my approach and clarity. The behavioral interview emphasized ownership, collaboration, and problem-solving in real scenarios, where I shared examples like implementing CI/CD from scratch to reduce hotfixes. Overall, Hexagon valued pragmatic, impact-driven engineers who could own systems end-to-end.
Interview went smoothly, it was a great experience. They were calm and helped me if I got stuck. It was divided into two rounds one was the technical round and other was HR round. In coding they asked a dynamic programming problem which i had to optimize till the tabulation method.
Preguntas de entrevista [1]
Pregunta 1
They asked every project I did in detail and dived deep into my resume.