We're looking for senior (team-lead) and regular developers. It's a PHP job, and we exclusively hire remote workers. We have about 16 developers at the moment, but we're expanding because we have a lot of projects on the back burner that we'd like to get started on. We won't be hiring you for any specific project; rather we'll be picking projects from the backlog once we have a sense for your strengths.
We only hire people who can do everything. You have to be able to write backend PHP code, HTML/CSS, JavaScript, and SQL. We don't want to have people employed who we can't just point at any problem that comes up. People do tend to find their own niche, admittedly, and we're fine with you being better at some things than others.
...unless you're a great search developer, in which case we'll hire you anyway and lock you in a small room where you will never do anything but improve our search. <3 <3 <3
I will warn you that, no matter how awesome you are, everyone we hire spends their first 90 days in the small-projects and bugfixes silo. We think that it's a great way to make sure that everyone knows the codebase, which is large and sprawling. After that point we start moving people onto project teams.
That codebase? It's 10 years old and written in PHP. This implies certain things. It predates proper object support in PHP, and almost every PHP framework. So we're running an in-house framework. Understand that you will have to deal with varying eras of code. Also understand that you may have to hold your nose and just fix a bug in an old component without taking the time to rewrite it to modern standards. :)
I'm exaggerating the horribleness of the codebase for effect. Lots of it is in good shape, and we've been working on incremental rewrites to fix up the worst legacy spots. There are certainly bad bits, but they're also working bad bits, whose badness largely comes from being hard to bend to new use-cases.
However! I see a lot of developers who would have a hard time fixing a bug / making a small change in an area which has a lot of legacy cruft present without going and rewriting the whole thing. Now, they are right that rewriting it is probably the best course of action from a codebase-health viewpoint... but it's not necessarily the actual best use of their time. If code is working then it's not an urgent priority that it get rewritten.
To be slightly trite, "perfect is the enemy of good."
That's why we'd like to get developers who are okay with the idea of working on a codebase that contains legacy code. And that's why I'm a little bit over the top about it.
Sorry, but this seems very odd to me that a developer would be almost 50% off in estimating their own team size, then post a second comment correcting it only halfway, and finally getting the correct answer by looking at your 'About Us' page?
What kind of working environment do you have that in a team of less than 25, a member of that team can be that far off-base?
Lots of communication via Skype chats in which I don't pay attention to the count of people in the room, and developers split into a bunch of small product teams so I don't have personal dealings with most of them on a daily basis.
Also I'm bad at estimating these things apparently. :P
It doesn't seem that unreasonable to think that they have a continual need for additional developers.
They're also not the only company that has a "We're Hiring" post in each of these threads which strikes me as a good thing--assuming the term of employment for new developers is longer than a month. :)
We're looking for senior (team-lead) and regular developers. It's a PHP job, and we exclusively hire remote workers. We have about 16 developers at the moment, but we're expanding because we have a lot of projects on the back burner that we'd like to get started on. We won't be hiring you for any specific project; rather we'll be picking projects from the backlog once we have a sense for your strengths.
We only hire people who can do everything. You have to be able to write backend PHP code, HTML/CSS, JavaScript, and SQL. We don't want to have people employed who we can't just point at any problem that comes up. People do tend to find their own niche, admittedly, and we're fine with you being better at some things than others.
...unless you're a great search developer, in which case we'll hire you anyway and lock you in a small room where you will never do anything but improve our search. <3 <3 <3
I will warn you that, no matter how awesome you are, everyone we hire spends their first 90 days in the small-projects and bugfixes silo. We think that it's a great way to make sure that everyone knows the codebase, which is large and sprawling. After that point we start moving people onto project teams.
That codebase? It's 10 years old and written in PHP. This implies certain things. It predates proper object support in PHP, and almost every PHP framework. So we're running an in-house framework. Understand that you will have to deal with varying eras of code. Also understand that you may have to hold your nose and just fix a bug in an old component without taking the time to rewrite it to modern standards. :)
http://deviantart.theresumator.com/apply