I recently received a job spec that had the most ridiculous “Required” skill set for an “Analyst Programmer”. I though I should share it with you as I have just spent the last 10 minutes cleaning tea out of my keyboard with cotton bud’s. Here is how it was presented in the email:
* C# Java Script Java
* ASP.NET 1.1 ASP.NET 2.0 J2EE
* Visual Studio 2003 SOA Visual Basic
* Winforms Development Visual Studio 2005 Linux
* SQL Server 2000 (TSQL and Database Design) AJAX Data Cleansing
* Full Life-Cycle SQL Server 2005 SMS
* Object Oriented Design Multi-channel CRM IVR
* Strong verbal and written communication skills Call Centre UML
* Organisational and problem solving capabilities ISO9000
Now obviously this list was formulated by someone who has no idea what these things are, so lets brake that up into a proper list…
Skills Required:
- C#
- Java Script
- Java
- ASP.NET 1.1
- ASP.NET 2.0
- J2EE
- Visual Studio 2003
- SOA
- Visual Basic
- Winforms Development
- Visual Studio 2005
- Linux
- SQL Server 2000
- TSQL
- Database Design
- AJAX
- Data Cleansing
- Full Life-Cycle
- SQL Server 2005
- SMS
- Object Oriented Design
- Multi-channel CRM
- IVR
- Call Centre
- UML
- ISO9000
I can’t imagine anyone actually knowing how to do all of these things. If they do, they would only have a cursory knowledge of each think and be useless at programming any one of these. I could understand this for a Architect or Evangelist role where depth of knowledge is not required. But for a programmer there is a necessity to concentrate on one technology at a time, and only with 2-3 years commercial experience would you be considered “good” at it.
Whoever this employer is needs to come to the realisation that this is about 5 (or more) roles all mashed together:
- Architect
- .NET Developer
- Java Developer
- Web Developer
- SQL Developer
If I am wrong, please let me know! And if you are one of these “Uber-Analyst Developers” then…well, I don’t believe for a moment that you could actually do all of these things well…
Advice for an employer: If you are an employer, only define a list of the absolute essential skills. If you find someone good enough at those, then they can learn the bits and bobs that go with the others.
Advice for a job seeker: If you are a prospective employee, don’t lie and say that you know all of these things (I have interviewed my fare share of people who did), but instead say that you know a set of core things, and that you can learn the rest…
Advice for everyone: I am not saying that it is the holy grail or anything, but read Joel on Software , many of his articles are just common sense, but other are down right genius (and, no, I am not looking for a job at Fog Creek Software ;).
Especially:
Technorati Tags: Personal Fail VS 2005
What to read next
Interviewing for Microsoft
A personal account of interviewing for a Microsoft Application Developer Consultant role, detailing the process, technical requirements, and …
Becoming a better developer
Practical steps for improving as a developer, including ongoing learning, project work, community involvement, blogging, and embracing …
A change for the better #2 - Aggreko to SSW
Describes a career move from Aggreko to SSW, focusing on software architecture, ALM, TFS migrations, and applying productivity rules in team …
Essential Skills Every Agile Consultant Needs: Mastering Domain Knowledge, Active Listening, and Honest Communication
Covers key skills for agile consultants: mastering domain knowledge, practising active listening, and communicating honestly to drive …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …