Sir pls send me technical interview question in mechanical eng pdf. Gowtham says: January 16, 2017 at 8:03 pm sir pls send me technical interview question in mechanical eng pdf. Plz help me to crack mechanical interview in production plz. Gurunath says: July 3, 2016 at 6:40 pm Thank u Sir Please send me in pdf format to my e.
- This question, How To Crack Technical Interview For Freshers and Experienced Software Engineers? Was asked on my Live Session on Musings with Software Engine.
- How to crack any Technical Interview? 0 Answer(s) posted Write an answer 688. Recommended Questions. How to crack any Technical Interview? Explain the procedure to design the digital IIR filters? Recommended Files from Library. JNTUH R16 B.TECH MECHANICAL ENGINEERING III YEAR COURSE STRUCTURE AND SYLLABUS COPY. JAVA PROGRAMMING.
- Tips to Crack the Campus Placement Interview How to prepare for campus placements engineering, Software Companies. Content on CV can result in leading questions to technical and practical questions during interviews. This will allow you to direct the interview to a certain degree and present yourself in a positive light.
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.
We round up the 131 best Mac games available in November 2020, from real-time strategy and RPGs to racing, shooting games and puzzles, together with links to buy at the best price - Page 10. Best free racing games for mac. Spectra: This twitch racer showcases one of Chipzel's latest albums, allowing the player to.
Related Article : Practice for cracking any coding interview
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:
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 questions are common in product manager interviews at companies like Google, Microsoft, and Amazon. For instance, your interviewer might ask, 'How would you explain cloud technology to a five-year-old?” These questions can feel really unsettling at first.
But the good news is that if you know how to approach them they can become fairly easy to answer. So, let's step through our suggested methods for answering technical interview questions as well as some examples to help you prepare for your interview.
Here’s an overview of what we will cover:
- How to answer
1. What technical questions can you expect in PM interviews? ↑
Product Managers work with engineers to build software products. PMs don't need to be developers but they need to understand how technology works. This is why companies like Google and Amazon ask technical questions in PM interviews. There are two types of technical interview questions: Technical explanation questions and Algorithm questions.
Employers use Technical explanation questions to assess the extent of your technical knowledge and your ability to communicate that knowledge simply. For instance, you could be asked, “How does the internet work?” Interviewers are looking for a summary that’s easy to understand, and might also follow up with questions to see how deep your understanding of the topic is.
Tech companies use Algorithm questions to test if you can think like a developer. For example, an interviewer might ask, ”How would you design a method to identify if a number is prime?“ Note that you’re only likely to be asked this type of question if you have a technical background. Your interviewers are mostly interested in how you think when they ask these types of questions. They will therefore only expect you to write pseudocode, not production-level code.
2. 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.
2.1 Technical explanation questions↑
Technical explanation question example:
“How does the internet work?”
2.1.1 Step-by-step approach: IGotAnOffer Method
We developed the IGotAnOffer method below to help you give a clear and thorough answer to Technical explanation questions. The steps might sound abstract at first but bear with us as the example below will help make them tangible.
- Clarify: Many candidates skip this step and jump straight into answering the question. This is a big red flag for interviewers. Before starting to answer make sure you understand exactly what the interviewer wants you to explain by asking clarification questions. In addition, if the topic you were asked about is extremely vast you will need to narrow down and focus your explanation on the most important aspect of the topic.
- Explain step-by-step: Next, you should explain the technical concept step-by-step. When possible, use a metaphor to communicate your understanding of how it works. In this step, it’s ok to ask your interviewer for some time to structure your thoughts before delivering your answer.
- Conclude and discuss: Finally, you should provide a summary of your explanation. At this point the interviewer will most likely critique your explanation, which is perfectly normal. They might continue to ask for further details to assess the depth of your understanding. Some interviewers will also keep on asking questions until they reach a technical area which you don’t master. If you don’t know something you should therefore admit it.
2.1.2 Example question with answer: How does the internet work?
Now that you know how to approach Technical explanation questions, let's look at an example.
Try answering the question below by following the method described above. Play both the role of the interviewer and candidate. Leave a comment at the bottom of the blog post with your answer. This is a great opportunity to gain some practice for your PM interviews.
The key is to answer each question without seeing other people’s answers. To do so, scroll down directly to the bottom and leave your answer before reading other candidates’ proposals.
Try this question:
“How does the internet work?”
Answer
Below you will find our proposed answer to the question. Before taking a look at it, make sure you go to the bottom of the page and answer the question by yourself in the comments section. There are only so many opportunities to prepare for technical interview questions!
Step one: Clarify
The Internet is a complex system with many features and we can’t realistically explain how all of it works in an interview. It’s therefore a good idea to clarify with the interviewer what specific features of the Internet we should focus on.
To reduce the scope of our explanation, we might say something like, “The internet is composed of many complex elements. I could talk about network connections, blockchain technology, specific web services, etc. But the most fundamental feature of the Internet is probably that websites can be accessed by typing a URL in a browser, so this is what I suggest we focus on. Is that what you have in mind too?”
Step two: Explain step-by-step
Let’s imagine the interviewer agrees that we should explain what happens when someone types a URL into the address bar of a web browser.
A this point, we would ask for a few seconds to gather our thoughts and to list the high level steps of what happens when a user queries a website. Once you’ve laid out your thoughts you can start walking the interviewer through the different steps.
When a user queries a website there are four systems involved:
- The device on which the user is typing the website’s URL. This is often called the 'Client'
- The DNS resolver which is going to help us find the IP address of the website based on its URL
- The Server, from which we need to get the website data that needs to be displayed
- The Internet which manages communications (e.g. queries, data, etc.) between the Client and the website’s Server
Here is what happens step-by-step:
- The Client browser uses the URL (e.g. example.com) to find the website’s IP address, which is either stored in local memory or found with a DNS lookup. Let’s use a metaphor for a second. A DNS resolver is like a big phone book matching URLs and IP addresses. If you wanted to call “John Smith” on the phone first you would need to find his number in the phone book.
- Next, the browser uses the IP address and queries the Internet for the website’s data. This is like if you dialed John Smith’s number, the phone company would make a connection between your phone lines.
- Then the website’s Server sends appropriate data (e.g. an index.html file) back across the Internet. In our metaphor, when John Smith answers and says hello, his voice is translated into an electronic signal that’s passed through the phone lines.
- Finally, the website’s data reaches the browser, which then displays a visual interpretation of that data. This is like your phone’s speaker turning the electronic signal into John Smith’s voice again.
Step three: Conclude and discuss
We would conclude by saying something like, “So, typing a URL into the address bar of a browser works a lot like making a phone call. Information is transferred back and forth between two connection points. Also, the transferred information needs to be interpreted by the receiver.”
Let’s imagine the interviewer is looking for more detail and says, “That’s an interesting explanation, but you glossed over DNS lookup which is a really important factor of the process you described. Can you explain more about that?”
Once again here we could ask for some time to list what happens step-by-step when a DNS resolver tries turning a URL into an IP address. Let’s assume we know a lot about how DNS resolvers work. Below is the information we would walk the interviewer through.
There are four major types of servers involved in DNS resolution:
- The Resolving name server receives the URL from the Client and is expected to send back an IP address. To find that IP address the Resolving name server communicates with three other servers: Root servers, Top Level Domain (TLD) servers, and Authoritative name servers.
- Authoritative name servers provide the IP address of specific websites (e.g. www.example.com). However, there are many Authoritative name servers, and the Resolving name server does not know which one to contact to find the IP address.
- A TLD server can point to the Authoritative name server of any website that ends with the particular domain extension it’s responsible for. As an example, a ‘.com’ TLD server stores the location of the Authoritative name server for all websites that end with ‘.com’. However, the Resolving name server does not know the location of the TLD server it needs to contact when it begins searching for the IP address.
- A Root server provides the location of TLD servers. The Resolving name server always knows where to find Root servers. So, contacting a Root server is the Resolving name server’s first step when searching for the IP address it’s trying to find.
Here is how the resolution works step-by-step:
- The Resolving name server queries a Root server, which points to the appropriate TLD server. Let’s use our phone book metaphor again. When calling John Smith, we would start our search for his number in the phonebook by deciding between the yellow pages for business numbers versus white pages for personal numbers. This is what the Root name server does for us.
- The Resolving name server then queries the appropriate TLD server, which points to the Authoritative name server. This would be like using the category and alphabetical sorting of the phonebook to find the specific page that lists all the “Smiths.”
- The Resolving name server then queries the appropriate Authoritative name server, which will provide the website’s IP address. There could be a lot of “John Smiths” listed in the phonebook, so you would use street addresses to determine the exact phone number for the specific John Smith you’re trying to call.
The interviewer interrupts and asks, “Another important element related to DNS is caching — can you explain how that works?”
At this point let’s assume we don’t know anything about caching, so we would say something like, “That’s really interesting, but I’m not sure how caching works in DNS processes. I would need to look into it a bit more to give an accurate answer.”
Remember, interviewers are likely to ask follow up questions until they reach the limits of your knowledge so it’s ok to say when you don’t know something.
2.2 Algorithm questions: IGotAnOffer Method↑
Algorithm question example:
”How would you design a method to identify if a number is prime?”
2.2.1 Step-by-step approach: IGotAnOffer Method
We developed the IGotAnOffer method below to help you give a clear and thorough answer to Algorithm questions. The steps might sound abstract at first but bear with us as the example below will help make them tangible.
- Clarify: Many candidates skip this step and just start writing code. Before doing this, you need to make sure you understand the question correctly by asking clarification questions and playing back what you understood to the interviewer. Doing this upfront is extremely important because you can’t answer the question correctly if your understanding is not accurate.
- Solve an example: Start by answering the question for a simple example. This will help you figure out how to write your algorithm for the generic solution in the next step.
- Write your generic solution: Once you’ve solved an example you should write an algorithm in pseudocode that solves the generic case. You should show the piece of paper you write on to your interviewer or use a whiteboard when possible.
- Discuss your solution: It’s a good idea to finish your answer by sense-checking your algorithm with an example. You should also list edge cases you would want to test your algorithm on but there’s usually no need to run through them unless the interviewer asks you to. Finally, if you have a very technical background, such as a Computer Science degree, the interviewer might also ask about the trade-offs of your code (e.g. memory vs. speed performance).
2.2.2 Example question with answer: How would you design a method to identify if a number is prime?
Now that you know how to approach Algorithm questions, let's look at an example.
Try answering the question below by following the method described above. Play both the role of the interviewer and candidate. Leave a comment at the bottom of the blog post with your answer. This is a great opportunity to gain some practice for your PM interviews.
The key is to answer each question without seeing other people’s answers. To do so, scroll down directly to the bottom and leave your answer before reading other candidates’ proposals.
Try this question:
”How would you design a method to identify if a number is prime?”
Answer
Below you will find our proposed answer to the question. Before taking a look at it, make sure you go to the bottom of the page and answer the question by yourself in the comments section. There are only so many opportunities to prepare for technical interview questions!
Step one: Clarify
First we want to confirm our understanding of prime numbers with the interviewer. The main question that comes to mind here is how prime numbers are defined:
- What exactly makes a number prime?
Let’s imagine the interviewer gives us a few details related to prime numbers. We would then summarize to make sure we understand correctly, and say something like, “So, a prime number is a whole number greater than one, and whose only factors are one and itself. In other words, a prime number divided by any whole number between one and itself (excluded) will produce a remainder.”
Note: If you’re not familiar with the concept of a remainder, one way to think about it is as the fraction left over after dividing. For example, 9 / 4 = (4 / 4) + (4 / 4) + (1 / 4). The number 4 divides into 9 exactly twice with 1 left over. That leftover 1 is the remainder of 9 / 4. A remainder of 0 is produced when there is nothing left over. For example, 8 / 4 = (4 / 4) + (4 / 4). The number 4 divides into 8 twice, and there is nothing (0 / 4) left over.
Step two: Solve an example
First, let’s pick a simple number and think about what we would do to determine if it’s a prime number. For instance, how could we determine if the number 7 is prime or not?
- The first condition is that it has to be greater than one
- The second condition is that when dividing 7 by any whole number between 1 and 7 (excluded) there should be none that produces a remainder of 0
We know that 7 is greater than 1, so the first condition is met.
To meet the second condition, 7 divided by 2, 3, 4, 5, and 6 all need to produce a remainder greater than 0. If dividing by any of these numbers produces a remainder of 0, we know 7 is not prime.
7 / 2 produces a remainder of 1 7 / 3 produces a remainder of 1 7 / 4 produces a remainder of 3 7 / 5 produces a remainder of 2 7 / 6 produces a remainder of 1 |
So, since 7 does not have any other factors besides 1 and 7, the second condition is met and we can conclude that 7 is a prime number.
Note: we don’t need to check numbers larger than 7 as we know it is not divisible by 8, 9, 10, etc.
Step three: Write your generic solution
Now let’s think about how we can generalize this logic. At this point we would start writing out our solution in pseudocode.
Let’s write an algorithm which takes a number N as an input and determines if N is prime or not as an output.
First, we should check if N is greater than 1. If it’s not, we know that it’s not a prime number and our algorithm should return “false.”
Step one: if (N <= 1) return false; |
![Crack Crack](/uploads/1/3/4/6/134669986/507366094.jpg)
Next, we'll need to start at the next integer above 1 (which is 2), and check if there are any other factors between 2 and (N - 1).
In other words, if any of the numbers between 2 and (N - 1) produce a remainder of 0, we know N is not a prime number.
This should work for any situation where N is greater than 2. But, we also know that 2 is a prime number, and if we divide 2 by 2 then we get a remainder of 0, which would incorrectly output 'false' (i.e. not prime) for the number 2. We can solve this by adding a simple step. See below for how we could approach this:
Step two: i = 2; Step three: if (N 2) return true; Step four: N % i = R; Step five: if (R 0) return false; Note: “” is standard notation to test if two variables are equal to each other. And “%” is standard coding notation for a function that calculates the remainder of a division between two numbers. |
This gets us about half way there, but we still need to add something to move us on to the next integer between 2 and N each time the remainder produced is different than 0, until we finally get to N.
Step six: else i++; Step seven: while i < N, go back to step four; |
If N is not divisible by any number between 1 and N (excluded), then N has passed our second condition, and we can confirm it is a prime number.
Step eight: return true; |
The whole algorithm then looks like this:
Step one: if ( N <= 1) return false; Step two: i = 2; Step three: if (N 2) return true; Step four: N % i = R; Step five: if (R 0) return false; Step six: else i++; Step seven: while i < N, go back to step four; Step eight: return true; |
How To Crack Mechanical Engineering Interview
Step four: Discuss your implementation with the interviewer
Let’s now test out our generalized algorithm on another easy number, like 10.
Step one: 10 > 1 Step two: i = 2 Step three: if (10 2) return true; Step four: 10 % 2 = 0 = R Step five: R 0, so return false; |
Our algorithm confirms that 10 is not a prime number, as 2 is also a factor.
Finally, we could call out non-integer and negative numbers as edge cases we would want to test. We might also highlight that we could make a more condensed version of our algorithm by using a for loop:
if ( N <= 1) return false; for (i = 2; i < N; i++) { N % i = R; if (R 0) return false; } return true; |
3. List of sample interview questions: Technical ↑
If you would like feedback on your answer to any of the questions listed here, you can leave your answer below and our team will get back to you. If you'd like to learn about the other types of questions you may face, you can also visit our ultimate guide to product manager interview questions.
3.1 Practice Technical explanation questions
Here is a list of Technical explanation questions that were asked in PM interviews at Google, Microsoft, Amazon, and Facebook, according to data from Glassdoor.com:
- Explain recursion to my grandmother
- What technologies would you use to build a live stream video service?
- Explain the concept of 'protocol' to a 4-year-old child
- What is the difference between C++ and Java?
- Explain what happens when executing mergesort
- When are Bayesian methods more appropriate than 'Artificial Intelligence' techniques for predictive analytics?
- How would you most efficiently store large images in a database?
- Explain the concept of big O notation
- How would you get authentication to work across domains
3.2 Practice Algorithm questions
Here is a list of Algorithm questions that were asked in PM interviews at Google, Microsoft, and Amazon, according to data from Glassdoor.com:
![How To Crack Mechanical Technical Interview How To Crack Mechanical Technical Interview](/uploads/1/3/4/6/134669986/402758963.jpg)
- Design a method that removes every other node from a linked list
- Write a program to randomly shuffle an array of numbers
- How would you output a tree in column sequence from left to right
- Invert the words of a sentence in a string
- Write a function that returns how many digits are in a number
- Take in an unsorted array with duplicates and return it with no duplicates
- Write a function that determines if an array of ‘chars’ is a palindrome
- How can you find and then remove the second to last element in an infinite list?
Now that you have a list of sample questions to work with, it’s important to consider how you will practice with these questions.
4. How to practice technical questions ↑
It’s best to take a systematic approach to make the most of your practice time, and we recommend the following three steps:
4.1 Learn a consistent method for answering technical questions
In this article, we’ve outlined a step-by-step method you can use to solve technical questions. We’d encourage you to first memorize the basic steps, and then try solving a couple of the sample questions on paper.
This will help you to understand the structure of a good answer. This is a good first step, BUT just knowing the method is not enough, you also need to be able to apply the steps in interview conditions.
4.2 Practice by yourself or with peers
A great way to practice the method for solving technical questions, is to interview yourself out loud. This may sound strange, but it’s an excellent way to improve the way you communicate your answers during an interview. Play the role of both the candidate and the interviewer, asking questions and answering them, just like two people would in an interview.
If you have friends or peers who can do mock interviews with you, that's a great option too. This can be especially helpful if your friend has experience with PM interviews, or is at least familiar with the process. You can also find peers to practice with on our new PM mock interview platform.
In addition to practicing by yourself, and with peers, it can be a huge advantage to do mock interviews with experienced PM interviewers.
4.3 Practice with experienced PM interviewers
If you know a Product Manager who can help you, that's fantastic! But for most of us, it's tough to find the right connections to make this happen. And it might also be difficult to practice multiple hours with that person unless you know them really well.
Here's the good news. We've already made the connections for you. We’ve created a coaching service where you can practice 1-on-1 with ex-interviewers from Google, Amazon, and other leading tech companies. Learn more and start scheduling sessions today.
PM Interview Coaching
How To Crack Mechanical Technical Interview Questions
Any questions about PM interviews?
If you have any questions about product manager interviews, do not hesitate to ask them below and we will be more than happy to answer them. All questions are good questions, so go ahead!
Keep reading:product manager interview articles