The backbone of the client is rendered with `haml` and a Vue instance is attached to it. The task was a bit obfuscated, and as it turned out later there were 2 parts to it: 1) The HTML was awfully syntactically wrong, and that was the first opportunity to make comments and improve the code. 2) There was some vanilla JavaScript in the Vue file that needed to be converted to Vue. I missed the second part in my preparation to the interview and that was the reason I failed. I got nervous --> froze during the interview and I wasn't given a second chance. 15 minutes after the interview ended I realized what I did wrong, corrected everything and made some suggestions, fixed the unit tests and the failing CI pipe, but there was no reply on my actions/email and I felt like I was cut off cold turkey with no feedback from the tech lead a t all. Now, that's a bit harsh.
Frontend Developer Interview Questions
13,273 frontend developer interview questions shared by candidates
- Add some feedback and questions to the document - complete/fix the code to match the mocks
Come mai hai cambiato molte aziende?
To write an event emitter
What is the tech stack at your current job?
How would you implement an input field
Const, var, let different? Promise related questions Question around your presented project
Tasks: OOP knowledge , currying, logic
UI coding question: print a navigation menu with categories and children using your framework of choice. You will need a recursive solution. How would you highlight only the "active" item and expand only the path that contains the active item. JS question: implement a JS solution for fetching/reading feature flags from an API. How would you improve performance, caching, share across different apps,... Systems design: jira active sprint board, what components would you use, how would you optimize the FE loading of thousands/millions of jira tickets, how would you measure performance. Advice for the company: although the process is great, I don't think it's great for a full-stack developer. Also, I felt I was not explicitly asked or guided around some things I was expected to talk about but apparently I didn't. Advice to candidates: a lot of emphasis around not just giving a solution but presenting alternatives with pros and cons. Speak your mind.
1. browser coding - tree structure 2. JS coding - implementation based 3. system design - straight forward design a product , more focus on frontend 4. Hiring manager - how did you handle conflicts?, past experiences, projects etc 5. Values - scenarios based questions to check if the candidate aligns to company values
Viewing 371 - 380 interview questions