Photo by Joelk75.
Many of our blog posts are geared toward Ruby developers actively pursuing new RoR opportunities. But the truth is, most Ruby developers already have a Ruby gig they are fairly happy with.
Well, this post is for all of you already employed and generally content Ruby developers out there.
We have a question (and answer) for you.
The Question: When is the best time to look for a new RoR gig?
The Answer: When you already have one.
It might sound counterintuitive, but we’re serious about this, and here’s why:
Looking for a job out of necessity is far different from keeping your eyes peeled for a great match and set up. Many developers get caught up in their work and forget that it’s important to keep an eye out on the changing landscape of opportunities. This has never been more true than today as the post-recession surge in demand is bringing to life more Ruby opportunities than we’ve seen since 2008.
Here’s the reality: even if you love your current gig, at some point you’ll need (or want) a new one. So, why not keep your eyes peeled in the interim?
"Well," you say, "it takes too much time to comb through potential leads and keep a constant eye out for new opportunities."
Guess what? That is what we do. It is literally our job to be on top of new Rails openings as they come up. We scrape and sort through hundreds of Rails jobs posted online everyday. If there’s a new opening out there, we’ll know about it. Seriously.
The good thing for you is that you don’t need to do any of the work. Since we do it anyway, all you have to do is tell us what would interest you and we can keep an eye out for you.
We have this type of relationship with some of our developers currently. We’ve even placed developers who weren’t looking but said, “I would only be interested in a job in this very specific industry, in this location, with this salary range, and working with this type of team.” While we didn’t have it right that moment, a few months down the line — we found a company that exactly lined up with his requirements.
The truth is, letting us know what you would want, ideally, in your next job is an easy, passive way to keep an eye out. When we place developers that were only passively looking, these placements oftentimes turn out to be the best match for both the developer and the company. This is because a match was made not out of desperation but out of true fit for both the candidate and company.
So, our suggestion for you today is to shoot us a quick email. It can literally be two sentences, e.g.:
I’m happy now but if you come across something like this, pass it my way: Team Lead, RoR w/UI Focus, big into TDD, in SF Proper, in the Green Tech industry.
-A Smart Ruby Developer
Shooting us this brief email will allow you to avoid the “trying to drink from a fire hose” experience of looking at job boards. But it gets better. Not only do you avoid spending the time browsing job boards when you’re not really looking, but you don’t have to worry about whether the company is seriously hiring or will be able to pay you. We only work with real clients, e.g. companies that have money and are serious about hiring. Today. And finally, instead of sending your resume to that catch-all firstname.lastname@example.org address, we have the ear of the hiring manager and, if you want to pursue the job, we connect you directly with him/her.
Keeping an eye out while you already have a job you’re content with is annoying. So annoying in fact, that most people don’t do it. Since it is our job anyway, why not let us do it for you?