Skillset of a Selenium Engineer

Note
This article is dedicated to show an approach, how to find the optimal skillset of a Selenium Engineer, based on the real project market. Please be aware, that the scope of my study in this article is on the German project market only, examining just 26 projects. So the statistical population is small and focussed, but current (no project description is older than 11.11.2012). There is no distinction between must-have-skills and nice-to-have-skills – all mentioned skills are weighted the same.

Results
Programming languages
* 85% of the projects want Java-skills (of these 68% explicitely want JEE-skills).
* 15% want PHP-skills
* 8% want Obj. C-skills
* 4% want C#-skills


Build-tools
Just 35% of the projects want skills in build-tools (of these 78% want Maven). Perhaps this percentage is so low, because having that knowledge is considered as self-evident for Java-programmers … like knowing your IDE.

CI-Tools
At least 38% of the projects want CI-skills (of these explicitly want: 40% Jenkins, 20% Hudson, 10% Bamboo).

Javascript
Not really surprising, that 58% of the projects want JavaScript-skills. But surprisingly 33% of these explicitly want jQuery-skills – hey, managers, shall we test or paint …

Testing Frameworks/Testing Tools
This category is really interesting, as it reveals much about the test setup of the projects:
The winner is JUnit – 62% of the projects want skills in that one. Don’t the responsibles know TestNG …?
12% of the projects want TestNG-skills.
I could hardly understand that they’re looking for skills in HP QC (8%), but why the hell they are looking for HP QTP-skills (8%) in Selenium-related projects …
Only 4% are looking for FitNesse, which makes me sad …
Only 4% (=1 project) are looking for BDD-Tools (in that single project, it’s Cucumber). Don’t they know, that BDD is hip, too?
Few are looking for PHPUnit(8%), JMeter (8%), CasperJS (4%), GreenPepper (4%), Tosca (4%), JDepend (4%), SOAP UI (4%), TestLink (4%).

Agile Methodologies
Wow, 58% of the projects want Agile Skills (of these 93% want Scrum, just 7% want Kanban). Is this because all the projects really work with Agile, or is this because asking for Agility is in vogue …

ISTQB
Being such important for the general software-testing-project-market, ISTQB-certificates are really underrepresented in Selenium-related projects. Only 12% of the projects ask for that!

miscellaneous
At least 23% of the projects are looking for skills in Web Services (of these 50% explicitly want it RESTful, and 10% want it SOAPy). 27% ask for AJAX-skills.
12% ask for skills in code-metrics (all of these want them in sonar!).
As a Selenium Engineer it seems, that you should be able to understand things like: SELECT * FROM mywebapp.testdata WHERE type = ‚edge-case‘ – 73% of all projects want you to database (of these 31% in Oracle, 26% in DB2, 4% in mySQL).

„Corner Cases“
One project just ask for Selenium – no other skills are wanted.
Just one project offers an opportunity to work remote.

Methodology
1.) As this study is focused on Germany, I went to all (known to me) German project exchanges on 8th/9th/10th Jan. 2013. For this study I only used project descriptions, that were accessible without registration. Forthermore I only regarded projects in Germany and for freelancers (no permanent positions).
2.) Every project exchange has some sort of search-tool, where I entered just „Selenium“.
3.) I made a fundus with screenshots of the resulting project offerings:


4.) I filtered the doublets.
[Excursion: At least in case of German project market it seems, that the enterprises generally don’t use the project exchanges – only recruiting agencies post project offerings there. Some enterprises contract multiple agencies and so different offerings appear for the same project. Unfortunately the agencies don’t reveal the name of the project’s enterprise (for commission reasons). Anyhow, similarities in skillsets, project location, project timeframe and time of posting are something like a fingerprint of a project. With little experience you can „see" the same project behind different offerings and so filter the doublets.]
5.) I made a list of the skills/skill-categories, that are relevant to my study (not „HTML“ which is obviously needed in every Selenium-related project). You find them in the first column of the Excel.
Excel-file to download
6.) I filled the Excel project-by-project manually.
7.) At the end I extrapolated the results from the Excel.

Outlook
You don’t need a PhD, to conclude that the skillprofile in a project offering reflects the „anatomy“ of real-world projects. So, beyond freelancers, this approach can get useful for tool vendors, service providers, software architects …

Due to my time restrictions, this study is pretty limited. But this approach can be picked up e.g. in seminar papers, interships, (…) and extended in many aspects. E.g. the statistical population should be much broader to get scientific statements and to apply some sophisticated statistical analysis.
This study based only on German project exchanges within a short timespan. People with good relationships to employees of project exchanges may get data with a much longer timespan. Job exchanges (like monster or stepstone) may be covered, too.
Future research can distinguish between must-have- and nice-to-have skills, can include softskills, …
This post is about Selenium only, but the approach may be applied to any other core-skills (…)