·
For each of your primary skills, you should
have a story; this includes both personal skills (such as your leadership or
analytical skills) and technical skills (C++, Java, or UML)
·
They
need to be about you, not a mentor or a colleague; they must be about your
goals, your skills, your struggles, your achievements, and tell not only how
you did something but why you did it
·
Just
as you review and brush up on various systems and technologies before an
interview, you need to prepare and have your stories ready to go before an
interview
·
Keep
the stories simple; they should last between 30 and 90 seconds
·
Rehearse
them with someone, ensuring that they are on point and focused
·
Your
stories must include not only how you did something, but why you did it
·
They
need to focus on your core skills and expertise, and should affirm what you are
bringing to the position
·
Stories
need to illustrate your value to the firm, for example you can share that your
ability as a leader led to the successful completion of a project ahead of
schedule, or that your analysis led to increased functionality of a system
·
Be
selective with your stories; consider them fully - a story that illustrates
your competitive drive if not done right might lead the interviewer to the
conclusion that you cannot work with others
·
Stories
must be honest and sincere; they cannot evolve as you tell them, which comes
from not only truthfulness but also preparation
Interviewing is a unique experience
Unlike how most of choose to live our lives, during an interview
we cannot let our accomplishments speak for us.
You need tell people during an interview what you have accomplished and
what you can accomplish for them!

·
Brag
about your achievements, your challenges and goals, now is not the time to be
modest take credit for what you have done on past projects and share with the
interviewer what you are capable of
·
Be
able to explain not only how, but why you used that technology; for example- On
my last assignment we chose to use Java because it runs on all platforms as
opposed to ….
·
Review
skills, especially if it is one you have not used in your current project and
be able to cite technology and reference examples of where, how, and why you
used it
·
Remember
you get only one chance to make the impression; do not guess about the skills,
stay focused on the things you know best
·
Remember
that the phone and communication is bi-directional, not only to provide
information on you but can also provide information to you
·
Keep
a copy of your resume in front of you while taking the phone interview,
so that when the interviewer refers to your experience, you can both
literally be on the same page
·
Do
not hesitate to ask the interviewer to repeat a question; as opposed to
guessing at what he or she said
·
Be
prepared to talk about your recent projects complete with examples of what you
did, how you did it and why, and likewise be prepared for follow up questions
probing those technologies and your depth of knowledge of them
·
When
the question is about what you did in a particular project, you need to provide
not only how you did it but why you did it; for example: While I was working
for company XYZ, I was working in their system group supporting a Derivative
system, the client needed to add functionality to the system because of recent
governmental regulation changes, the system was written in Java. I was
responsible for making changes to _____ and that technology was used because of
______
·
When an
interviewer asks you why they should hire you, you must speak confidently and
honestly about your abilities, which is achieved by knowing your goals, your
skills and your achievements; you need to acknowledge your abilities and
accomplishments such as having a very strong work ethic,
integrity, excellent industry experience, and that you can
aggressively pursue your goals
