Priceline.com logo

Priceline.com Frontend 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

3 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Priceline.com.

Showing 3 of 7
Priceline.com logo
Priceline.com

Front End Developer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Technical Coding Behavioral

I sent in my application and heard back about the role. Then I had a technical chat with a lead frontend dev where we talked shop and then I did some coding on jsfiddle and solved one quick coding problem. They then flew me in for an in-person interview and put me up in a hotel since I'm from out of town. The in-person part had three rounds: two with groups of developers and the last with a product manager. I had to solve three coding problems focused on strings and JS objects/JSON. The interview really dug into JavaScript specifics, more than usual for a front end role, but it wasn't too hard. Everyone was nice and I took their offer.

Confirmed questions3 questions
  • What are your thoughts on javascript variable scoping, specifically some advanced questions?
  • Can you show me how you would manipulate some json data to filter out some of the objects?
  • Please code something that checks if any items in an array are greater than 10.
Priceline.com logo
Priceline.com

Front End Engineer

Engineering · more than a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

I applied online and a recruiter hit me up through email. We did a phone screen but honestly, they didn't really check my Javascript skills well. After that chat, which was friendly but not really technical, they set up an in-person interview. The whole gig is basically Javascript. They mentioned they're using a new stack with node.js and angular, moving on from JSP. It was kind of unprofessional having to take PTO for the on-site when they could've figured out my JS level over the phone. If you have node.js on your resume, they'll dig into that, and same for angular. If you don't get the offer, and you value your PTO, you basically paid out of pocket for it since they could have done a better job on the initial phone screen.

Confirmed questions5 questions
  • Can you explain Javascript scoping?
  • What is hoisting in JS?
  • How do you change scope?
Priceline.com logo
Priceline.com

Front End Developer

Engineering

Entry Average Neutral experience No offer 1 round
Interview process
Recruiter call Take home Technical screen
Interview formats
Coding Technical

I put in my application on the website. A bit over a month later, I was sent an online test that I didn't have to do. They said that if I took the test, my interview process would be faster, but if not, I would have to wait longer, but I would still advance. I decided to do the test. It had six questions and I had one hour to complete them. Three were multiple choice, and three were coding questions. The coding questions were: array filter, build constructor, and array change.

Confirmed questions3 questions
  • How to filter an array?
  • How to build a constructor?
  • How to change an array?

Priceline.com Frontend Engineer Interview Questions

Quoted word for word from Priceline.com interview reports.

Could you explain the difference between display: none and visibility: hidden in CSS?

Read reports

Formats, difficulty and experience

Across all 7 Priceline.com interview reports.

Interview formats

Technical 38.9%
Coding 33.3%
Behavioral 27.8%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 42.9%
Neutral 42.9%
Negative 14.3%