Knowledge of C++

I was recently asked to describe my experience with C++ in terms of being a: Novice, Beginner, Intermediate User, Advanced User or Expert.

Clearly I am not an expert or I would know the answer to this question, but how do you guys define the varying levels of competency. Lines of code written? Ability to debug?

Here are a few thoughts about programming in general.

* Beginner/Novice - written a couple programs
* Intermediate User - written many programs and has a solid understands of the basics. Can debug their own code.
* Advanced User/Expert - This is where you find a wide variety of programmers. You will find people, who classify themselves in this area, who write excellent code that is bug free, well documented, and their fast. You will also find others that place themselves in this category who are prone to bugs, slow, poor documentation, etc. Just because someone has done something for along time doesn't mean their excellent.

I would say the best approach to illustrate to someone your programming skills, is to talk about software projects and discuss the details. I like to see a track record.

There are no hard and fast rules. Different industries and indiduals are going to have different interpretations. I am now working in an industry where an engineer is deemed "senior" at 7 years whereas my personal metric based on engineering capability would place a few people at senior after maybe 10 years, with the majority at 15 or even 20 years.

If I was interviewing someone and asked them this question, it would be to assess how they respond rather than to determine an accurate indication of their capabilities. Capabilities would be determined with pointed questions.


Given that, these would be my personal metrics of a C++ software engineer:

Novice - Has studied software concepts but very little hands on projects. Knows how to spell 'C++'.

Beginner - Mastered "hello world" and other simple programs. Understands the language syntax and tools but has limited experience. Understands object oriented principles and how to use them.

Intermediate - Implements complex projects with help of experts. Has good knowledge of design patterns, data structures, algorithms, development tools. Can integrate various technologies into projects. Can debug complex problems given enough time.

Expert - Has architected and implemented many complex projects. Understands tradeoffs in data types, structures, and algorithms. Can debug problems in short order. Undertands nuances of tools and language and can implement non-standard solutions when needed. Serves as a mentor or subject matter expect to those below expert level. Understands tradeoffs in software implementation and hardware resources.

I see the other responses and agree broadly but I would also add the importance of asking the right question.

C++ is obviously more than an OOP extension to C, but this is really only apparent when applied to specific environments.

For example: C++ as part of Visual Studio is far mor about understanding Windows and how Microsoft's OOP paradigms fit into Windows; an embedded system C++ compiler, however, may have its benefits in how it fits an OOP kernel or other program layers, or may just be bloated way of implementing C on a microsystem.

My point is this; it's not just how well does a potential programmer know C++, but also how well do they know the environment to which is being applied.

A good programmer will be flexible; but above all honest about their experience. So I would always look for someone who is open about what they can do and in what environments.

As for whether it's important to 'sell oneself' I don't know - I would certainly not clasify myself as an expert to my peers, but I probably appear as one to a lay person.

Not sure if this helps - but maybe it's no bad thing to ask more questions.