Even if a great C.V. is a good advantage, during an interview, it can be useful to try to explain you're good at work to get the job.

However, how can you do it without seeming pretentious?

  • 2
    Do you get the impression people find you to be pretentious during interviews or other settings?
    – user8365
    Jan 7, 2014 at 19:32
  • I don't really know but it's possible. In doubt, I prefer avoiding the risks.
    – Zistoloen
    Jan 7, 2014 at 19:48

5 Answers 5


I'm currently sitting on the other side of the table, building up a team.

Maybe it's not the norm but for me, if you 'talk the talk' as they say, I can get a feeling for whether candidates are good on the job and ultimately I'll form my picture working with a candidate on a trial day, or pair programming session.

So, if you genuinely are good at a job, display it not by preening yourself on something but by having an honest conversation, being interested in what problems you would be facing and - if you can - Current producer supplier, on how you would approach those difficulties, regardless of whether you would be hired.

Would work with me, at least.

  • 1
    I agree, he definitely doesn't need to SAY it, he needs to SHOW it during the interview.
    – Spidey
    Jan 10, 2014 at 14:26

Executive Summary

  1. Actions speak louder than words
  2. Lead the interviewer to asking about your strengths
  3. Avoid overt unprompted self-promotion

Speak Softly, and Carry a Big C.V.

If you have done nothing of value, you aren't going to have much success promoting yourself to employers. The best way to explain you are good at work is not through explaining to the interviewer how you are good at work, but by having great work experience, demonstrable accomplishments, and good references from previous employers.

You Can Lead an Interviewer to Water...

Everyone is going to have areas they are stronger in, and areas they are weaker in. If I'm Steve Jobs, I probably don't want to be focusing an interview on how I handle interpersonal relations and conflicts with my coworkers. Instead it would be much better to try to focus questions on inspiring passion and having vision for future direction or some such. So if the interviewer asks, "Could you explain how you address conflict with members of your team?" you want to lead the interviewer off that track and steer them toward asking about your strength. For instance:

"There are two types of conflict. When a project isn't going well, or management doesn't seem to be hearing the feedback from the team doing the work, conflict can rise out of frustration. The other type of conflict is productive creative disagreement that is based on wanting to create something great. In my last role I focused on making sure that all conflict was the latter type, by making sure my team all shared the same direction."

The point is that you are taking a question that could paint you in a bad light, and shifting the discussion to something you are better at, which is how to lead people to have a common goal. By leading the interviewer to ask about your strengths, you don't need to promote yourself, you can just answer honestly based on your accomplishments, and get the interviewer to think more highly while making the interviewer seem like they are the one leading.

Don't Toot Your Own Horn

Conversation should be natural and flow based on the questions being asked. When you try to stick in accomplishments or anything that comes across as overt self-promotion, it makes it seem like your skills/accomplishments aren't relevant to the discussion. If the discussion isn't allowing you to talk about things you are proud about or have experience with, you need to shift the discussion (see above section).

Even when you are discussing your accomplishments, I recommend avoiding sounding like you did everything yourself (unless of course you did). Any time you've worked with a team, using language that includes them ("We" instead of "I", etc.) will make you sound better to many employers because you are giving credit to people who have nothing to gain from you including them in the discussion. I'm not a fan of people who pass off the team's work as their personal accomplishments, and seen it backfire when the team members they put as references didn't react as expected when asked about them.

Putting it All Together

Interviews go best when the discussion feels natural. If you seem confident, relaxed, and have substance to your answers, you will come across well. If you are reaching, or if you are forcibly trying to throw out things you are good at that don't quite fit, you will likely seem pretentious or less qualified than you are.

The only way to get good at interviewing is to practice. When you have a chance to go to an interview, try to take it (even if you don't think you'll take the job). By getting practice when there's nothing on the line, you'll end up being much better at it when it really counts.

  • +1 for If I'm Steve Jobs, I probably don't want to be focusing an interview on how I handle interpersonal relations and conflicts with my coworkers Jan 7, 2014 at 1:55
  • 2
    I don't care how skilled you think you are, if the job is not entry level, you had better have a track record of accomplishments that can speak for themselves.
    – HLGEM
    Jan 7, 2014 at 18:05
  • @HLGEM, amen. If you think that isn't clear enough in what I wrote above, please feel free to improve it.
    – jmac
    Jan 7, 2014 at 23:15
  • @Jmac, I thought what you wrote was fine, was just emphasizing one of teh main points you made.
    – HLGEM
    Jan 8, 2014 at 13:47

The best solution I've seen so far is to explain what you've done in the past. Show that you've got a proven track record of success and overcoming adverse situations.

Usually this is done by explaining problems you've faced in previous positions and how you worked through them. You're not trying to show that you did everything yourself; you're trying to show how you utilized the resources you had on hand (including other coworkers) to come to the solution.


In all honesty, I'd say there is no one in the world is guaranteed to be good on every team. So the fact that you've been good at work, is not a 100% assurance that you'll be good at this job, in this company or on this team.

The best you can do is:

  • Demonstrate your skills by being as engaged and collaborative with the interviewer as you would be in the work place. This is my absolute #1, if you aren't actively listening, and striving towards being a participative member of a two way conversation, then all the former successes in the world may not make you seem like a good guy to work with.
  • Have a clear vision in your mind of the work you've been good at in the past, what made it a success (the work as a whole, not you yourself), and why you enjoyed it or what you learned while doing it.
  • Similarly, have in mind teams and jobs you've really enjoyed. Most people don't enjoy jobs they are horrible at (and in fact, I suspect perform worse at jobs they hate), so chances are good there is some correlation between work you enjoy and work you have had proven successes with.

Don't push to mention any of these things - see where the interview takes you. But if you walk in the door primed with memories of successful accomplishments, good team experiences, and work you've been passionate about - then it's quite likely that the first time they say "can you give me an example of...?" it'll be one of these things that leaps to mind.

I generally don't want to hear from a candidate just how great they think they are, or just how wonderful they've been on the job. I'd like to think that most people will have enough self-confidence to think they are good at their jobs... I want to know that the person has done some hard work, had the drive to tackle stuff even when the path to success wasn't clear, and then learned from their mistakes. That means I need to hear both the challenge and the final success to feel like I've got a good one.

  • By good at work, I meant skilled (with a good CV).
    – Zistoloen
    Jan 7, 2014 at 13:32
  • Same advice still holds. As an interviewer I'm less concerned with the skills the person has as I am with the skills I need, so I'll ask questions to verify knowledge and skills and hope the candidate can answer them, but I also know that a perfect match won't happen, so more important than the skills you have is the ability to learn new ones. Jan 7, 2014 at 14:59

Saying you're good at C# - Ho Hum.

"One of the things I noticed with the old mainframe style screens was that they had a 'search mode' and an 'edit mode'. Now that we have much larger screens I set this up so that the 'search' is on the left and one can select a record for edit, the edit panel is on the right. The search user control allows search parameters and presents a list, the edit user control is populated with the currently selected item on the list."

The above quote is what I would tell someone if I was migrating old 80x25 character screens to a GUI interface. This is easy to write in most current languages. Defining a consistent design pattern is something an employer would expect from developers with a few years of experience.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .