How to react when asked to rate your skills in an interview
The article discusses the common interview question where candidates must rate a skill from 1–10 and argues that, while many find it silly, it mainly tests self-awareness and self-reflection. It explains that interviewers look less at the exact number and more at how you justify it, how well you know your strengths and gaps, and how you react under this kind of pressure.
It then suggests preparing a small self-rating table aligned with the job ad, including each skill, a rating, and concrete reasons plus recent improvements. In the interview, you can use this preparation to give a clear number with supporting examples. Finally, it proposes an advanced approach: question the usefulness of numeric ratings and instead describe in detail where you have strong experience, where you lack exposure, and how you plan to grow, which can give interviewers a richer picture than a simple score.
Reading notes#
- The question “How would you rate your JavaScript (or other) skills 1–10?” often unnerves candidates and is perceived as dumb, but can be turned into an advantage.
- The author states the question serves a purpose: it exists to be faced and handled if you want the job.
- Core intent is to test self-awareness: how you see yourself, how you rate your own skills, and how deeply you have reflected on them.
- Interviewers also observe how much thought you put into your answer and how you react to a tricky prompt.
- Professional work, like software development, involves regular use of a skill set including thinking, designing, prototyping, testing, and coding solutions.
- Employers expect employees to improve over time as they invest in training, responsibility, and freedom, and they look for ambition to progress.
- To improve, you must know where you currently stand, which requires continuous self-reflection and awareness of your level.
- Knowing your current level helps you plan a path to your goals and judge when you can solve problems alone and when you need help.
- A slow, generic response can signal that you have not reflected on your skills recently.
- Interviewers usually expect more than just a number; they want reasons that explain how you arrived at a specific rating.
- The article notes that there is typically no verification whether an 8 or 9 is justified; delivery and reasoning matter most.
- Preparation advice: take some time before the interview to honestly rate yourself based on the job ad’s required skills.
- The author suggests creating a table listing each skill, your rating, and why that rating is justified, plus how you have improved recently.
- Example skills for such a table include JavaScript, frameworks like React/Vue/Angular/Svelte, API design, and layouting.
- As a bonus, you can think about what additional relevant abilities beyond the listed hard skills might matter for the role.
- Doing this exercise not only prepares you for rating questions but also trains your self-reflection.
- The author warns that you may be asked to rate skills unrelated to the position, which they personally dislike, but preparation still helps you answer.
- You are encouraged to verbalize your thought process while thinking about an answer so interviewers do not watch you in silence, which can earn extra points.
- In the interview, if the question appears, prior self-reflection allows you to state a number honestly and justify it with arguments.
- You should present yourself as prepared and not thrown off by this kind of tricky question, using it to show your reflection work.
- Example “good” numeric answer: giving yourself an 8 in JavaScript, citing extensive work as a Senior Developer, improved understanding of Promises and async/await, and acknowledging limited experience with features like generators.
- The article highlights what this example achieves: you rate yourself, give reasons, show improvement, and admit remaining gaps.
- The author then suggests you can go beyond this basic strategy and “crush” the question by rethinking the role of numbers.
- They argue that rating skills with numbers is nearly impossible and question what a 10 in JavaScript would even mean.
- The text mentions that even someone who learned the full ECMA spec would not give themselves a 10.
- It also cites Brendan Eich saying he would not call himself a JavaScript expert anymore because he has not kept up with the language’s evolution, even though he could catch up.
- From this, the article concludes that numbers are a poor indicator and that the question’s main function is to probe self-awareness.
- Suggested alternative: abandon the numeric rating and instead demonstrate that you understand your relative position in terms of experience and gaps.
- The author notes that experience as a frontend developer is often transferable between similar SPA projects with comparable building blocks.
- Being aware of other language or framework features you have not used much makes it easier to articulate what you lack.
- Recommended strategy: show you know what you have worked with extensively and what you have rarely or never used.
- Example “crushing” answer: politely state that numbers are a bad metric and that different similar developers would give different scores.
- In that example, the candidate then outlines having spent years building base components, gaining deep experience with functional React components and React’s rendering loop.
- They also describe significant exposure to accessibility issues due to an internal user base of around 500 frontend engineers.
- The same example includes admitting limited experience with remote calls and the fetch API and describing frontend data skills as an area needing improvement.
- It further mentions little exposure to server-side React and tools like Next.
- The candidate then expresses strong belief that, with time and opportunity, they can catch up quickly and become a valuable contributor.
- The article claims this richer answer provides more insight than a bare number with brief reasons.
- It also argues that such an answer demonstrates awareness of flawed rating systems while still making clear what you know and don’t know.
- This approach shows deep reflection on past work and awareness of what the future role might demand.
- The author concludes that interviewers should not need more than this level of transparency, and if they do, the company may not be worth joining.
- At the end, the article invites readers to follow the author on Twitter or LinkedIn and mentions options to support the author or share the piece.
