Front End Engineer Interview Questions

Front End Engineer Interview Questions

A front end engineer is focused on the user experience of software or an app. During an interview, you will need to demonstrate that you understand UX/UI design principles, a commitment to clean code optimized for the product offering, and a willingness to work with backend engineers to solve problems. Expect to be asked about your technical experience, as well as your people management and design skills.

Top Front End Engineer Interview Questions & How to Answer

Question 1

Question #1: What is your preferred workflow/management style?

How to answer
How to answer: Outline what tools and methodologies you use to manage the development of a product. Talk about the strategies you use to work with a diverse range of stakeholders, including clients, sales and marketing, and back end engineers. Use specific examples to show how your workflow has been successful, and also express a willingness to adapt and change when necessary.
Question 2

Question #2: How do you manage testing, reviews and version control?

How to answer
How to answer: A lot of a front end engineer's role involves the nitty gritty details that make sure a user's experience is seamless. Highlight that you understand the importance of good clean code, testing protocols, and version management. Use examples of methodologies you have used and what problems they addressed or solved.
Question 3

Question #3: What excites you most about the UX/UI space?

How to answer
How to answer: A question like this is your opportunity to show that you are passionate about front end engineering. Explain how you integrate user-centered design in your projects and the philosophies that you follow. Outline any books or articles you have read and what you agree with. If possible, talk about what changes you foresee and how you think design and technology will adapt to those changes.

21,104 front end engineer interview questions shared by candidates

For the take-home code test, they want you to build a UI, with which to search for campaigns, each by the campaign URL (they provide working sample URLs in the README). Upon successful search, the result is to be added to a list of results, from their response JSON/JSONP (which, BTW, doesn't even have the correct content type, in the response header). Each result is rendered per their README, with regard to CSS and PNG images (for removing a result from the results list, etc, which they also provide). The donation amount for each result is added to a total, to be rendered, via alert, upon a button click. Upon removal of a result, its donation amount is subtracted from the total, and rendered dollar amounts must be formatted (i.e., $10,000.00). As an additional condition, each result should render only after its child images (for which there are two source links: one for the campaign, the other for the campaign owner) have loaded into the DOM. They suggest you spend no more than three hours on the test, and provide you a span of seven days, in which to submit your working code, along with any notes.
avatar

Front End Engineer

Interviewed at Tilt

3.9
Aug 26, 2015

For the take-home code test, they want you to build a UI, with which to search for campaigns, each by the campaign URL (they provide working sample URLs in the README). Upon successful search, the result is to be added to a list of results, from their response JSON/JSONP (which, BTW, doesn't even have the correct content type, in the response header). Each result is rendered per their README, with regard to CSS and PNG images (for removing a result from the results list, etc, which they also provide). The donation amount for each result is added to a total, to be rendered, via alert, upon a button click. Upon removal of a result, its donation amount is subtracted from the total, and rendered dollar amounts must be formatted (i.e., $10,000.00). As an additional condition, each result should render only after its child images (for which there are two source links: one for the campaign, the other for the campaign owner) have loaded into the DOM. They suggest you spend no more than three hours on the test, and provide you a span of seven days, in which to submit your working code, along with any notes.

The first question was JavaScript scoping: var x = 9; var module = { x: 81, getX: function() { this.x = 10 return this.x; } }; module.getX(); // nr 1 -> 10 var retrieveX = module.getX; retrieveX(); // nr 2 -> 9 var boundGetX = retrieveX.bind(module); boundGetX(); // nr 3 -> 81 The second question was FizzBuzz again:
avatar

Front-end Developer

Interviewed at Typeform

3.3
Jul 14, 2016

The first question was JavaScript scoping: var x = 9; var module = { x: 81, getX: function() { this.x = 10 return this.x; } }; module.getX(); // nr 1 -> 10 var retrieveX = module.getX; retrieveX(); // nr 2 -> 9 var boundGetX = retrieveX.bind(module); boundGetX(); // nr 3 -> 81 The second question was FizzBuzz again:

Viewing 81 - 90 interview questions

Glassdoor has 21,104 interview questions and reports from Front end engineer interviews. Prepare for your interview. Get hired. Love your job.