Everyday Health Group Frontend Engineer Interview Questions
& Process

I went through this blitz interview that another reviewer mentioned, which they claimed was great, but to each their own. It was a long process involving a presentation, a written test, panel interviews, and then one-on-one interviews. I found it demotivating that companies like this seem to delude themselves into thinking they get the best candidates through this process. They really pushed the idea that they are a fun, amazing company to work for, which gave me the impression they saw it as 'you'd be lucky to work for us,' not a mutually beneficial hire. They also seemed to emphasize that they were more interested in how we think. But as Maury would say, that's a lie. They cared exclusively about your skill, not how you think or even your personality. The questions on the written exam were specific coding questions, like 'how would you use jquery to cause alternating rows to different colors' and 'write a javascript function that accepts an unlimited number of args.' None of the questions proposed a high-level problem and asked how you'd solve it, which is the right way to gauge a candidate's thinking. A page full of very specific bootstrap implementation questions should have given that away. The panel interviews were worse. They googled JavaScript interview questions, which were the exact questions they asked, completely turning me off from this company. Questions included: 'Explain JavaScript inheritance, what's the difference between null and undefined, what does position: absolute mean? what's the difference between two equal signs and three equal signs?' During the inheritance question, I went into how prototypical inheritance differs from classical inheritance, and they were completely lost. Realizing I didn't want to work for front-end developers who have no knowledge or care for how back-end languages and true OOP work, I politely answered the rest of their questions and then left before waiting to hear if I made it to the final round. The best part was listening to all the remaining candidates talk about how they love Macs and hate using Windows, and were telling each other the company would probably be okay with them using a Mac instead, while Everyday Health uses ASP.NET/C#. Keep in mind one or more of these people got hired.

The company held a hiring blitz. 12 referred candidates were brought in for a 4-hour interview. The night before, we did a small take-home test. In the office, there was a half-hour written test, after which half were cut. Dinner was provided. Then, there were two interview rounds. They cared more about our thought process than what we knew. By evening, 4 candidates remained, and they had 2-3 openings. My recruiter said they'd make an offer the next morning, and I got it that afternoon.

First, there was a technical interview with the Team Lead. He showed some javascript code and asked me to predict the output without running it. Then, I had a face-to-face meeting with the whole team where I met everyone individually. They asked me technical questions specifically about front-end technologies, especially javascript. This round lasted for about 3.5 hours.