Live data from Hacker News

Programmer's Competency Matrix for SDE hiring parameters (2008)

sijinjoseph.netlify.app

31–40 of 51 posts

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#31
Most of these are ok to roughly score developers. Might want to weigh the importance by position and calibrate against the other candidates/employees in that org.

However, one criterion I disagree with is years of experience. I suspect (based on personal experience) that the variance of the other categories with respect to years of experience is a lot higher than one would think. So there's no real utility to including it.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#32

I remember seeing this matrix back in 2008: https://weblogs.asp.net/sjoseph/programmer-competency-matrix

That explains git being at the highest level.

That was my first clue that this has been kicking around a while.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#33

Makes everything sound so mechanical and boring. Do they want normal people or some bot like creature that they can just assign numbers in a matrix? Depressing.

You don’t want to hire boring bot-like people, but you also don’t want a totally subjective hiring system full of bias. I think having an objective scoring of some sort is a good reference even if it’s not the final decision.

Here’s the thing: there is precious little if any empirical evidence suggesting that what is objectively measurable (e.g. solutions to textbook CS problems) has utility as an indicator of engineering competence. There are exceptions of course, for example in roles requiring a person implement such things as for a library, but these aren’t the rule.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#34
post #27

My thoughts: First of all, the third column here is highly editorialised. If you have a look at anything related to languages, he always lists Erlang, Oz, Prolog -- I wonder why? I won't go into a diatribe on this-or-that nonsense but it would be fairer to talk about languages by their capabilities i.e. either include more languages like Ocaml (which is my hill to die on for "high-society" languages) or just say "has…

> As for the Systems Programming section, does he really think that knowing how a compiler works is a system-related topic?? and why is that level 1? shouldn't the first level be understanding things like system calls, filesystems, drivers, kernel operation?

I think the idea is that most people will start exploring the world of programming from higher layers working their way down. People use software, then they write software with tools (languages), then they try to understand the tools, then they try to understand what the output of the tools mean on a yet deeper level, going down the rabbit hole all the way down (to physics? but I guess the lines is drawn elsewhere).

This may be wrong but it's obvious from the rest of the matrix that this is probably just based on how the author and maybe their friends gained "proficiency".

None of this is generally applicable. I do think the,matrix is still valuable. It provides a view of how some people may evaluate competence (even if misguided wrt ordering/levelling) and provides a set of goals that are not bad per se. Being on the highest levels mentioned there does probably in fact translate to a certain high degree of experience and competence.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#35
post #8

Earlier quoted context omitted.

Is nano really That Bad? It's always been good enough for my needs, and in the cases where it's not I generally hop on Sublime or vscode, make the changes I want to make, then paste it into my term.

It isn't, but frequently the default editor is set to vim. That said I would question the judgement of anyone that judges you based on your favored editor. Except emacs, those folks will burn in hell.

In interviews I ask candidates what their favourite editor is. Not to judge the choice, but to try to gauge if they care enough about the tools they use to have looked at different ones and taken a position.

I feel that there is a strong correlation between overall competency and whether someone cares about their tools, and their passion for their editor is a way of getting hints of that

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#36

A lot of dismissive complaints that boils to "this is objectifying programmers", and yes I get it. But now I'm on the other side (VP, but still coding), and actively recruiting, I realized some things taken for granted from myself and my good engineers, are still missing from a large number of candidates I've interviewed so far. I usually ask the candidate for a live coding test over zoom. "Here's what you need to co…

That's why programming has declined from Software Engineering to 'coding'. I'm sure there are similar scoring tables in Civil Engineering, and Engineers there dont whine because they don't know or y principle.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#37
post #27

My thoughts: First of all, the third column here is highly editorialised. If you have a look at anything related to languages, he always lists Erlang, Oz, Prolog -- I wonder why? I won't go into a diatribe on this-or-that nonsense but it would be fairer to talk about languages by their capabilities i.e. either include more languages like Ocaml (which is my hill to die on for "high-society" languages) or just say "has…

> As for the Systems Programming section, does he really think that knowing how a compiler works is a system-related topic?? and why is that level 1? shouldn't the first level be understanding things like system calls, filesystems, drivers, kernel operation? I think the idea is that most people will start exploring the world of programming from higher layers working their way down. People use software, then they writ…

I would go on further and say that it's not only for the recruiters but also for the hires to understand whay are the general skillsets they can have to expand over a period of time.

Block-chain Dev, Android Dev, AI/ML devs are domain specific but in each of those there are atleast 3-4 domains mapping out in general from the PCM.

There will be a domain specific competency matrix on top of PCM.

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#38
post #8
post #6

Earlier quoted context omitted.

the IDE section is a bit dated. as a hiring manager, my belief is that IDEs are good enough (and even have collab features that are good in work-at-home-epoch) that it's not an unreasonable to never use/never have used vi/vim/emacs. If you're doing server administration, not being able to use vi is unacceptable; but these days everything is deployed by container and logging into raw linux systems is not really a thin…

Is nano really That Bad? It's always been good enough for my needs, and in the cases where it's not I generally hop on Sublime or vscode, make the changes I want to make, then paste it into my term.

It's not that nano is bad, but for server administration you cannot be sure what exists on the other end, and due to security rules you can't always install what you want, except, there will always be vi. Nano might not be there when you need it (I have learned this the hard way).

Re: Programmer's Competency Matrix for SDE hiring parameters (2008)

#39
post #28

Earlier quoted context omitted.

How do you standardize this across applicants? I'd worry that there's not enough to compare across candidates doing something as generic as this.

In my experience it’s used as a prescreen qualification- the actual interview of multiple candidates happens afterwards or in a second round.

But aren't prescreens subject to the same subconscious bias as the actual interview?
Post reply on HN