Showing posts with label preparation. Show all posts
Showing posts with label preparation. Show all posts

Saturday, 11 February 2012

"What is your greatest weakness?"


 “What is your biggest weakness?” is a question that is starting to disappear from interviews, especially for graduate programmes, because it has become very cliché. However, there are still plenty of old school hiring managers out there who (some would argue out of laziness…) like to ask this question, in part because they know everyone absolutely hates answering this one.  Even Barack Obama faced it during his presidential campaign from several journalists!

The main stage I’ve heard it used at for graduates is in final stage partner/director interviews – which unfortunately makes it a question you definitely need to be prepared for because getting a ‘no’ at this stage of the process - even if you’ve done really well in a challenging assessment centre - is usually career-limiting.

In general respondents still use the approach of ‘I know you are asking for a weakness, but I am going to tell you something that you will actually see as a positive.’ Something like ‘I like to get into the detail of something because I like to make sure everything is done right’, or ‘I need to learn to say no – sometimes I get involved in too many things and get pulled in too many different directions.’ Or my favourite (!) ‘I’m a perfectionist’. Oh please – so boring, and doesn’t lead the conversation anywhere…

To be honest, as a recruiter, that trick is very old now. It is really dull when someone rolls out an answer such as these and in general it doesn’t inspire me to push them forward to the next stage.  I prefer to hear honesty about a development point and some evidence of how you’ve already started working on it:

 “At the end of my internship, I was given a lot of positive feedback but I also asked for development points as I was keen to make sure I learned from the experience. My manager told me that sometimes in meetings I needed to be more confident, because most of the time the points I raised with him after the meeting were spot on, and he wished I had said them in the meeting.  I knew this was something that I needed to work on, and I was trying to, but to have a manager I respected raise it with me really reinforced the point.

I reflected on the occasions where this had happened – where I had regretted not making my point in a meeting – and I realized that had I spoken up at the time, I would have been seen in a positive light by the directors at those meetings as I would have been making pertinent points and would probably have enhanced my prospects of advancement. I also realized that the worst thing that could happened would have been I made a point that wasn’t necessarily relevant and the meeting would probably have just moved on and no one would really have thought the worse of me except that I was trying to participate, which in general people appreciate rather than just sitting there quietly.

On my return to university, I was put in a project team with some more senior members of the faculty around whom I did feel quite intimidated. I set myself a challenge of making sure that I spoke up in the first team meeting at least once. I was very nervous, but I did it. After having made one point, which was picked up on and further discussed, I found that I made two and three more points and got more involved in the discussion as my confidence grew.

I still do get nervous in meetings, but I am working hard at it and feel that I am getting much better as I am exposed to more opportunities to participate. If I got this role, I would continue to work on this development point.”

This is broadly an answer that I had a couple of years ago and I thought it was a good, honest answer and demonstrated something who wasn’t playing games with the weaknesses question. I also liked that she was well-prepared as it was very articulately discussed.

I’m not saying that you don’t walk a fine line with some answers like this – if you take this approach, you have to have a finely-tuned answer about how you have worked to improve that development point / ‘weakness’ – but there is something very refreshing about someone who has been given some tough feedback and instead of ignoring it, or thinking the person giving the feedback is just wrong, has taken it onboard, analysed where they are going wrong, and then gone about correcting it in a methodical and conscious way.

As a line manager as well as a recruiter, the idea of training and developing someone who is open to feedback and really works on improving themselves as a result is quite exciting because it is possible to have proper, frank development conversations with someone like that and really bring them on quickly. Their prospects for advancement are much better than for others in my mind.

(As a slight aside, I would avoid actually using the word ‘weakness’ in your answer, even if they have said ‘weakness’ in the question. It is a word with such negative connotations. I prefer ‘development point’ or ‘areas for improvement’ – I would use that language instead of ‘weakness’ if I were you. They are also words that indicate more self-awareness and confidence.)

What’s your “weakness”? If you know, then you’re already half way to an answer because being conscious of it and knowing you need to do something about it is already more than many people.

GR

Friday, 5 November 2010

Conducting Useful Research for Interviews

Thanks for voting in the poll everyone... this was the winning article, so here it goes. I will try to get around to writing the other ones too in the weeks ahead as they all got quite a few votes.

Just to clarify before we kick off that this article is about research... but you also need to do preparation (competency answers, explaining everything on your CV, why you want the job, etc). Both are essential to be truly ready for an interview. I'll cover preparation in a future blog if it's of interest to you.

I'm going to have to start with the painful truth about conducting useful research for interviews... it's all about being organised and not just aimlessly surfing on the web (hands up who already knew this?...). We all do it (believe me, I procrastinate endlessly on Facebook/TSR/Twitter/Blogger/etc before I force myself to sit down and actually write these entries). You need to be really disciplined to really make the most of your valuable time. There is so much on the web these days that it is easy to waste a lot of time doing research for your interview without ever actually feeling like you are fully equipped. There is always the worry that something else obvious out there that you've missed that they will bring up at the interview.

The research approach you take will be slightly different depending on the industry and the company that you are applying to, but broadly speaking for "Top 100" type companies, there are 4 categories to consider:

1-the programme/role
2-the company
3-the industry
4-the current landscape/news

