How to (really) evaluate a developer's skillset

How to (really) evaluate a developer's skillset

The interpretation of résumés and curriculum vitaes in the technical world is often thought to be a straightforward affair.

It is argued to be comparatively easier to assess precise technical skills than it is to measure expertise and proficiency in (for example) the arts, careers involving social sciences, or roles where defined competencies are more intangible and perhaps subjective.

A developer knows x-number of languages, y-number of development environments and toolsets, has worked for z-type companies in specific projects teams of an exact size… and is comfortable with one specific platform (as in Windows, Linux, Apple, other) or a defined combination of platforms.

Further still, a developer will have a specifically classified ‘type' i.e. they will be a User Interface (UI) specialist, a database administrator or a sysadmin (not developers by some definitions, but still essentially in the same family), a server-side developer, a security developer, or a hardcore ‘command line' programmer or perhaps even a games developer.

This all makes the hiring, placement and remuneration of developers supposedly very straightforward, you could expect. The trouble is, it's not that easy in the real world.

To continue reading...


« Appian vs. IBM BPM: Buyer's guide and reviews


The birth of consumption- & outcomes-based IT pricing »
Adrian Bridgwater

Adrian is a technology journalist with over two decades of press experience. His primary focus is dedicated to examining software application development issues. He also has a special interest in open source, data analytics and data intelligence, cloud computing, mobile devices and data management. He has worked across print media, newspapers and television.

  • Mail


Do you think your smartphone is making you a workaholic?