2 min read

Why you should rate yourself 2 out of 10 in an interview

Learn why rating yourself too high in interviews can hurt your chances and discover a better approach to answering the 'rate yourself' question.

In many technical interviews, you're often asked, “How would you rate yourself out of 10 in a particular technology?” For instance, an interviewer might ask, “How much would you rate yourself out of 10 in HTML?”


This question can seem straightforward, but many candidates make the critical mistake of rating themselves too highly. I’ve encountered applicants, especially those applying for roles like Frontend Developer or Website Designer, rating themselves 8, 9, or even 10 out of 10 in technologies such as HTML, CSS, JavaScript, Bootstrap, React, and others.

Why is this a mistake?

Here’s why rating yourself too high can negatively impact your chances:

  • Rating yourself 8/10 suggests you know 80% of the technology. A 9/10 means you claim to know 90%, and a perfect 10/10 implies you’ve mastered 100% of it.
  • Even with 13+ years of experience as a Full Stack Web Developer, I’d only rate myself 4 or 5 out of 10 in these technologies, despite scoring 14/15 on LinkedIn assessment tests and being in the top 10% of Fiverr tests.
  • Technologies like HTML, CSS, JavaScript, Bootstrap, and React are extremely vast. It’s unrealistic to claim mastery at the level of 8, 9, or 10 out of 10 because there’s always more to learn, and these technologies are constantly evolving.
  • Overestimating yourself may give the interviewer the impression that you're overconfident or don’t fully understand the depth and complexity of the technology.
  • If you rate yourself too highly but fail to answer 80%, 90%, or 100% of the technical questions, you leave a poor impression and risk failing the interview.

How to approach this question?

The best way to approach the "rate yourself" question is to be honest, humble, and aware of your skill level. This is where the Dreyfus Model of Skill Acquisition can help. It breaks down skill levels into categories: novice, advanced beginner, competent, proficient, and expert. Referencing this model can provide a more accurate and thoughtful way to describe your abilities.

For Freshers:

  • A safe and respectful answer could be: "I’m a fresher and new to this industry, so I don’t believe I should rate myself. Instead, I would appreciate the opportunity to be evaluated on my skills, and I would be grateful if you could rate me." This response is safe, respectful, and polite.
  • If the interviewer insists on a self-rating, respond with: "As I mentioned, since I’m new to this field, rather than giving a number, I’d classify myself as a novice or advanced beginner based on the Dreyfus Model of Skill Acquisition." (Never claim more than that, or any higher level.)
  • If they still push for a numerical rating, you can say: "If I must, I’d rate myself between 2 and 3 out of 10, considering the depth and complexity of this technology."

For Experienced Candidates:

  • A suitable answer could be: "With 5 years of experience, I’ve learned how deep and complex this technology is. According to the Dreyfus Model of Skill Acquisition, I would consider myself competent or proficient in this technology." (Avoid claiming expert status.)
  • If the interviewer insists on a number, say: "If I have to give a rating, I’d say between 4 and 5 out of 10, keeping in mind how vast and continuously evolving these technologies are."

Final Thoughts:

It’s always better to play it safe, understate your skills, and demonstrate a willingness to learn, rather than overestimate your abilities. Humility in interviews often works in your favour, as it shows you understand the challenges and complexities of the technologies and are open to continuous learning.