mirRoR Index
2,468.16 +100.2 (4.23%)Job Strength Index
1,854.92 +98.3 (5.60%)Developer Strength Index
613.24 +1.9 (0.31%)About the mirRoR Index:
The mirRoR Index is our way of tracking the health of the Ruby on Rails community. The index is the sum of our Job Strength Index and Developer Strength Index.
Since our start in 2006, we've increasingly relied on various analytics to track trends, illustrate opportunities, and even backup our own hunches and anecdotal observations. The types and amount of data we've tracked and stored has increased over time and so has its utility for us.
We've decided to share this data with the Rails community since we thought others may find it useful as well (or at the very least, geekily amusing).
The Job Strength Index is comprised of the following components:
- 40% New Ruby on Rails jobs
(30 day moving average)
We monitor scores of sources for new Rails opportunities daily, de-duplicate, and evaluate them. - 40% First Time Rails Employers
(30 day moving average)
Each day we cross-reference new Rails jobs with our historical data to determine which jobs are with employers hiring a Rails developer for the first time. - 20% mirRoR Revenue
(90 day moving average)
Though we're only involved in a small percentage of total Ruby on Rails deals, we believe it is significant, and indicative of total hiring activity.
The Developer Strength Index is comprised of the following components:
- 40% New Ruby on Rails Developers
(30 day moving average)
Each day we monitor a few dozen sources (plus referrals) to discover new Rails developers. - 40% Existing Ruby on Rails Developer Activity
(30 day moving average)
We count the number of Rails developers we already know who are actively searching for a job with us. - 20% Average Ruby on Rails Developer Salary
We take the average developer salary for jobs we fill and massage the data a bit to eliminate anomalies.
Each index is set to 1,000 as of early July, 2009. While we have data as far back as January 2007, the collection and storage methods changed too often to fit this model.
By July of 2009, we had been tracking the same data points, in the same ways, for long enough to consider it an appropriate base. Perhaps later we'll try to aggregate more of our old data to generate an accurate historical picture. We're also considering city/region specific indexes, as we've noticed activity between them is not always correlated. (SF is hot right now, NY not so much.) Until then, enjoy the mirRoR index!
Each index is updated automatically at noon Eastern Time every day, posted here, and tweeted to @mirRoRindex. (We have written some code that analyzes our business practices and pulls all necessary data into the indexes automatically.)
Jobs RSS