1. Technical skills alone are not sufficient for you to perform well in your interviews and progress in your career.
2. Your technical skills must be complemented with business skills (i.e. knowledge/ understanding of the business, ability to communicate and interact effectively with the business users/customers, ability to look at things from the user’s perspective as opposed to only technology perspective, ability to persuade/convince business with alternative solutions, which can provide a win/win solution from users’ perspective as well as technology perspective), ability to communicate effectively with your fellow developers, immediate and senior management, ability to work in a team as well as independently, problem solving/analytical skills, organizational skills, ability to cope with difficult situations like stress due to work load, deadlines etc and manage or deal with difficult people, being a good listener with the right attitude.
3. If you have "I know it all attitude", it will adversely affect affect your ability to be a good listener, ability to look at things in a different perspective, ability to work well in a team and consequently your progression in your career.
4.Pick your recent projects and enthusiastically brief on it. Interviewer will be looking for how passionate
you are about your past experience and achievements. Also is imperative that during your briefing, you
demonstrate on a high level(without getting too technical) how you applied your skills and knowledge in some of the key areas like Design Patterns,Design issues,Performance issues, Multithreading etc.
5. 90% of the interview questions are asked based on your own resume. So in my view it is also very beneficial to mention how you demonstrated your knowledge/skills by stepping through a recent project on your resume.
6. The general rule for interviews is to use the STAR model.
8. Weaknesses:
Select a trait and come up with a solution to overcome your weakness. Stay away from personal qualities and concentrate more on professional traits for example:
9. Where do you see yourself after 2-5 years
2. Your technical skills must be complemented with business skills (i.e. knowledge/ understanding of the business, ability to communicate and interact effectively with the business users/customers, ability to look at things from the user’s perspective as opposed to only technology perspective, ability to persuade/convince business with alternative solutions, which can provide a win/win solution from users’ perspective as well as technology perspective), ability to communicate effectively with your fellow developers, immediate and senior management, ability to work in a team as well as independently, problem solving/analytical skills, organizational skills, ability to cope with difficult situations like stress due to work load, deadlines etc and manage or deal with difficult people, being a good listener with the right attitude.
3. If you have "I know it all attitude", it will adversely affect affect your ability to be a good listener, ability to look at things in a different perspective, ability to work well in a team and consequently your progression in your career.
4.Pick your recent projects and enthusiastically brief on it. Interviewer will be looking for how passionate
you are about your past experience and achievements. Also is imperative that during your briefing, you
demonstrate on a high level(without getting too technical) how you applied your skills and knowledge in some of the key areas like Design Patterns,Design issues,Performance issues, Multithreading etc.
5. 90% of the interview questions are asked based on your own resume. So in my view it is also very beneficial to mention how you demonstrated your knowledge/skills by stepping through a recent project on your resume.
6. The general rule for interviews is to use the STAR model.
- S - Describe the situation you were in
- T - Explain the task, providing enough info so that the interviewer understands the problem.
- A - Describe the action you took to solve the problem.
- R - What were the results of your actions
- Taking initiatives and being pro-active: You can illustrate how you took initiative to fix a transactional issue, a performance problem or a memory leak problem.
- Design skills: You can illustrate how you designed a particular application using OO concepts.
- Problem solving skills: Explain how you will break a complex problem into more manageable sub-sections and then apply brain storming and analytical skills to solve the complex problem. Illustrate how you went about identifying a scalability issue or a memory leak problem.
- Communication skills: Illustrate that you can communicate effectively with all the team members, business analysts, users, testers, stake holders etc.
- Ability to work in a team environment as well as independently: Illustrate that you are technically sound to work independently as well as have the interpersonal skills to fit into any team environment.
- Hard working, honest, and conscientious etc are the adjectives to describe you.
8. Weaknesses:
Select a trait and come up with a solution to overcome your weakness. Stay away from personal qualities and concentrate more on professional traits for example:
- I pride myself on being an attention to detail guy but sometimes miss small details. So I am working on applying the 80/20 principle to manage time and details. Spend 80% of my effort and time on 20% of the tasks, which are critical and important to the task at hand.
- Some times when there is a technical issue or a problem I tend to work continuously until I fix it without having a break. But what I have noticed and am trying to practice is that taking a break away from the problem and thinking outside the square will assist you in identifying the root cause of the problem sooner.
9. Where do you see yourself after 2-5 years
- Next 2-3 years to become a senior developer or a team lead.
- Next 3-5 years to become a solution designer or an architect.
No comments:
Post a Comment