Once you have cleared the telephonic round for a technical job, you will be called for a personal interview to analyze your technical skills, communication, interpersonal, and problems-solving skills, and to access you as in person in whole. Soft skills are important because you'll be expected to interact with peers, clients, suppliers, and vendors. They won't spare anything until they're convinced to the core that you are the kind of candidates they have been looking for. So honing up your interviewing skills before the 'big day' is crucial. We are presenting top 10 tips for technical interview for you that will calm down your anxiety and boost your chances of selection.
Since they don't want to miss the chance of working with an IT titan, most candidates focus on clearing their complex concepts and logic problems. This drives away their attention from the fundamentals of data structures and algorithms. Or, they believe they are thorough with these essential features of the technical job, and hence divert their focus on tough questions. And when the time comes to demonstrate their fundamentals, they falter. So, along with complex-level concepts, do focus on your fundamentals since you may have to prove yourself as an 'all-rounder.'
Going for a technical interview without brushing up your skills is like going for a date without a wallet. This will put you in an embarrassing situation. Imagine how would you feel when you pick up the tab and find your wallet missing. Won't your date regret going out with you. Similarly, when the interviewer finds you scratching your head to answer a simple question, he or she will start doubting your credibility. Therefore, whether it's a date or a technical interview, go prepared. Brush up your coding and programming skills by practicing on a whiteboard. Ditch the PC or laptop for a few days, and use the whiteboard because most companies don't provide laptops, and ask candidates to solve a puzzle on the whiteboard instead.
Coding exercise is a definite part of a technical interview. So practicing your coding skills is vital. There is a total possibility that you may be asked to write code in more than one language. If you're not sure which language to learn, research the type of projects the company has done. Identify the type of language they use for projects, and practice it. Don't worry about not being able to use the exact parameters. You can at least demonstrate your clarity on loops, functions, classes, etc. by writing reasonable code.
Quite likely, the recruiters will ask many questions to you just to check how you can solve a problem and keep your temperament in check during the activity. Accept it that it's not possible for anyone to answer all the questions of the interviewer. So it's okay not to be able to answer all the questions. But giving roundabout answers is not acceptable. This way, you'll not just waste the interviewer's time, but also annoy him or her. But do let them know how you will be finding the answer and enhance your thinking skill.
One sure-shot question you'll be asked in a technical interview is "Tell me about the technical challenges you faced in a project and how you overcame them." When answering this question, focus on the toughest technical challenges. Give them a brief and precise answer on how you managed the situation and delivered the project. Show your knowledge of the architecture and talk about the hardest parts. Demonstrate how you developed a new algorithm and fixed bugs.
While most IT companies have a casual work environment and they don't follow any dress code, it is better to dress smartly. In case, the company has a dress code, call and find out. If jeans and T-shirts are allowed, appear for the interview in business casual.
Arriving late for the interview will not only create a bad impression of you, but also put a question mark on your punctuality. So to avoid being late for the interview, try to visit the interview location a day before. This will help you understand the exact time required to reach the spot. Further, allow yourself a buffer time of 30 minutes so that even if you're delay because of the traffic, you can still make it in time.
What skills you hold and what you've achieved are already outlined in your resume. But the recruiter wants to see where and how you used your skills and what was the outcome. So carry a portfolio of your work so that the interviewer can see it personally. The portfolio could be a physical notebook, a link where you have stored the samples of work done, and an online blog to demonstrate your skills and achievements. In addition, carry a notepad, pen, and hard copies of your resume.
Communication is one of the important selection criteria in any interview. But since it's a technical interview, your communication will be assessed on your ability to answer technical questions. So try to communicate softly and don't make any haste in answering the questions. Moreover, while communicating, maintain an eye-contact with the interviewer.
How you enter the interview cabin, greet the interviewers, and take your seat will be closely watched by the interview panel. One good way to impress the interviewers is not to sit down until asked. And after taking the seat, don't forget to thank them. Sit comfortably and don't slouch. Don't be uptight and be as normal as possible.
Remember, technical interviews are similar to other interviews. The only difference in being interviewed by the technical company is the need to demonstrate your skills on the whiteboard. If you implement these tips seriously, you can pocket the job quite easily. For more interview tips, keep browsing our website.