Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Interviews Peepaal - Preparing to Succeed
  2. 2. What does company look for? <ul><ul><li>Strong ability to learn </li></ul></ul><ul><ul><li>Passion for technology </li></ul></ul><ul><ul><li>Intelligence </li></ul></ul><ul><ul><li>Willingness to work hard </li></ul></ul><ul><ul><li>Strong technical skill </li></ul></ul><ul><ul><li>Raw talent </li></ul></ul><ul><ul><li>Self-confidence </li></ul></ul><ul><ul><li>Adaptability and Flexibility </li></ul></ul><ul><ul><li>Honesty and Integrity </li></ul></ul>
  3. 3. What to expect and wear <ul><li>W hat to expect at the day of the interview? </li></ul><ul><li>During the interview you can expect to meet with one Technical Interviewer/Panel and one HR Interview. </li></ul><ul><li>  </li></ul><ul><li>What to wear at the interview? </li></ul><ul><li>While some companies do not mind casual wear, be safe and wear formal clothing. Suits are not necessary, as the interviewers will be wearing casual attire. Wearing Jeans and a T-shirt indicates that sufficient respect or seriousness for the interview so stay clear of that. A standard technical interview outfit consists of non-denim cotton pants, a collared shirt and shoes(no sneakers). </li></ul>
  4. 4. Coding Questions <ul><li>What will the Coding Questions be about? </li></ul><ul><li>For Coding Questions: You should be ready to code during your interviews. Make sure that you brush up on your C/C++ skills before you come, as interviewers love to ask questions related to linked lists, loops, arrays & pointers, etc.  You might get a basic algorithmic-type problem you solve on paper with a pen/pencil. Before you go for the interview make sure you are very comfortable with the programming language that you choose. </li></ul><ul><li>  </li></ul>
  5. 5. Coding Questions : Tips <ul><li>Make sure you write your best code that you will ever write, keep in mind the code you write will be the only code the Interviewer will ever see. If you write ugly code the interviewer will assume you always write ugly code. </li></ul><ul><li>Generally you can choose your language while coding, try to come up with a simple design in a fairly short amount of time, rather than trying to incorporate too much and making the code unnecessarily complicated. Always double check for errors and bugs, before handing it over to the interviewer. </li></ul>
  6. 6. Approach is measured <ul><li>Keep in mind that the interviewer wants to see the thought process throughout the interview. Keep the problem solving process interactive if you have any questions or problems. At the same time the less the hints you need the better it is. </li></ul><ul><li>The process should highlight your ability for problem solving, logical thinking and communications for eliciting requirements. </li></ul>
  7. 7. Do not dismiss the question <ul><li>For example if you are given a problem like this &quot;Write a function that determines if two integers are equal without comparing them&quot;. This is a silly and contrived problem. You might want to answer &quot;That is a stupid question&quot;. </li></ul><ul><li>You would flunk if that is the answer. </li></ul><ul><li>You need to answer the question as it has been asked. You could for example if you are forced to use a hash table for a problem say &quot;This might be much easier with a binary search tree to extract the largest element but let's see how to solve this with a hash table&quot;. </li></ul>
  8. 8. Ask clarify questions <ul><li>You can't solve the problem if you don't understand it. Often there are hidden assumptions and you can't demonstrate your skills if you don't understand the problem. Don't hesitate to ask questions about the problem and don't start solving it until you understand it. </li></ul>
  9. 9. Steps to follow - Use Example <ul><li>Once you understand the problem, always start with an example. This will highlight methodical and logical thought process. Examples are also especially useful if you don't see the solution right away. </li></ul><ul><li>  </li></ul><ul><li>  </li></ul>
  10. 10. Steps to follow: Algorithm <ul><li>After the example focus on the algorithm to be used to solve the problem. This may require some additional examples and will take some time and is expected. Make sure you communicate your progress to your interviewer instead of blankly staring at the whiteboard. You can mention the approach that you are using and this could lead to some hints from the interviewer. </li></ul><ul><li>After you figure out your algorithm explain your solution to the interviewer, this gives him an opportunity to evaluate the solution. he may then give a go ahead to start coding or give you some more inputs. </li></ul>
  11. 11. Steps to follow: Test your code <ul><li>Test your code before saying you are done! </li></ul>
  12. 12. Non Coding Questions <ul><li>For resume/non-coding questions: Expect ‘Experience’ or ‘Behavioral’ questions which are open-ended questions about your past experiences, jobs and projects.  Be specific, answer what was meaningful about the experience and what you learned.  </li></ul><ul><li>Don’t practice too much, try to keep the answers natural, make sure that you have captured the key points Also, keep it short, but make sure that you have covered what you wanted to. </li></ul>
  13. 13. What better Candidates do <ul><ul><li>Diagrammed the problem clearly </li></ul></ul><ul><ul><li>Asked clarifying questions before writing code </li></ul></ul><ul><ul><li>Considered the consequences of every line </li></ul></ul><ul><ul><li>Checked their work without being prompted </li></ul></ul><ul><ul><li>Proved that their code was correct by trying different inputs </li></ul></ul><ul><ul><li>Self-tested their code </li></ul></ul>
  14. 14. Things to Avoid in Interview <ul><li>Don’t linger on the good or the bad, don’t talk too much or ramble, don’t hide your thought process, especially for coding questions and don’t forget you are interviewing your employer too, so make sure to take the time and know them and ask them any questions you have about the company, the products, the job etc. </li></ul>
  15. 15. Can i be asked Brain Teasers? <ul><li>You will also come across some problem solving questions (like brain teasers or puzzles) so be sure you fully understand the question and take a few seconds to think about the problem & ask clarifying questions before jumping in!  </li></ul><ul><li>Interviewers like to ask ambiguous questions, so when in doubt; ask plenty of questions to be sure you fully understand the problem before jumping in to a solution.  Also what the interviewers are looking for here is your approach, rather than the correct answer. Thinking aloud might help! </li></ul>
  16. 16. Who is a Qualified Candidate <ul><li>Someone that has very strong abilities to write code in C/C++ Someone that is very driven and passionate about technology, desiring to make software products that will go all over the world Someone with fluent English speaking skill </li></ul>
  17. 17. References <ul><li>Development: Code Complete by Steve McConnell Writing Secure Code, Second Edition by Michael Howard, David C. LeBlanc Coder to Developer: Tools and Strategies for Delivering Your Software by Mike Gunderloy, Sybex. </li></ul>