
Sabre 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
Candidate interview experiences
First-hand accounts from people who interviewed at Sabre.
Front End Developer
So after the recruiter first reached out, I got a link to a HackerRank test. It had 25 questions and I had 2 hours to do it. The recruiter mentioned AngularJS, but the test barely had any AngularJS questions, only 2. It was mostly algorithm questions, not really a Javascript test. A big problem was handling STDIN in Javascript code. They give you nodejs boilerplate, but I couldn't figure out how to reference STDIN, so my code failed their tests (they run it in node v.10). It was weird because they didn't ask about closure, scope, prototypes, 'this', or Javascript OOP. Honestly, it felt like non-JS engineers wrote it. They did ask about the '!!' operator though. So yeah, Javascript wasn't a focus, and neither was readability. There were multiple choice questions too, like about the CSS box model, the '!!' operator, jquery, and general CSS. It wasn't super hard, but the confusing questions and the STDIN issue were pretty bad.
- Can you write Fizzbuzz, making sure it gets the loop count from STDIN? You'll be stuck if you don't know how to reference STDIN.
- Could you write a Romanizer that takes a number from STDIN and outputs Roman numerals? Again, STDIN is key here. Also, it wasn't clear if the input was a single number or an array.
- How would you write a function to count the distinct groups of palindromes in a string?
UI Developer
It was an online interview using a webcam. Two interviewers were present, and they were both very friendly and approachable. The interview focused on fundamental programming concepts, without any practical coding exercises. Questions covered topics like encapsulation and procedural programming, along with some behavioral questions.
- Can you explain how to optimize the build or compilation process for User Interface components?
Frontend Developer
It was a very streamlined and no-nonsense interview process. I had one interview call with two interviewers, which was mostly resume and behavioral questions, and one easy technical question. I heard back about 2 weeks later with an offer, but I declined.
- Regarding your JavaScript experience, could you explain what the DOM is?
Sabre Frontend Engineer Interview Questions
Quoted word for word from Sabre interview reports.
“How would you write a function to count the distinct groups of palindromes in a string?”
Read reports →“Could you write a Romanizer that takes a number from STDIN and outputs Roman numerals? Again, STDIN is key here. Also, it wasn't clear if the input was a single number or an array.”
Read reports →“Can you write an AngularJS service that constructs a URL from three parts? And also, write the tests for this service.”
Read reports →“Can you write Fizzbuzz, making sure it gets the loop count from STDIN? You'll be stuck if you don't know how to reference STDIN.”
Read reports →“Could you write an AngularJS directive that performs a 'health check'? The requirement was vague but involved pinging the server every 10 seconds and showing the status. Also, write a complete test suite for this directive.”
Read report →“Can you list the different kinds of variables you're familiar with?”
Read report →“Can you explain how to optimize the build or compilation process for User Interface components?”
Read report →“Regarding your JavaScript experience, could you explain what the DOM is?”
Read report →“Have you previously worked with Gulp?”
Read report →Formats, difficulty and experience
Across all 7 Sabre interview reports.