Entrevista Técnica: Teve perguntas sobre clean code, code review, dia-a-dia do desenvolvimento, como funciona o DOM e virtual DOM, como funcionam alguns hooks no react, como funcionam funções assíncronas e algumas perguntas sobre js, a diferença e como faz os teste unitário, integração e sistema. Também teve perguntas sobre micro front ends.
Island count in two dimensional matrix. Every 1 is a land and every 0 is water. If two 1s are beside each other, then it's considered as one island.
Check if matrix is word square (check [i][j] === [j][i])
questions on projects in my resume
1. System design 2. HR 3. Java coding 4. Algorithms solving 5. Deep dive into one of previous projects 6. Career and Work Experience Interview
Even though it was a front-end role, it was a general language agnostic coding question similar to leetcode. The question was regarding changes in strings and using data structures to find the longest chain of changes.
The interview was coding a simple HTML parser.
Although I didn't formally sign an NDA I did agree to not talk about details on blogs or forums. That said I can only discuss in general terms. The questions were really not what I was expecting. There were two questions and neither of them required data structures or even an algorithm. Really just a standard coding question requiring some logic, analysis, and OO design but nothing fancy. Alas, for reasons beyond me the interviewer did not like how I answered the questions. Google does not provide any feedback on why you were rejected beyond a standard copy/paste response from the recruiter. On a side note- the interviewer didn't ask a single question about me or seem to care in the slightest. "Just another day, another interview" kind-of attitude. Which I guess is to be expected from them, but kinda depressing from the interviewee perspective. Afterwards I went through the interview minute-by-minute in my head and tried to guess what the interviewer was looking to see. Obviously it's a lot easier to come up with a great design when you are not under pressure. So no pearls of wisdom from me how I would do it differently since I felt I was very well prepared. I guess it's partially the luck of the draw, and the mood of the person doing the screening. When they have the full day of interview at least there needs to be a consensus from several interviewers. In the screening stage you get only one chance and one persons opinion to get you through the door.
Quite a few questions on time complexity, one question on organizing columns of information and creating a CSS view, questions about linked lists and tree traversal, explain how the internet works, etc.
Quais ferramentas e tecnologias você domina que são relevantes para esta posição?
Viewing 271 - 280 interview questions