Barnes & Noble logo

Barnes & Noble Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Barnes & Noble.

Showing 3 of 7
Barnes & Noble logo
Barnes & Noble

Software Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

I had a phone call with the recruiter first. Then, I met with the hiring manager and two other people on the same day. Each meeting was about 30 minutes. Everyone seemed interested and asked good questions. I really liked them and the interviews. It felt like it was more about whether I'd fit in than just my resume. One person asked me a lot about what I thought they should do in a certain situation, since they were new to it and didn't seem to know much about it.

Confirmed questions3 questions
  • Can you share some general information about your background and past experiences?
  • What is your approach to handling this specific situation?
  • Could you provide your perspective on how this new scenario should be managed?
Barnes & Noble logo
Barnes & Noble

Software Engineer

Engineering

Senior Average Neutral experience No offer 2 rounds
Interview process
Technical screen Recruiter call Offer
Interview formats
Technical Behavioral

The interview involved a project manager, architect, and senior developer. It was unique because no tech questions (C++, ATL, MFC) were asked. Instead, they focused on my past projects, specifically looking for WTL experience. I described my projects and how I executed them. Later, the recruiter called to offer me the position and asked about my availability. After that, the recruiter kept delaying updates on the next steps, and I never found out what happened.

Confirmed questions1 question
  • You mentioned using WTL in a project; could you explain your reasoning for choosing it?
Barnes & Noble logo
Barnes & Noble

Software Engineer

Engineering

Mid Easy Neutral experience Accept offer 2 rounds
Interview process
Phone screen Onsite
Interview formats
Technical

It was a phone interview followed by an onsite interview. The process was pretty straightforward, you can find information about it online. I flew to New York City, which was a great experience. The interview questions weren't overly difficult. The onsite was at a Google building, so the work environment felt really nice.

Confirmed questions1 question
  • How would you solve the 25 horses on 5 tracks problem?

Barnes & Noble Software Engineer Interview Questions

Quoted word for word from Barnes & Noble interview reports.

Can you explain how to manage caching when dealing with multiple versions of a class?

Read reports

You mentioned using WTL in a project; could you explain your reasoning for choosing it?

Read reports

Could you provide your perspective on how this new scenario should be managed?

Read report

Formats, difficulty and experience

Across all 7 Barnes & Noble interview reports.

Interview formats

Technical 53.8%
Behavioral 46.2%

Interview difficulty

Easy 14.3%
Average 42.9%
Difficult 42.9%

Candidate experience

Positive 66.7%
Neutral 33.3%