The first visit involved a face-to-face interview with two developers. We discussed my knowledge, expectations, and the specifics of the job position.

Following that, I was given a test to complete at home via email. The test required building a responsive JavaScript application that would:

• Display a list of games based on a provided JSON file.
• Allow users to search the list.
• Show detailed information for each game on a separate page.
• Enable users to add or remove games from a favorites list.
• Display and allow searching of favorites on another page.

The requirements stated that I was allowed to use JavaScript frameworks/libraries, but not too many (?).

The resulting Single Page Application (SPA) was built with Angular 1.5 and Bootstrap, written in ES6. It featured three views, routing, deep linking, pagination, and search functionality. I used a basic Angular seed with some personal modifications.

On the second visit, I had four interviews.

The first interview was with two developers to review the test. They expressed concern that I had used too many libraries, noting that my package.json was "full of libraries." In reality, my application had only two dependencies: Angular and Bootstrap. The rest were clearly marked as "devDependencies" and were used for tooling (webpack modules, Karma, linting, Babel ES6 transpiling modules, etc.). They also had the impression that I had acquired everything from the seed. However, my code was present, and the application performed as required.

If I used a seed, it doesn't mean the application was magically created from it or that I don't understand its contents. Similarly, if I follow a JavaScript pattern, it doesn't mean I didn't write the code or that everything originates from the pattern.

In conclusion, I believe the description of the test was inaccurate and too vague.

The interview also included questions about Angular, classic JavaScript trick questions (e.g., "What's the length of const x = [2]?"), and some elaborately phrased questions about "CSS Paradigms." Another question asked if arrow function syntax uses "lexical scoping" for "this," posed after I had already explained in my own words that in arrow functions, "this" is picked up from the surrounding function.

The second interview focused on "What if..." and "What would you do..." type questions related to Kanban, SCRUM, and Agile methodologies.

The interviewer for the third interview had not read my CV. He asked, "if they flew me in," despite the fact that I live and work in Barcelona, which was clearly stated on my CV. He also argued that ES6 has static type checking (perhaps as a trick question).

The last interview consisted of the same repetitive questions and inquiries about my workflow and latest accomplishments. Most of his questions were based on my previous answers, and it felt as though he was seeking negative responses (e.g., Q: "But why did you choose this framework when the previous app was written using that framework?" A: "Because it felt right for that specific project and in that context.").

On the third and last visit, I had two interviews.

The first was with a developer who gave me some tests on paper using pseudocode. Initially, I thought he would ask more JavaScript-related questions. However, the questions were basic computer science queries about data structures, algorithms, and Big O complexity.

Even though the questions were easy, the position was for a front-end engineer who builds standard UIs, not a back-end developer, a game developer, or a computer scientist.

Anyway, at least they didn't ask me to invert a binary tree on paper, because I would have simply turned the page over.

The second interview again covered my work process, "what would you do..." scenarios, and Agile/Scrum topics.

After seven interviews, they rejected me, and I lost two vacation days. However, I realized that this might not be the best place for me.

Describe event delegation.

Describe the module pattern.