9 answers
L
Student
Woodbridge, Virginia
6
Questions
Updated
445 views
When should I say "I am familiar with"? When should I say "I am profficient at"? When can I call myself an expert or SME?
When you apply for jobs, there is usually a marker for time worked at 1-2 years, 5+ years, and 10+ years. At what point should I qualify myself as familiar, profficient, or an expert? Does having a credential help lessen the time required to be considered an expert?
Login to comment
9 answers
Stephanie Hamer
Campus Recruiter
5
Answers
Denver, Colorado
Updated
Stephanie’s Answer
Great question!
Here's a simple way to think about it:
* Familiar: You’ve worked with something enough to understand the basics and have a conversation about it, but you’d still need time to ramp up or get more comfortable with it.
* Proficient: You can do the task without much hand-holding. You’ve done it enough to feel confident talking about it and handling common situations.
* Expert/SME: You're the person others come to for help. You can teach it, troubleshoot problems, and spot things others might miss.
Regarding credentials/certifications, they can help, but they don't replace actual experience. A certification can help depending on the role and requirements, but it usually doesn't make you an expert by itself. In short, credentials are a good way to prove you've studied the subject, but expertise is proof you can apply it in real situations.
Here's a simple way to think about it:
* Familiar: You’ve worked with something enough to understand the basics and have a conversation about it, but you’d still need time to ramp up or get more comfortable with it.
* Proficient: You can do the task without much hand-holding. You’ve done it enough to feel confident talking about it and handling common situations.
* Expert/SME: You're the person others come to for help. You can teach it, troubleshoot problems, and spot things others might miss.
Regarding credentials/certifications, they can help, but they don't replace actual experience. A certification can help depending on the role and requirements, but it usually doesn't make you an expert by itself. In short, credentials are a good way to prove you've studied the subject, but expertise is proof you can apply it in real situations.
Yuritza G Nino de Daall
Quality Assurance / Process Improvement / Project Manager
58
Answers
Flowery Branch, Georgia
Updated
Yuritza G’s Answer
Hello there!!!
I think it is less about how many years you have and more about the level of responsibility you can handle. Someone with two years of hands-on experience solving real problems every day may be more proficient than someone with five years of limited exposure. The quality of your experience often matters more than the length of time.
A simple way to judge yourself is to ask: Can I work independently? If you still need regular guidance, you are probably familiar with the subject. If you can consistently deliver results on your own, you are likely proficient. If you can make decisions, improve processes, and explain complex topics to different audiences, you may be approaching expert or SME level. Credentials and certifications can definitely help demonstrate knowledge and commitment, but they are usually not a shortcut to expertise. In most workplaces, people earn the title of expert when they have built trust through experience, good judgment, and a track record of helping others solve difficult problems.
Good luck!!!
I think it is less about how many years you have and more about the level of responsibility you can handle. Someone with two years of hands-on experience solving real problems every day may be more proficient than someone with five years of limited exposure. The quality of your experience often matters more than the length of time.
A simple way to judge yourself is to ask: Can I work independently? If you still need regular guidance, you are probably familiar with the subject. If you can consistently deliver results on your own, you are likely proficient. If you can make decisions, improve processes, and explain complex topics to different audiences, you may be approaching expert or SME level. Credentials and certifications can definitely help demonstrate knowledge and commitment, but they are usually not a shortcut to expertise. In most workplaces, people earn the title of expert when they have built trust through experience, good judgment, and a track record of helping others solve difficult problems.
Good luck!!!
Sandeep Khandelwal
Software Engineer
132
Answers
San Ramon, California
Updated
Sandeep’s Answer
Hello there,
I would say you are familiar with something when you understand the concepts and can use it, but may still need guidance for advanced situations. You are proficient when you can work independently, solve most problems, and apply the skill effectively in real projects. You can consider yourself an expert or SME when others regularly seek your advice, you handle complex challenges confidently, and you have a proven track record of delivering results.
In my experience, expertise is determined more by impact and depth of knowledge than by a specific number of years. Certifications can help demonstrate knowledge and accelerate learning, but they do not replace real-world experience. True expertise comes from consistently applying knowledge, solving difficult problems, and helping others succeed.
I would say you are familiar with something when you understand the concepts and can use it, but may still need guidance for advanced situations. You are proficient when you can work independently, solve most problems, and apply the skill effectively in real projects. You can consider yourself an expert or SME when others regularly seek your advice, you handle complex challenges confidently, and you have a proven track record of delivering results.
In my experience, expertise is determined more by impact and depth of knowledge than by a specific number of years. Certifications can help demonstrate knowledge and accelerate learning, but they do not replace real-world experience. True expertise comes from consistently applying knowledge, solving difficult problems, and helping others succeed.
Kevin Teder
9
Answers
Updated
Kevin’s Answer
When you become proficient or a SME really varies depending upon the nature of the skill/experience.... and yes, receiving certifications does help with being perceived as proficient or a SME.
Vasanthi Muni
Solution Architect
3
Answers
Phoenix, Arizona
Updated
Vasanthi’s Answer
Hi,
Understanding is key to your growth. If you know the concepts but haven't used them yet, you're 'familiar.' When you've gained hands-on experience and can tackle moderate to complex problems, especially in real-world situations, you're 'proficient.' As you start designing solutions and leading on complex challenges, you'll become an expert or SME. While credentials are helpful, what's most important is consistently solving real-world problems. Keep pushing forward!
Understanding is key to your growth. If you know the concepts but haven't used them yet, you're 'familiar.' When you've gained hands-on experience and can tackle moderate to complex problems, especially in real-world situations, you're 'proficient.' As you start designing solutions and leading on complex challenges, you'll become an expert or SME. While credentials are helpful, what's most important is consistently solving real-world problems. Keep pushing forward!
Steven Feliciano
4
Answers
Updated
Steven’s Answer
“Familiar With” means you’ve touched it. You understand the concept, you’ve built something small with it, but you’d still reference documentation regularly. Use this when you’ve spent weeks to a few months with something and could hold a basic conversation about it — but wouldn’t want to be thrown into a production environment alone.
“Proficient In” means you can work independently. You solve real problems with it, you don’t panic when something breaks, and you know where to look when you’re stuck. This kicks in after roughly 6 months to 2 years of consistent, hands-on use — especially when that includes real projects or work under actual pressure.
“Expert” or “SME” means people come to you when they’re stuck. You’ve seen edge cases, debugged things with no Stack Overflow answer, and can speak to tradeoffs and architectural decisions without hesitation. Realistically, this is 3–5+ years of deep, focused use — not just time served, but intentional depth.
What Those Job Application Time Markers Actually Mean
The 1–2 year, 5+ year, and 10+ year buckets are guidelines, not gates. At 1–2 years you’re expected to contribute without heavy hand-holding. At 3–5 you’re expected to own problems end to end. At 5–10 you’re leading, mentoring, and making architecture calls. Beyond that, you’ve watched the industry shift and adapted more than once.
Don’t disqualify yourself based on years alone. If a job asks for 3 years and you have 1 but you’ve shipped serious projects — apply anyway. Years are a proxy for experience, and real experience speaks louder.
Do Credentials Shorten the Timeline?
Yes, but selectively. A relevant degree signals foundational depth and can compress the familiar-to-proficient gap in a hiring manager’s eyes. Certifications carry weight in specific domains and show validated, intentional learning. But a strong portfolio of deployed, real-world projects often outweighs both — especially in frontend, where your work is literally visible.
The credential doesn’t replace the experience. It vouches for your baseline so the hiring manager trusts your self-assessment faster.
A Simple Rule to Live By
Before labeling anything on your resume, ask yourself: “If they asked me to prove this in an interview right now — could I?” If yes, claim it confidently. If no, drop a tier. That single gut check keeps your resume honest and your interviews stress-free.
Time is a rough measure. Depth, consistency, and real output are what actually move you from one tier to the next. A student who ships three real client projects in 8 months has more claim to “proficient” than someone who watched tutorials for two years. Own what you’ve genuinely earned — and keep building the rest.
“Proficient In” means you can work independently. You solve real problems with it, you don’t panic when something breaks, and you know where to look when you’re stuck. This kicks in after roughly 6 months to 2 years of consistent, hands-on use — especially when that includes real projects or work under actual pressure.
“Expert” or “SME” means people come to you when they’re stuck. You’ve seen edge cases, debugged things with no Stack Overflow answer, and can speak to tradeoffs and architectural decisions without hesitation. Realistically, this is 3–5+ years of deep, focused use — not just time served, but intentional depth.
What Those Job Application Time Markers Actually Mean
The 1–2 year, 5+ year, and 10+ year buckets are guidelines, not gates. At 1–2 years you’re expected to contribute without heavy hand-holding. At 3–5 you’re expected to own problems end to end. At 5–10 you’re leading, mentoring, and making architecture calls. Beyond that, you’ve watched the industry shift and adapted more than once.
Don’t disqualify yourself based on years alone. If a job asks for 3 years and you have 1 but you’ve shipped serious projects — apply anyway. Years are a proxy for experience, and real experience speaks louder.
Do Credentials Shorten the Timeline?
Yes, but selectively. A relevant degree signals foundational depth and can compress the familiar-to-proficient gap in a hiring manager’s eyes. Certifications carry weight in specific domains and show validated, intentional learning. But a strong portfolio of deployed, real-world projects often outweighs both — especially in frontend, where your work is literally visible.
The credential doesn’t replace the experience. It vouches for your baseline so the hiring manager trusts your self-assessment faster.
A Simple Rule to Live By
Before labeling anything on your resume, ask yourself: “If they asked me to prove this in an interview right now — could I?” If yes, claim it confidently. If no, drop a tier. That single gut check keeps your resume honest and your interviews stress-free.
Time is a rough measure. Depth, consistency, and real output are what actually move you from one tier to the next. A student who ships three real client projects in 8 months has more claim to “proficient” than someone who watched tutorials for two years. Own what you’ve genuinely earned — and keep building the rest.
Joseph Neilson
Radiation Detection Physicist
266
Answers
Oxford, England, United Kingdom
Updated
Joseph’s Answer
Familiarity and SME status is often correlated with time, but it is not defined by it - it's more about capability. I've known mediocre people who I wouldn't even regard as properly proficient in a certain tool, even after using it for a decade; while faster and more inquisitive people have achieved proficiency in months and approach SME status in a couple of years.
Same goes for certifications - they can be a huge step into expert territory, or virtually irrelevant. There was one tool I got certified in based on a very limited training case study, and I'd be completely unprepared to use it in any broader sense - but I've also seen intensive training courses that will take you from zero to an all-singing-all-dancing expert.
It all depends on various things:
- the specific tool :-
- How complex is it to begin with?
- How much / often do you use it - daily driver or once in a blue moon? The less you use something, the longer time period would be typical for mastery. It's often more the hours than the years - there's a common adage about mastery corresponding to around 10000 hours for a lot of things.
- How much is it dependent on knowing the ins-and-outs of edge cases you only see infrequently through experience, vs how much is well documented or procedurally driven?
- Quality of training and certification?
- You :-
- Strength and applicability of prior connected subject knowledge?
- Your intellectual capacity to learn and process new information
- Your willingness to formally research things you don't know;
- or willingness to give it a go and informally experiment to build understanding
Same goes for certifications - they can be a huge step into expert territory, or virtually irrelevant. There was one tool I got certified in based on a very limited training case study, and I'd be completely unprepared to use it in any broader sense - but I've also seen intensive training courses that will take you from zero to an all-singing-all-dancing expert.
It all depends on various things:
- the specific tool :-
- How complex is it to begin with?
- How much / often do you use it - daily driver or once in a blue moon? The less you use something, the longer time period would be typical for mastery. It's often more the hours than the years - there's a common adage about mastery corresponding to around 10000 hours for a lot of things.
- How much is it dependent on knowing the ins-and-outs of edge cases you only see infrequently through experience, vs how much is well documented or procedurally driven?
- Quality of training and certification?
- You :-
- Strength and applicability of prior connected subject knowledge?
- Your intellectual capacity to learn and process new information
- Your willingness to formally research things you don't know;
- or willingness to give it a go and informally experiment to build understanding
Jennifer Bloomquist- CIPP/US/E, CIPM
Risk Specialist for Privacy and Confidentiality Impact Accessments
23
Answers
Clarksville, Tennessee
Updated
Jennifer’s Answer
Hi L,
The answer to your question is highly specific to what type of job you're looking at. For jobs that require licensure like physicians, teachers, attorneys, therapists, etc., I would say that being a SME takes more time.
In general, having a credential but no practical experience with a topic usually puts someone in the "familiar with" territory. Proficiency is generally obtained in the 1-2 year mark or if you have a degree or graduate degree in a particular topic. Being a SME varies by job. I've known SMEs who focus on one thing in particular and are SMEs in the 1-2 year timeframe. I've also known SMEs which took 5+ years in a role or subject matter experience to get to that spot. Rather than time spent, if we're speaking generally, the more specificity a person needs to have, the longer the time it takes to become a SME. For example, in highly regulated industries, it takes longer because there are legal, regulatory, and knowledge requirements that have to be met. Think the development of pharmaceuticals as an example.
If a the job isn't for something highly regulated, if a person has experience in a topic where they are the go-to person on a topic on a team, that is the more layperson meaning of SME. If you're unsure, you might use the approach of making a list of the things you do and don't know about a topic or tool in a job posting. If you can do most of the usual functions without having to look up how to do them, then I'd say you're solidly in the proficiency category. If you can do just about anything in that tool but commonly have to research and practice how to do them because you're still learning the basic functions, I'd say familiar with or the start of proficiency or midway into the "familiar with" category. It's less of a time spent way of looking at it and more of a question of time to complete a task. If a person is given a normal user level task with a particular tool or in a specific knowledge domain and they generally can just do the task without needing help, I'd consider that proficient. If a person is given a task that is really an obscure thing that most people don't know how to do, I'd call that being the SME.
Another way of looking at it is if on a team everyone has 1 or 2 things that they have deep knowledge on and other people can cover for them when they're on vacation for general use of the tool or knowledge domain but they encounter things that they really had to look into to solve or had to put it in the parking lot to ask you when you return because normal tools at hand don't answer how to accomplish that task that a general user wouldn't know, then the person on vacation is a SME.
If, on the other hand, everyone on a team is cross trained on a topic or tool and everyone generally has the same proficiency and knowledge without highly specialized tasks or skills , then that team may not have a SME at all on that tool or topic. Everyone may be a the proficiency level.
Generally in white collar work, if a job posting lists that the position is for a SME, that means candidate probably isn't being brought in as part of a group in a training class where a whole team does the same thing and is at the same level. Generally, that person is being brought in as the expert with a topic or tool and is being hired specifically because they know that thing/topic/tool as an expert.
The answer to your question is highly specific to what type of job you're looking at. For jobs that require licensure like physicians, teachers, attorneys, therapists, etc., I would say that being a SME takes more time.
In general, having a credential but no practical experience with a topic usually puts someone in the "familiar with" territory. Proficiency is generally obtained in the 1-2 year mark or if you have a degree or graduate degree in a particular topic. Being a SME varies by job. I've known SMEs who focus on one thing in particular and are SMEs in the 1-2 year timeframe. I've also known SMEs which took 5+ years in a role or subject matter experience to get to that spot. Rather than time spent, if we're speaking generally, the more specificity a person needs to have, the longer the time it takes to become a SME. For example, in highly regulated industries, it takes longer because there are legal, regulatory, and knowledge requirements that have to be met. Think the development of pharmaceuticals as an example.
If a the job isn't for something highly regulated, if a person has experience in a topic where they are the go-to person on a topic on a team, that is the more layperson meaning of SME. If you're unsure, you might use the approach of making a list of the things you do and don't know about a topic or tool in a job posting. If you can do most of the usual functions without having to look up how to do them, then I'd say you're solidly in the proficiency category. If you can do just about anything in that tool but commonly have to research and practice how to do them because you're still learning the basic functions, I'd say familiar with or the start of proficiency or midway into the "familiar with" category. It's less of a time spent way of looking at it and more of a question of time to complete a task. If a person is given a normal user level task with a particular tool or in a specific knowledge domain and they generally can just do the task without needing help, I'd consider that proficient. If a person is given a task that is really an obscure thing that most people don't know how to do, I'd call that being the SME.
Another way of looking at it is if on a team everyone has 1 or 2 things that they have deep knowledge on and other people can cover for them when they're on vacation for general use of the tool or knowledge domain but they encounter things that they really had to look into to solve or had to put it in the parking lot to ask you when you return because normal tools at hand don't answer how to accomplish that task that a general user wouldn't know, then the person on vacation is a SME.
If, on the other hand, everyone on a team is cross trained on a topic or tool and everyone generally has the same proficiency and knowledge without highly specialized tasks or skills , then that team may not have a SME at all on that tool or topic. Everyone may be a the proficiency level.
Generally in white collar work, if a job posting lists that the position is for a SME, that means candidate probably isn't being brought in as part of a group in a training class where a whole team does the same thing and is at the same level. Generally, that person is being brought in as the expert with a topic or tool and is being hired specifically because they know that thing/topic/tool as an expert.
William Vvuko
Retired engineer
234
Answers
Moyo, Northern Region
Updated
William’s Answer
Hi L,
This is a very interesting question.
Experience is evaluated in two ways: quantitative (years accumulated) & qualitative (content of experiential learning). The truth is that people learn at different rates: some are fast, others are average and some slow - they may eventually all be deemed competent if they were working in similar roles, based on standardized competence assessment criteria.
As someone who was involved in shortlisting candidates with engineering backgrounds for roles in the business I worked for, I would generally look at the qualitative aspects of experience.
Considerations include technical knowledge: understanding of the underlying principles and demonstrated ability to apply them in real life situations; ability to deal with complexity, ambiguities in the absence of substantive data - gut feel; leadership skills - ability to bring people together, providing a compelling vision and enlisting their consent to make it happen: within team dynamics, your leadership qualities stand out even when you are not in a leadership role; demonstrated ability to identify and resolve problems - especially the complex ones (it's the main vehicle for continuous improvement including innovations & creation of new ideas); and emotional intelligence (EQ) - your ability to read situations correctly and act upon them appropriately based on your knowledge of self & others: this is the most important contributor to success at the place of work.
Businesses often recruit young professionals mainly based on potential (ability to learn & apply knowledge and skills) and allow them grow through planned & controlled competence-based learning and training - one's initial position on the Potential vs. Performance Grid (derived from People Balance Sheet) determines this trajectory.
At the place of work, broader knowledge makes you more resourceful. Ability to consistently get things done on time in full and to the required standard makes you get ahead.
A Subject Matter Specialist is that person who has deep knowledge & understanding of the area/subject under consideration - such a person can mentor, train and assess the competence of persons in the given field.
Knowledge & skills can be acquired formally (through the education system & training) and informally through experience (tacit knowledge). Competence assessments do not distinguish between the two when deeming a person competent in a given role.
Tacit knowledge, when distilled & codified becomes formal knowledge (the cutting edge ones usually form part of company secrets).
I truly hope this sheds a bit of light on your query.
Best regards.
This is a very interesting question.
Experience is evaluated in two ways: quantitative (years accumulated) & qualitative (content of experiential learning). The truth is that people learn at different rates: some are fast, others are average and some slow - they may eventually all be deemed competent if they were working in similar roles, based on standardized competence assessment criteria.
As someone who was involved in shortlisting candidates with engineering backgrounds for roles in the business I worked for, I would generally look at the qualitative aspects of experience.
Considerations include technical knowledge: understanding of the underlying principles and demonstrated ability to apply them in real life situations; ability to deal with complexity, ambiguities in the absence of substantive data - gut feel; leadership skills - ability to bring people together, providing a compelling vision and enlisting their consent to make it happen: within team dynamics, your leadership qualities stand out even when you are not in a leadership role; demonstrated ability to identify and resolve problems - especially the complex ones (it's the main vehicle for continuous improvement including innovations & creation of new ideas); and emotional intelligence (EQ) - your ability to read situations correctly and act upon them appropriately based on your knowledge of self & others: this is the most important contributor to success at the place of work.
Businesses often recruit young professionals mainly based on potential (ability to learn & apply knowledge and skills) and allow them grow through planned & controlled competence-based learning and training - one's initial position on the Potential vs. Performance Grid (derived from People Balance Sheet) determines this trajectory.
At the place of work, broader knowledge makes you more resourceful. Ability to consistently get things done on time in full and to the required standard makes you get ahead.
A Subject Matter Specialist is that person who has deep knowledge & understanding of the area/subject under consideration - such a person can mentor, train and assess the competence of persons in the given field.
Knowledge & skills can be acquired formally (through the education system & training) and informally through experience (tacit knowledge). Competence assessments do not distinguish between the two when deeming a person competent in a given role.
Tacit knowledge, when distilled & codified becomes formal knowledge (the cutting edge ones usually form part of company secrets).
I truly hope this sheds a bit of light on your query.
Best regards.