Interview experience at Google - SDE II
Tags: javascript, discuss, google, interviewexperience
Published: 2022-06-19 15:36:47

It was my first time getting an interview at any FAANG company. The position was for SD II Fullstack Developer Bengaluru | Hyderabad | Remote.

After the phone call with recruiter he schedule the interview 1 month after so I can have a little time to prepare for DS and Algo. Although I never took DS and Algo seriously and had a little idea about these topics.

**First Round:**
It was a 45min Technical Interview round. I was asked 2 question and I was able to solve those Problems as these was easy problems [as feedback says It was warm up round].

I was Rejected and given **Boundary Line** candidate feedback. I asked recruiter and he gave me detailed feedback where I missed and also the feedback of the person who took my Interview that where I was lacking.

**Mistakes I made**
*  I was able to solve the first problem with optimal solution but Time complexity was wrong also made some trivial errors. Nervousness le dubi 😥.
*  I was able to come up with solution but Unable to code as time limit exceed.

> Although I though I did very good but It was not even enough. Will have better luck next time.

**Questions**
As per the guideline cannot share the exact questions but I will mention the type here.

1. Was related to string validation [Leetcode easy].
2. Something similar to generic language translator. [Leetcode medium].

**Feedback:**
* **Coding:** Borderline: able to map simple algorithm to code but made one or more non-trivial errors. Did not check all boundary conditions. Did not take advantage of well established language constructs and data structures.
* **DS and Algo:** Borderline: Marginal understanding of common data structures. Resulted in some significant errors in solutions or a generally inefficient solution. Able to implement and analyze a naïve algorithm well, but unable to improve on that solution.
* **Design:** Borderline: Designed a solution, but for incorrect problem or missed significant requirements. Did not use a sound problem solving approach (ex. didn't consider alternative or tradeoffs. )
* **Efficacy:** Borderline: Work pace was slower than expected for the complexity. 

>I was able to improve my solution but only after prompting by interviewer so never wait for him to ask, just tell him if he wants an optimal solution ?.
>Most candidates gets to coding stage but I was able to only get to planning stage in second question.

**Note:** 
* Always tell interviewer about your approach and its time complexity even if he didn't ask, also Ask him that if he wants you to have optimal solutions again even if he did not ask. 
* Never jump directly to coding even if you know the answer just clear the approach and TC to him then ask for to implement.
* Ask as many question you can to clear the understanding of problem
* Do not miss the edge cases [these were the trivial errors I made]
* Understand time complexity thoroughly.
* Do not be nervous. [I was and made trivial mistakes which I realize after interview like: the time complexity].

> My advice to you all, go to the interview with no expectations, don't let thoughts about failure get in the way of your own success. Keep your mind free, this is much easier said then done. `from: @helloKali `

&nbsp;
cover image is taken from google search:

Thanks for reading and best of luck ✌️