Yammer logo

Yammer Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
41.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Yammer.

Showing 3 of 13
Yammer logo
Yammer

Software Engineer

Engineering · more than a year ago

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

A recruiter reached out, and then I was invited on-site. The recruiter, who was a contractor, offered me lunch, and I met with two different teams. At one point, the recruiter mentioned they had no hiring budget left, but then they called me back about a month later saying they could hire again.

Confirmed questions1 question
  • Can you implement a queue using stacks?
Yammer logo
Yammer

Senior Software Engineer

Engineering · more than a year ago

Senior Average No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

I sent in my application online for the Senior Ruby Developer gig. A few days later, I got an email from HR to set up a phone chat. This first call was basically a chat about tech, my experience, and my resume. We also talked about the Yammer product and other stuff, which was pretty chill. The HR person also laid out the whole hiring process: phone call, then a few Skype interviews, and finally an onsite interview, followed by a chat with an executive or someone high up. After the initial phone screen, they scheduled a Skype interview with a senior engineer. We went deep into current tech and the algorithms used for searching and indexing, and my experience with open-source software. They also hit me with some Ruby questions. The second Skype interview was set up by the first interviewer with the technical lead or another Ruby engineer for the next day. They actually called me an hour and ten minutes later than scheduled, which was a bit of a wait. We started chatting, and he asked some straightforward tech questions, but unfortunately, our Skype connection kept cutting out, so I'm not sure if he could hear me properly. We hung up and tried to reconnect. The connection was better on his end after that, but then he asked about extending modules again, a question I thought I'd nailed in the first interview. That same question dragged on for about five minutes due to his bad connection, which was frustrating. He also asked about my background, functional programming, and some Ruby/Rails specifics like convention over configuration, attr_accessor vs. attr_accessible, and extending modules. It felt pretty basic. I didn't make it to the next round, but I suspect it was because of the bad call quality or maybe they found someone with more experience since I only had about two years of experience for a senior role. Still, I enjoyed the conversations!

Confirmed questions8 questions
  • Can you explain the difference between a string and a symbol in Ruby, and when would you choose one over the other regarding memory and performance?
  • What's the difference between classes and modules in Ruby, and can you elaborate on include, extending modules, and mixins?
  • Could you discuss some specific Ruby features or demonstrate the 'Ruby way' of coding?
Yammer logo
Yammer

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Onsite Take home
Interview formats
Behavioral Coding

My interview process was a bit unique because I was referred by a recruiting agency. It started with a phone screen by a recruiter. Then, I had an on-site interview which included general knowledge questions, discussions about my previous work experience, and some non-technical questions to gauge my personality and cultural fit. Following that, I was given a take-home assignment to demonstrate my coding abilities. After submitting the assignment, I received an offer immediately. It was a straightforward experience!

Confirmed questions1 question
  • They provided a mockup and asked me to write the code for it.

Yammer Software Engineer Interview Questions

Quoted word for word from Yammer interview reports.

Given an unlimited stream of THTHTHTHTHTHHHHHHTTHTHTHTHTH, which sequence comes first: THT or HHT?

Read reports

What are the two elements in an integer array whose sum is closest to zero?

Read reports

What's the distinction between `attr_accessor` and `attr_accessible`?

Read reports

Could you provide an implementation for Nearest Neighbor Search?

Read reports

Can you explain the difference between a string and a symbol in Ruby, and when would you choose one over the other regarding memory and performance?

Read report

Regarding Ruby on Rails, what are the conventions, and what does 'convention over configuration' mean?

Read report

What's the difference between classes and modules in Ruby, and can you elaborate on include, extending modules, and mixins?

Read report

Why and when is 'convention over configuration' beneficial, and what are its downsides?

Read report

Formats, difficulty and experience

Across all 13 Yammer interview reports.

Interview formats

Technical 37.9%
Coding 31%
Behavioral 31%

Interview difficulty

Easy 23.1%
Average 46.2%
Difficult 30.8%

Candidate experience

Positive 41.7%
Negative 41.7%
Neutral 16.7%