NaviNet
3.8 of 5 44 reviews
www.navinet.net Boston, MA 150 to 499 Employees

NaviNet Software Engineer Interview Questions & Reviews

Updated Nov 20, 2013
All Interviews Received Offers

Getting the Interview 

50%
33%
16%

Interview Experience 

100%
0%
0%

Interview Difficulty 

4 candidate interviews Back to all interview questions
Relevance Date Difficulty
in

Declined Offer

Positive Experience

Average Interview

Software Engineer Interview

Software Engineer
Boston, MA

I applied through a staffing agency and the process took 1 week - interviewed at NaviNet in September 2013.

Interview Details – Pretty straightforward. Got the interview through a recruiter and was able to land a phone interview which was then followed up by an in person interview a few days later. Interview went well. I met with the manager and we discussd the role and what they were looking for and then I was asked to design a shopping cart system. After designing the system two developers came in and we discussed the architecture and implementing new methods into the design

Interview Question – Nothing too difficult I knew the shopping cart system problem ahead of time as it was given to me by the recruiter and company beforehand to prepare.   Answer Question

Reason for Declining – Was offered other positions I was more interested in.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Easy Interview

Software Engineer Interview

Software Engineer
Boston, MA

I applied through college or university and the process took 4 weeks - interviewed at NaviNet.

Interview Details – Interviewed out of college via a career fair. Interview was a pretty standard audition type. They gave me a simple data structure (like you'd get for an intro to data structures assignment) and gave me an hour by myself to draw out on a whiteboard the general interface and implementation for how I would design a few features and how they would interact. Two engineers than came back and asked my questions about my design decisions. I basically just had to justify why I made the decisions I did, and we discussed in a non-interrogative way what were some other ways it could have been implemented, and they asked me hypothetically how I might change things to satisfy a different set of requirements.

I would basically just suggest getting comfortable with object oriented design and be able to explain why you design something the way you did. They didn't ask me any syntactic or nitty gritty "even if I didn't know that I could just google it" questions, which was a nice change of pace and I felt was a plus (some places think its important to be know obscure shell commands and the like off the top of your head).

Interview Question – Nothing exceptional. Was asked to design a shopping cart system that you might find on a e-commerce web portal and show how I would implement a few basic methods and structure the data.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

Accepted Offer

Positive Experience

Difficult Interview

Software Engineer Interview

Anonymous Employee
Cambridge, MA

I applied through a recruiter and the process took 2 weeks - interviewed at NaviNet in March 2010.

Interview Details – Detailed phone interview to weed out anyone who doesn't know what they're talking about. Second interview was developing and presenting role based software. Third interview was one on one meet and greet.

Interview Question – Name some design patterns you've worked with.   Answer Question

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response

1 person found this helpful

Accepted Offer

Positive Experience

Easy Interview

Software Engineer Interview

Software Engineer
Cambridge, MA

I applied through a recruiter and the process took 2 weeks - interviewed at NaviNet in July 2007.

Interview Details – I had a technical phone screen first, during which I was asked pretty basic technical questions that covered broad range of things (from Transact SQL to object oriented design). They immediately told me that it went well and that HR person will be in touch. After that they emailed me "technical audition" material, which I was supposed to prepare for in advance. I then came in and presented the solution to 2 senior developers on a white board. They asked me a lot of questions, most of them were open-ended design questions and very few syntaxical ones. They made me an offer within a week. This company is taking the hiring process very seriously and is looking for certain types of people that are smart, generic, dynamic, curious, passionate about what they do, and also can communicate well. You can't really prepare in advance for interviews like that.

Was this interview helpful?  
Yes | No
Flag Interview  |  Add Employer Response
RSS Feed Embed
Interviews for Top Jobs at NaviNet

Worked for NaviNet? Contribute to the Community!

NaviNet Videos

Loading...

NaviNet – Why Work for Us?

NaviNet is featured as one of The Boston Globe's 2013 Top Places to Work for in Massachusetts! We strive to be the greatest partner to our clients and the best employer to our employees. We're thrilled about the… Full Overview

Provided by employer [?]

The difficulty rating is the average interview difficulty rating across all interview candidates.

The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.

Your response will be removed from the review – this cannot be undone.

Glassdoor is your free inside look at NaviNet Software Engineer interview questions and advice. All 4 interview reviews posted anonymously by NaviNet employees and interview candidates.