As said in my last post regarding Tips and patterns to be followed while approaching Interview problems, this article is written focussing mainly on how to ace an interview given you have all the required technical skills.

Do check out my last post and if you happen to like it, don't forget to upvote and share it among your friends. [https://leetcode.com/discuss/general-discussion/861135/tips-and-patterns-while-approaching-a-dsa-problem-in-interviews/709201]

Below I have listed some of the techniques and tips that you should keep in mind while giving an interview.

• Dress yourself formally before the interview and make sure to take sound sleep before the D-day.
• Do not feel shy of speaking your heart out in the interviews, even if the approach is not well defined, the interviewer would want to help you if you interact and maintain the purpose of problems with him.
• Make sure you understand the problem very precisely, ask questions, repeat, do not feel ashamed. You could also ask the person to run a testcase for you. Start writing the code only when it has been agreed upon and fully optimized. Do it in one go, and check for any errors and debug them.
• Keep a smiling face throughout, do not try to fake anything. Those people there, are masters of knowing about your attitude towards the role.
• Always start off by a brute force approach to the given problem. Never jump onto conclusions too early. Remember they are meeting you probably for the very first and last time, so your impression has to be cast in the best possible way. Therefore, if you start off by giving a brute force approach followed by relevant optimizations, they would know that you're capable of thinking and optimizing on spot, which is a very crucial task in hand while giving an interview.
• Be confident of your skills and try to speak fluently. Even if fluency is not possible, do let the interviewer know that you're the right person for the job. Your confidence plays a very important role in defining that.
• You should also ask the interviewer about a pseudocode before you write it. Sometimes they allow it, so be careful to know about it beforehand.
• One very important thing: Try to practice writing code on notepad, so that you know about the indentation and other problems that you might face when not working in a compiler. It is definitely a very good practice and really helps you to debug your code fast enough.
• Know your resume in and out. There should never be anything that is not relevant to the position you are applying for. Keep it concise and clean. Never write something that you've got no idea about. You may regret it later as it may become the reason for your rejection.
• Any rough work that you may do (in online virtual interviews) should be done on the coding prompt itself, be it a dry run of your algorithm or answers to your testcases. I understand that pen and paper is an alternative but you have to let the interviewer know of your entire thought process, and doing this on the prompt itself really helps.
• Make sure you have good connection available. Stay in a quiet place while giving the interview. Will help you enhance your focus.
• Finally, for the HR round, tell examples from your life where you exhibited qualities that the interviewer wants to know about. He would easily relate to them this way, and yes, try to keep it as natural as possible.

And yes, do not lose your confidence if you don't crack the interview. Many factors influence it and you should always learn something new out of each experience. Remeber that you have got your own gifts, some may get things sooner than you but you need to keep moving forward, getting better with each failure, 'Rising from the Ashes' as I like to call it.

Never compare yourself with others, if you can look to the guy in the mirror and say that you're better than what you were yesterday, you have done amazingly well.

Keep practising, keep learning. The world is there for the taking. Cheers :)