Hammer logo

Hammer Software Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Hammer.

Showing 3 of 6
Hammer logo
Hammer

Software Engineer

Engineering · more than a year ago

Entry Difficult Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical

The whole process was fast and good. The technical team is good. It's a good profile. The technology is very good. There are many things to learn. I interviewed and got confirmed in about a month. Received the offer letter very fast.

Confirmed questions1 question
  • Technical questions relevant to the job.
Hammer logo
Hammer

Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Onsite Onsite
Interview formats
Technical Coding

I had an onsite interview first, no prior calls. I interviewed with other software engineers one on one. They asked some basic questions on data structures, networking, programming concepts, and to figure out how some sample code works. It was about checking my overall understanding of concepts. Then I had a second onsite interview, which was pretty similar.

Confirmed questions1 question
  • Questions on binary tree algorithms were asked, not too difficult though.
Hammer logo
Hammer

Senior Software Engineer

Engineering · more than a year ago

Senior Average Neutral experience No offer 1 round
Interview process
Technical screen Onsite
Interview formats
Technical Coding

I interviewed with the hiring manager and two senior staff engineers. The manager seemed a bit nervous, speaking very quickly. One of the senior engineers asked me some C++ questions and incorrectly stated I was wrong about a question regarding 'delete'. It turns out I was correct after looking it up later. They also asked some general problem-solving questions. The role involves working with SCRUM, focusing on sustaining and feature work, not new development. The salary range seemed to be in the low $90s. Overall, it felt like an okay place to work, but perhaps not a lot of fun, based on the vibe from the engineers.

Confirmed questions2 questions
  • Given 8 objects, one with a different weight, what's the most efficient way to find it using minimal measurements?
  • Can you identify the issue with this C++ code: { object* p=NULL; p = new object(); p->foo() delete p; }?

Hammer Software Engineer Interview Questions

Quoted word for word from Hammer interview reports.

Can you identify the issue with this C++ code: { object* p=NULL; p = new object(); p->foo() delete p; }?

Read reports

Given 8 objects, one with a different weight, what's the most efficient way to find it using minimal measurements?

Read reports

Can you explain the SIP message flow and how a call is set up?

Read report

Formats, difficulty and experience

Across all 6 Hammer interview reports.

Interview formats

Technical 50%
Behavioral 25%
Coding 25%

Interview difficulty

Easy 0%
Average 83.3%
Difficult 16.7%

Candidate experience

Negative 50%
Positive 33.3%
Neutral 16.7%