This article is primarily based on what you should and should not do in the technical Interviews and how a person should be preparing for the interviews. There are many questions about whether what should be prepared in order to crack a technical Interview.
First and Foremost: The interviewer is looking for a guy who can code a little and have done some projects during their college tenure. Have some projects to show that you are passionate about something.
What you should prepare for the Technical Interviews:
- How to answer technical interview questions ↑ A common mistake candidates make when answering technical questions is to provide an unstructured answer. In this next section, we’ll walk through two step-by-step approaches you can use to avoid that pitfall — one for Technical explanation questions and one for Algorithm questions.
- Sep 20, 2018 Getting an interview call for your dream job is another step in the right direction. However, it is not the end of the road as you still need to crack that interview. In this blog, we look at some important interview skills that can help you ace the interview and get the job. So, let us see what are the most effective interview skills!
Jul 28, 2018 Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. What will TCS ask Mechanical Engineers during technical interview? 16: 5th August 2018 02:22 PM: How should I crack the B.E Mechanical engineering via campus interview? I am a mechanical engineer: 1: 23rd August 2015 09:44 AM: How to prepare for the interview of Mechanical Supervisor Trainee? What questions are asked in the interview?
For Product based companies:
step1->step2->step3: All the steps are Linked List, now you know that you can’t skip over a step to get to another. [;-)
Until and unless you are familiar with skip lists
Until and unless you are familiar with skip lists
Step 1. Good grasp over Programming Language: Gain good knowledge of a programming language. C, C++, Python, Java are some of the best programming language to start with.
Step 2. Data Structures: Array, Linked List, Stack, Queue, Binary Search Trees, Hash Tables are some of the fundamental data structures you should study. Most companies will limit their questions to these data structures and most interview questions are very basic. Implementation of data structures will give you a good grasp over pointers if implemented in c, and oops in python.
Step 3. Algorithms: Algorithms play a vital role for product based companies and a student should at least be familiar with the basic Algorithms like implementation of Searching, Sorting, and should be familiar with the graph, dynamic, greedy approach of the algorithms. Algorithms are really easy and should not be a problem.
** Projects: You should go over the projects you have done during college as some companies even have separate project rounds and if not, the technical interview would be about your projects for around 30% of it’s time.
Additional Things to know: Good knowledge of operating system and oops would be helpful in technical interviews. Companies like adobe ask questions from operating systems, cadence ask questions of oops in written tests.
Know that:
>They are not gonna look for academic records as they know that these things don’t matter much to them
>They are always gonna ask you questions from data structures and algorithms even if they may make you work on something else as these are the backbones of everything.
For Example:
>Van Emde Boas algorithm is the reason behind the very fast routing in network
>Breadth First Search Algorithm is behind searching of a content on a webpage
>Graphs are behind the Google Maps Implementation
>I think that Dijkstra as well as Max Flow, Min cut Algorithm is used in the Google Maps
>I think that Persistent Data structure is the structure behind the Github
>Searching and sorting are the algorithms you see everyday in life
>Stack is behind the Undo i am doing while writing this article
>Runway Reservation system works on the Binary Search Trees
>Van Emde Boas algorithm is the reason behind the very fast routing in network
>Breadth First Search Algorithm is behind searching of a content on a webpage
>Graphs are behind the Google Maps Implementation
>I think that Dijkstra as well as Max Flow, Min cut Algorithm is used in the Google Maps
>I think that Persistent Data structure is the structure behind the Github
>Searching and sorting are the algorithms you see everyday in life
>Stack is behind the Undo i am doing while writing this article
>Runway Reservation system works on the Binary Search Trees
**Just remember that if there are around n**n problems in the world, there are algorithms only to solve n problems and they are looking for someone to work on them along with them
**Everything you see has an algorithm working behind it
How To Crack Mechanical Technical Interview Video
For Service Based Companies:
1. They would be looking for someone with Good Communication skill as they are client based.
2. They would ask easy questions on Data Structures and Algorithms
3. They are gonna look for a good academic record
4. Prepare for Project related questions
5. Prepare for dbms(normalisation), sql
6. Prepare for English comprehension for the written test
2. They would ask easy questions on Data Structures and Algorithms
3. They are gonna look for a good academic record
4. Prepare for Project related questions
5. Prepare for dbms(normalisation), sql
6. Prepare for English comprehension for the written test
Just Remember:
In Product Based Companies:”You won’t be a jack of all trades, but master of one”
In Service Based Companies:”You will be a jack of all trades, but master of none”
Some Tips:
Learn by building: I got a good grasp over C++ by building a game in Unreal Engine
Stay Hungry: Don’t be limited to the things which can be asked in the interview.
How To Crack Mechanical Engineering Interview
Simplify things: There are a lot of things which may scare you as you may be seeing the advancement in recent years but remember that all those advancements are simple algorithms which are executed differently by different people. Just remember that there is always a simple explanation for every thing there is
For Example:
> You may be thinking that there are a lot of data structures and it’s gonna be hard to learn them all but know this, there are only two data structure models:
1. Word Ram Model: Array, Stack, Queue, String
2. Pointer Model: Linked List, Trees
2. Pointer Model: Linked List, Trees
There is always a simple and easy explanation to all the technologies in the world, just be patient enough to get to that point when it all starts to make sense and looks easy.
Resource:
MyCodeSchool Video Channel
MIT Algorithms free course
Practice for cracking any coding interview
MyCodeSchool Video Channel
MIT Algorithms free course
Practice for cracking any coding interview
Recommended Posts:
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to [email protected]. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the 'Improve Article' button below.
Technical Interview is one of the easy phases to go through in a company’s recruitment procedure if you approach this the right way, otherwise it can be one of the toughest obstacle to overcome. I have seen people struggling in Technical Interviews for so long and then I’ve seen only some of them getting selected in the end. That’s why this article is to help you understand what any company seeks in interviewee while they are conducting Technical Interviews.
Here are the steps you need to follow in order to get through this phase with flying colors:
- Do background search : This is really important step that you do background search about the company before sitting in the interview. This will help you learn what kind of questions that particular interviewer would ask. Let’s get this straight that every company has a type of question that they ask and more often than not, these questions are repeated and that’s why doing a background check is useful about any company’s interview. For example, you would not like to study dynamic programming a day before interview if the company always asks questions about DBMS or OS in their interviews.
- Utilize your time : When you get shortlisted for the interview, usually there is not a lot of time remaining from that time to the actual interview, so utilizing your time is really necessary. After doing background search, if you think you are good at the topics that any particular company asks, then search for hot questions on that topic. For example, 20 most frequently asked queries in SQL in interviews. There might be a topic in which you will be good and another in which you feel rusty. In that time, never revise the “good” part but focus on the “rusty” part and prepare that only. Because when asked a question about some topic in which you are good, you will generally find a way to give a right answer.
- Right Answer vs Right Attitude : There is a misconception about interviews that if you want to get selected, you must give all the question’s answers. But often the interviewer checks your attitude about how are you handling the question. Even if you get 5/10 answers correct in a right attitude, you will get selected in the end. Now what i mean by right attitude: When a question is asked to you, do not answer right away, even if you have faced that question before. Act like you are hearing it for the first time and then put your thinking cap on. Take a little time to revise the solution you are trying to give. Usually even if you get closer to the answer rather than actually arriving on the exact answer is good. Do not give up so quickly but at the same time, try to give at least some answer in max 3-5 mins, if you can’t do that, straight away tell the interviewer that you can’t solve this question that will give time for another question for him/her to ask that you may answer.
- Think out loud : Suppose you are given a coding question in which you have to write the code. After interviewer has given you the question, you take your time and in about 10-15 mins, give your answer in the paper. This approach is wrong! While solving any coding question, it is important to think out loud, that means telling the interviewer what your approach is to solve that problem, what you are thinking at particular moment when you are stuck. For example, “I have got a solution but now am thinking how to optimize it and do it in linear time” rather than thinking silently. This will show your explaining skills that most of all companies seek.
- Give a right logical algorithm when you can’t code : In interviews, you may face this situation that you know the logical algorithm to solve a problem but can not quite code entire answer in a language. This may be due to lack of implementation skills but in an interview, there is no time to improve on that. In that case, you can simply say the interviewer “I do not know the exact code but I can write the algorithm or pseudo code for the problem”. Failing to do this, interviewer will think you have less problem solving skills but in truth you have less implementation skills, and most companies do not focus a lot on the latter one.
- Keep it clear : When you are paper coding in an interview, it is important that you keep the sheet clean and readable rather than cancelling a lot of portion of the code in between and writing it in the end, etc. You have to make the job of interviewer easy, so write code only when you are sure that it is right. There are no backspaces when actually writing with pen. You can master this trait by practice.
- Last but not the least: Stay cool In my personal interview experience I was told to find 10 data inconsistency and 5 inaccuracy problem in a database of 200 tuples and 12 columns in 120 seconds. The interviewer literally started a stop watch from his phone in front of me. These kind of questions are to test your stability in pressure situations. Be prepared for such tasks and keep calm in these situations. Getting hyped up is not going to crack it for you. Be confident, maintain eye contact and a smile throughout the interview.
So, that is how I think anyone needs to prepare and behave for Technical Interviews.
I took part in my college’s placement procedure and I have given technical interviews in 2 companies 1) HSBC Technologies India(SDE) 2) ZS Associates(BTA) and have got selected in both of them. Cracking Technical Interview is not a tough ask and I hope this article provides enough information to do it.
I took part in my college’s placement procedure and I have given technical interviews in 2 companies 1) HSBC Technologies India(SDE) 2) ZS Associates(BTA) and have got selected in both of them. Cracking Technical Interview is not a tough ask and I hope this article provides enough information to do it.
Related Article : Practice for cracking any coding interview
How To Crack Mechanical Technical Interview Questions
Attention reader! Don’t stop learning now. Get hold of all the important DSA concepts with the DSA Self Paced Course at a student-friendly price and become industry ready.
Recommended Posts:
How To Crack Mechanical Technical Interview Letter
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to [email protected]. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the 'Improve Article' button below.