Let's take them one at a time:

The Programme/Role
You need to understand everything that is already on the website about the programme or role that you are applying to. This shows your high level of interest, but more important allows you to speak intelligently with your interviewers about the programme and make the right statements about why it is right for you. As an interviewer, if someone asks you a question to which the answer is readily available on the site, it is very off-putting. So, devour the grad website - everything on it.

The Company
You need to understand the company structure - the different departments/divisions/areas (everyone calls them something different). Understand their global structure - where was the company founded (geographically) and what is their presence now. Understand their make-up - there have been a lot of major mergers and divestments in the last couple of years - make sure you are aware of any that have happened affecting the company.

Make sure you understand how they are performing and where the profit is being generated in the company. Have a look at the communications / investor relations / news sections of the site - be aware of what the company is saying to the market about themselves and their work. If applicable, take a look at the high Exec Summary of the annual report. This will usually outline where the company is at (although beware how long it has been since the report was released.... if it was 11months ago, the picture could be significantly different now).

The Industry
Some of this information is quite 'fixed', so some people find it easier to read the information from a book, rather than the web (e.g. "All you need to know about the City" book). Research who their competitors are (and how they are performing relative to them.)

The Landscape
This is about demonstrating your knowledge of current affairs in the industry and that affect the industry. You also need to understand the current landscape of the industry - what is the current market for their products / offering? There is lots of readily-available information on this - blogs, Google News, the FT - but this is also one of the areas where it is easy to spend a lot of time surfing aimlessly. Try to undertake this type of research in careful 30min blocks. Pick a topic, and then research that and only that for that period. If something else springs to mind that you need to look into during that research, make a note on a piece of paper to add it to your plan, but don't go off on a tangent researching the new topic there and then (even if you think it might be more important.

Overall on this last one, it is not really something that you can research in a week before your interview - it is one that you need to be building your knowledge on over a period of weeks and months. Find the blogs / subscriptions that work for you and sign-up as soon as you can. RSS Feeds can also be useful from certain sites. It might even be worth setting up a separate email address rather than cluttering up your own personal address. Check out CNBC, MoneyWeek, Yahoo! Finance, hereisthecity, etc.


Keep all your notes well organised, and bookmark sites that you visit that are useful, storing them all in a folder.

I've put together a checklist for you if you are interviewing for an Investment Bank and are planning your research approach - it can be downloaded here. I'll try to put one together for Consulting too in the next few weeks - I've run out of time tonight - but it should not be that different to the IB one, just tailored slightly more towards that industry. 


Above all, be organised and be disciplined with your time. Ultimately it's unlikely that you'll go into an interview feeling 100% confident that you have everything covered, but if you've covered a reasonable spread of research across the above topics, you should be able to talk to a good amount of what might come up.

Sunday, 31 October 2010

Competency questions - what else do you need to know?

As I've said before, I don't want to reinvent the wheel on this blog too much by providing information that you already know or guidance that is already well-documented on other graduate recruitment sites.  Thus, I am not doing to go into too much detail on answering competency-based questions, using the STAR model, making sure you address the question asked, etc.   Knowing how to answer a competency-based question is essential to success in securing a place on a graduate programme, so make sure you know how to answer them.

The challenge with competency-based interviews is that graduates are now so well-practiced and well-able to provide great answers, that even more questioning is needed to differentiate them in order to really try to identify the best for the roles available. In many ways this is causing a move back towards trying to ensure you have to think on your feet during the interview and therefore less scripted and formulaic questioning by the interviewers and their instead using what they have heard to determine what the next question is. Thus more and more the follow-up question to each competency scenario is becoming the differentiator.

What is the "follow-up question"?
This is the question that the interviewer might throw at you depending on the competency answer you have just provided. Some typical examples would be:

  • What would you do differently next time?
  • How would people in the team you managed say you did as project manager? What would they say you could improve on?
  • Why did you/it succeed?
  • Why did you/it fail?
  • What could you have done to make it even better?
  • What did you learn about yourself?
  • Would you do it again? Why? Why not?

How do they decide what question to ask you?
They will usually ask a follow-up question on the part of your 'story' that sounded the least plausible to their ears. For example, if you say everything went well and there were no arguments or issues, then they might follow-up on that with "What was it that made the team work so well together? Were there any contentious issues or points of discussion?"  To be honest with a situation like that, you are best to have an example of something that was difficult in the team - generally in situations where you are working in a team - especially at Uni - realistically something probably did go wrong and it was difficult. It sounds more plausible to be upfront about them - and as long as you learned from it, then that's perfectly fine - and in fact, more reflective of the working world too.

"What would you do differently next time?" is probably the most common and the most generic question asked, so it's worth preparing an answer to that for most of your scenarios.  Don't say you would do nothing differently - come up with something. A good answer might be to plan a particular part of it more meticulously, or to set objectives for individuals within the team so that roles are clearer - something like that.

Think of the question that you would least like to be asked as a follow-up to the scenario you've explained... and then imagine that they have asked you it - what would you say? I promise, you won't regret it! Worse case scenario, they ask the question and you have an answer prepped. Best case scenario, they don't ask it, but you go into the interview more confident because you're more prepped.