thinkocode

  What is your biggest weakness? Do not say something like, "Oh well, I am a perfectionist.." kind of things. Be genuine. Tell them what really is your weakness and how you have tried to improve it. This will make them feel that they can trust you. Embody, for a moment, the interviewer's point of view. If you were the interviewer yourself, wouldn't you like a candidate who accepts his/her weaknesses and tries his level best to improve?  Any questions for me? Before preparing these questions, make sure the center of all your questions should be on the company (or the interviewer). Mention things that they have already mentioned, which makes them feel unconsciously that you are very attentive and interested in them.  For example, What were the mistakes you did at the start of the job and how did you rectify it?  How much growth or improvement have you seen in this company since the day you started?  Where do you see this company going in the next 5 - 10 years...

  Tell me about yourself? Keeping in mind the four wild cards strategy, subtly try to change the direction of the interview in your favor. Frequently mention things that you want to get asked, maybe your recent project that you are very confident of. Try to showcase your efforts and struggles in releasing a project or a goal. Give hints/triggers to them to one of your success stories, so that they get to ask more about them, and you get to show off your success story. Every other participant would talk about their skills. What will you do or say that will make you stand out? Always walk through those four wild cards . Why us? This is the most common type of question you might get asked in almost every interview you attend. While answering this question, always try to make the interviewer or the company feel special. You want to repeatedly answer the questions in such a way that you stand out from the rest of the candidates.  Do enough research on the company and impress ...

  Three Key Questions As discussed earlier ( here ), always think in terms of the interviewer's point of view about the whole interview process. This whole perspective of theirs boils down to just these three questions.  1. Can you do the job? 2. Can I work with you? 3. Are you going to improve? You need to prepare accordingly before sitting for an interview.  To answer these three questions, we will use the Four Wild Cards Strategy. Four Wild Cards The crux of your whole identity and perception lies in these four cards - Technical, Success, Leadership, and Challenges. Technical  This includes your technical skills, knowledge, and experience. You don't have to spend time really preparing for it before the interview, as, you have already all the technical skills required for that job position, if not, well, you are not quite eligible for that job yet.  Success Make a list of all the note-worthy successes you have achieved. Do not directly pinpoint them i...

It seems like you are at that point in your life where you would have to "sell yourself" in order to make a career. You would be nervous and anxious too, imagining these interviews, right? Don't worry, you only require a shift in your perspective on the interviews to get you going.   Mindset   Before sitting in an interview, read out this blog once again. 1. Let yourself know that it isn't only you that is in utter need of something. Even the interviewer needs an eligible employee for their company. Immerse yourself into the role of an interviewer for a few minutes and think about the whole situation from their point of view.    2. When you really understand that it is not only you that needs something from someone, you realize that this is not the only company that can provide you what you want. Just like there are many candidates applying for a job role, there are many companies too, looking for a skilled-eligible employee. This is not your only chance....

Here's a quick problem for you. Given two sorted arrays, merge them such that the resulting merged array is also a sorted one. For example, let array A be [2,4,6,8] and array B [1,3,5,7,9]. The result should be [1,2,3,4,5,6,7,8,9].  Did you get it right? If not, no problem at all. Let us first try and think about how we would approach this problem. The very first step our minds could think of would be to apply a loop and merge them into the array one by one, and then sort them. Right? But think about the time complexity now. What will be the time complexity if we go about this approach? First, O(n1+n2) for traversing each element of both the arrays, and then O((n1+n2)^2) (because a simple sorting algorithm has a Big O time complexity of O(n^2)). Think of a better approach. One way could be to initialise two tracking keys or variables to traverse both of these arrays (variables i and j here). Start from the zero position. If an element of array A, at that particular posit...

Introduction Arrays are the most simple and most accessible data structure to learn and implement. They are simply a collection of data (of similar datatype usually) stored sequentially in memory. The index of an array is nothing but an integer value that indicates the position of each element in that array. Indexing in C++ starts from 0. Credits :  https://www.guru99.com/array-data-structure.html Think of an array like a well-built, organized bookshelf. All the books on that bookshelf are well placed according to their genre, just like all the elements in an array are of the same data type. You can find your desired book based on the position(index) of that book on the shelf. You can simply insert a book in a row already filled with some by finding the position where you want to insert it. Similar is the case with removing a book.  The Big O of such operations are:  Do not worry if you don't intuitively understand them. We will build our very own array data struct...

What is a Data Structure? Data structures are simply the different types of structures of the container in which colossal data is to be stored. Consider this analogy of storing food items. For storing fruits, you require a different storage box, for storing packaged food, maybe you need a huge container. For storing different types of items you require some container made for that specific item. Similar is the case with the data. For different types of data, depending upon their use cases, we implement different types of data structures to store them. Each data structure has its own limitations and advantages depending upon the data we are storing just like how we store food.  And therefore, a great software engineer isn't the one who only knows how to make the container, but he/she is the one who knows when and why to use a particular container (data structure) for a particular use case. Relating this to our analogy, the one who uses baskets to store wheat is naive, and t...