This isn't consistent with my most recent experiences recruiting: we
advertised at all levels, and received very few applications from junior
developers. You're welcome to search the list and find the job ad I posted.

At the time, we were looking specifically at both ends of the spectrum:
either somebody shit hot to help teach us some cool new tricks (which is
what we got, in the end) or somebody fresh that who could bring in some
optimism and take some of the load off while we worked out how to fix
everything.

It's also possible that I, being the one who posted the ad, was being
deliberately exclusionary: I only wanted juniors to apply via the mailing
list rather than via recruiters or seek. I wanted somebody who was keen
enough about Ruby to be part of the community (or at least be aware that it
exists), rather than somebody who's just graduated a Java-heavy CS degree
and will now latch on to anything that will help them make rent this month.

So it's possible that we're not hostile towards juniors - but possibly
we're doubtful of juniors put forward via recruiters, thanks to being
burned before by resume-fiddling and other such nasty things.

Also - do these several amazing juniors have github accounts, or other
proof of capability? Are they on this list (at least filtered for anything
with [JOB] in the title)?


On Fri, May 3, 2013 at 2:26 PM, Ashley Pettit <[email protected]>wrote:

> Hi Guys,
>
> I've noticed a bit of a problem with the ruby community and I wanted to
> voice my concerns.
>
> Firstly let me say the ruby community is great. Full of passionate people
> who love what they do and 9 times out of 10 something built in ruby is
> better than something not purely because the developers are so passionate
> about creating awesome products.
>
> So where's the problem?
>
> Ruby is a language which has been embraced by start-ups and small-medium
> sized businesses. It's not something the larger companies have taken to.
>
> Why is this a problem?
>
> Small-medium business do not have the time to train juniors. They want
> people who are already great. They release jobs where there is an immediate
> requirement. They don't hire just because there is misc development to be
> done. They hire for a specific project or specific set of work. With other
> languages like .NET, junior developers are able to get experience with
> larger companies who run graduate programs and who can afford to train
> people for future rewards. With Ruby however, this is not the case.
>
> Again why is this a problem?
>
> No company that I know is currently running ruby graduate programs, no-one
> is hiring talented juniors and no-one is investing in developing people's
> potential. Many really talented junior developers with < 12 months
> experience are being left out in the cold unable to find work and are
> forced to learn a language like .NET because they can't find ruby work. I
> personally know of at least several great junior Rubists who have so much
> potential yet no company will hire them as they don't have the magical 2+
> years experience to be considered a "Mid-level developer".
>
> I personally think that the ruby community (especially employers) needs to
> support junior rubists a little more or the community will simply stagnate.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby or Rails Oceania" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Michael Pearson

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rails-oceania?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to