Talk me through your CV
Discussion
Hi All,
Being one of the most common questions at an interview; what is the best way of answering this question?
Do people start with their education or work experience?
Do people start with their current role or oldest role first?
How much depth do you go into for each role?
Key things I have noted is always state why you moved onto a new role and maybe state key achievements at each stage.
Being one of the most common questions at an interview; what is the best way of answering this question?
Do people start with their education or work experience?
Do people start with their current role or oldest role first?
How much depth do you go into for each role?
Key things I have noted is always state why you moved onto a new role and maybe state key achievements at each stage.
None of the above, as odd as that may seem. If you have to explain your CV then it's not written well some would say. If this question is asked, some would say they are missing an opportunity to learn more about you.
Based upon research in to the true requirements if employers and recruiters: tell them how you can do the job well; that you will enjoy doing the job; and that you will fit their organisation. Anything else may be a wasted opportunity. Good luck!
Based upon research in to the true requirements if employers and recruiters: tell them how you can do the job well; that you will enjoy doing the job; and that you will fit their organisation. Anything else may be a wasted opportunity. Good luck!
I don't think this is necessarily a bad question. Its open ended and gives the interviewer a bit of a feel for you work life balance perhaps and you may well reveal a lot more about your ambitions than if asked the question outright.
I.e. I used to do C++ and then I moved to Excel / VBA RAD development over my last 3 roles as I wanted to be closer to the end consumer of my work ( the Front Office ) and have a shorter / freer release cycle. I release fixes and improvements almost every day now. Instead of releasing every 4-6 months inside a legacy behemoth.
I went contracting as I was asked previous to sort of work myself out of a job by replacing 'my' system I worked on with another teams new shiny .Net one, and if I am going to do that role replacing Excel VBA applications it makes more sense to go in as a consultant. When the job is done I am able to move on without worrying about the politics of what a new role would be, reporting lines and employee grade that would come with a permanent position. you get more money but less work security / continuity. Both sides win with a contractor in these roles I feel.
I am leaking information in a subtle way about the kind of project / technology and team I like to work on and where I want to go all in the one question.
I guess it avoids the "I am a great team player and believe I am dynamic / fast paced blah blah you get when asking about certain things in a direct manner.
I.e. I used to do C++ and then I moved to Excel / VBA RAD development over my last 3 roles as I wanted to be closer to the end consumer of my work ( the Front Office ) and have a shorter / freer release cycle. I release fixes and improvements almost every day now. Instead of releasing every 4-6 months inside a legacy behemoth.
I went contracting as I was asked previous to sort of work myself out of a job by replacing 'my' system I worked on with another teams new shiny .Net one, and if I am going to do that role replacing Excel VBA applications it makes more sense to go in as a consultant. When the job is done I am able to move on without worrying about the politics of what a new role would be, reporting lines and employee grade that would come with a permanent position. you get more money but less work security / continuity. Both sides win with a contractor in these roles I feel.
I am leaking information in a subtle way about the kind of project / technology and team I like to work on and where I want to go all in the one question.
I guess it avoids the "I am a great team player and believe I am dynamic / fast paced blah blah you get when asking about certain things in a direct manner.
I interview around 200 people a year. (I am an in house recruiter)
Generally if I ask this question (and I don’t always) it is because I want to get the candidate to talk. Open them up a bit.
We may have already discussed the job, I might have briefed them on the business – but not yet heard much from them.
So I want a five minute overview, the key thing I am looking for is a consistent, thoughtful, planned approach to the career. (or by exception, what bits went wrong, how did you bounce back)
Why did you make those choices, what did you gain, what motivated you to look for something else ?
By all means mention which University you went to and why if it was five years ago, but not if it was 20 years ago.
Put the emphasis of about 80% of your time explaining motivation and achievement – this reveals your ambition and some depth to you as a person instead of a CV. How people talk about themselves is always enlightening.
I would freely admit it is a bit of a lazy question, chance I am only interested in about 5% of the answer I get most of them time. However it does serve to “warm up” the discussion and relax the person ahead of some more challenging questions.
People will never tell you the real stuff in the first ten minutes, you need to build a bit of rapport and a simple run through of the CV and a few easy questions help build that.
Generally if I ask this question (and I don’t always) it is because I want to get the candidate to talk. Open them up a bit.
We may have already discussed the job, I might have briefed them on the business – but not yet heard much from them.
So I want a five minute overview, the key thing I am looking for is a consistent, thoughtful, planned approach to the career. (or by exception, what bits went wrong, how did you bounce back)
Why did you make those choices, what did you gain, what motivated you to look for something else ?
By all means mention which University you went to and why if it was five years ago, but not if it was 20 years ago.
Put the emphasis of about 80% of your time explaining motivation and achievement – this reveals your ambition and some depth to you as a person instead of a CV. How people talk about themselves is always enlightening.
I would freely admit it is a bit of a lazy question, chance I am only interested in about 5% of the answer I get most of them time. However it does serve to “warm up” the discussion and relax the person ahead of some more challenging questions.
People will never tell you the real stuff in the first ten minutes, you need to build a bit of rapport and a simple run through of the CV and a few easy questions help build that.
I always ask this question, and it can be very illuminating.
Firstly, be consistent with your CV. It's amazing how often such a question has me wondering if I am looking at the right CV.
As for how to answer it, give a narrative of your career. Join the dots, you finished university and decided to do this job because ABC, after so long you changed jobs because XZY. Like slides in a lecture, the CV should form a sort of prop for the conversation about your career to date, not a substitute for it.
Firstly, be consistent with your CV. It's amazing how often such a question has me wondering if I am looking at the right CV.
As for how to answer it, give a narrative of your career. Join the dots, you finished university and decided to do this job because ABC, after so long you changed jobs because XZY. Like slides in a lecture, the CV should form a sort of prop for the conversation about your career to date, not a substitute for it.
Gassing Station | Jobs & Employment Matters | Top of Page | What's New | My Stuff