Real, anonymous reports from people who interviewed for Frontend Engineer at OpenTable, newest first and distilled into what to expect across the loop.
Get your personalized OpenTable Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I began with an HR/recruiter conversation focused on role alignment and salary expectations. Shortly after, I had what felt like a fundamentals screening where they tested JavaScript knowledge and also gave me a CSS-only task: build a penguin-like illustration using nothing but CSS. There was also a typeahead-style problem. I wasn’t sure how they weighed each part, but the selection seemed to come from how I performed across the frontend concepts and my problem-solving, even though I felt the CSS question didn’t represent my ability perfectly.
Next came a cultural fit round with an engineering manager that mixed some basic culture questions with more frontend fundamentals. I remember leaving that discussion unsure because the assessment didn’t feel aligned with core frontend areas like state management. When I got rejected at that stage, it was disappointing, but I wasn’t too surprised by the misalignment—what threw me off most was how unfamiliar the evaluation felt.
> 1 year
Difficult Negative Vancouver, BC
I went through a long run of interviews that didn’t feel efficient for evaluating someone for the role. I had three technical rounds, each lasting an hour or more, and still didn’t get an offer. After those, there were two additional interviews that were booked and then canceled, which made the whole timeline feel extra drawn out.
What really frustrated me was how much time the process took compared to how little guidance I had on what topics were expected. I also ran into restrictions during one of the technical assignments where I wasn’t allowed to use reference sites like Stack Overflow, which didn’t reflect how software development typically works day to day. Some of the topics I was tested on didn’t match the area I said I specialized in; when I clarified I was a frontend developer, the questions still leaned toward software architecture topics that I hadn’t worked with.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
