News for hackers. Stuff that matters.
Re:Stop Speaking in Bullshit by cperciva on Thursday October 14, 2010 @02:35AM (#1790038)
The strange thing about this article is I read the first patch of job descriptions and I thought you were poised to make fun of them

Me too. This bit could describe the local transit system: "We’re profitable, make the lives of hundreds of thousands of people better every month, have a rapidly expanding user base, and napping is an encouraged part of our corporate culture."

Maybe I'm unusual, but my idea of a perfect job posting is one which says something about the job. Don't write platitudes about how you're looking for people who think outside the box; say "we think the most exciting thing in the world is designing algorithms to target advertising better, and that's what you'll be doing if you get this job".

Re:Stop Speaking in Bullshit by hasenj on Thursday October 14, 2010 @04:17AM (#1790221)
I actually find it boring to apply for a job to "design algorithms to target advertising".

Think about it: do you want to do that for the next 10 years of your life? Do you want the next 10 years of your life to revolve around such a thing? Even if you don't mind it: is that what entices you to apply for the job?

I don't care what the work itself is. I care about the environment and the culture.

I'd rather design a spread-sheets application in a hacker-centric culture, than design hard-core search algorithms in a typical management-and-sales-centric culture.

Re:Stop Speaking in Bullshit by pmjordan on Thursday October 14, 2010 @04:28AM (#1790249)
Seriously? Rather you than me. They're hardly going to advertise having a crappy company culture. ("You'll be reporting directly to two different managers with opposing objectives, but don't worry, we provide a generous mental health package!") That's for you to work out by reading up on the company and when you go to the interview. Plus, you're claiming a false dichotomy. I doubt great culture and great tech challenges are negatively correlated.

Besides, the "next 10 years of your life" argument is a strawman. If you don't want to be working on the same, hard micro-problem forever, pick a smaller company, where your work will vary wildly. Sure, not all of it is going to be solving super hardcore problems, but I'd want evidence in the job description that there are interesting challenges ahead.

Re:Stop Speaking in Bullshit by hasenj on Thursday October 14, 2010 @04:43AM (#1790279)
They don't have to advertise a crappy culture, it will just manifest itself as bullshitting.

> pick a smaller company, where your work will vary wildly

Exactly!

Re:Stop Speaking in Bullshit by sgift on Thursday October 14, 2010 @04:37AM (#1790266)
No, I don't want to do that for the next 10 years, but I want to know that they expect me to do it. Maybe not for the next 10 years, but a least initially. And if I don't like this I can decide to pass on the opportunity.

Even with good environment and culture you still have to do the work. Every day. For the next few years. So, I think it would be a good idea to know if you like to do what they want you to do.

Re:Stop Speaking in Bullshit by nadam on Thursday October 14, 2010 @04:59AM (#1790305)
It's not only the culture what is important for me, but what are my strengths, what am I good at? If I do what I am good at that can be the win-win situation. I am not especially good at the frontend work they described. I mean I could do the job, but it is not my strength. I am better at creating algorithms, and I am also more enthusiastic about that kind of work. Also they mentioned lots of dynamic languages. I am better at a job where I can go deep into problems preferably using only one or two languages. And I better like let's say Scala than all those dynamic languages. I am also a speed-optimization enthusisast: at speed all those mentioned languages suck. Company culture is important, but by far not the only important thing.
Re:Stop Speaking in Bullshit by cperciva on Thursday October 14, 2010 @12:53PM (#1791595)
I don't want to design algorithms for targetting adverts, either. That's why I think job postings should include such information -- so that people can say "nope, not interested" without going through a lengthy interview process.
Re:Stop Speaking in Bullshit by RyanMcGreal on Thursday October 14, 2010 @07:27AM (#1790530)
>This bit could describe the local transit system

You don't happen to live in Toronto, do you?

Re:Stop Speaking in Bullshit by kareemm on Thursday October 14, 2010 @02:09PM (#1791915)
He lives in Vancouver. It applies to BC Transit, but even more so to the TTC.
Re:Stop Speaking in Bullshit by wot on Thursday October 14, 2010 @02:48PM (#1792088)
I would have guessed San Francisco.
Re:Stop Speaking in Bullshit by cperciva on Thursday October 14, 2010 @12:50PM (#1791578)
No, Vancouver.
Re:Stop Speaking in Bullshit by mfukar on Thursday October 14, 2010 @02:59AM (#1790090)
I don't think it's unusual; it's very rare for job postings to say anything of substance about what the job/position really entails. From May to September, while I was looking for a job, I must've read a thousand or more of job descriptions, and none (OK, maybe a handful) would leave me confident that I knew what I'd be doing there, in case I got the job.

It was extremely frustrating and kind of scary to be in that state of uncertainty.

Re:Stop Speaking in Bullshit by kmfrk on Thursday October 14, 2010 @05:46AM (#1790386)
It'd be a problem if that is the entire posting, but I consider it better to have it in the text than not. Obviously, it's not going to be enough for the posting alone.

That a lot of people say the same about thinking out of the box doesn't mean that you can't mean it - and it gives you a chance to call their bluff at the interview to make sure you don't get a job you don't want.

I agree that the posting overall is too vague on what the actual job is about - you might just as well be required to mop the floor before you punch out.

They mention the skills required, the state of the business and the kind of people they'd like to work with, but leaving out what the startup is actually about and what your role will be breaks the deal. It makes it sound like they need a code monkey.

Re:Stop Speaking in Bullshit by danilocampos on Thursday October 14, 2010 @02:59AM (#1790089)
In fairness to the original posting, there are concrete examples of what you'd be doing (as their programming generalist) that I omitted in the original draft of the post:

"Depending on the task, we program in Ruby (on Rails), Javascript (a lot of this), PHP, Python, Objective-C (iPhone), and Java (Android). Flexibility is a plus."

Updated now.

Re:Stop Speaking in Bullshit by cperciva on Thursday October 14, 2010 @03:10AM (#1790115)
That's part of the answer, but not all. Telling me what tools you need me to use helps me determine if I'm qualified or not; but it doesn't tell me what I would be doing with those tools.

I'd rather solve interesting problems in a language I hated than solve boring problems in a language I loved.

Re:Stop Speaking in Bullshit by MrIncognito on Thursday October 14, 2010 @04:11AM (#1790210)
Heh hold your horses, Colin. The tools are only there to show you that you can't live in one and ignore all others here.

And you're right, I spent a lot less time telling you what's great about the company than I did on trying to make it obvious who we're not looking for. That's because we're looking for a very specific breed of person.

In this startup, you will not only be doing engineering, but also answering customer emails and chat messages. You will likely be an important part of strategy discussions, and you may have to write the odd press release. You may even need to go door to door and figure out what our customers want. Not every engineer is interested in that stuff, and I wanted to make sure those people didn't apply.

You will basically a cofounder-level person coming in at a stage where a lot of the risk is removed.

As far as some of the interesting challenges...

Heavy image processing, data processing, and analytics. Primarily client-side web application with client side data processing. Very heavy database loads with poor potential cacheability. Data synchronization across multiple clients. Near duplicate document detection. Graph problems which need to be precomputed to varying degrees to make the application very responsive. Spam detection.

Re:Stop Speaking in Bullshit by lemming on Thursday October 14, 2010 @07:32AM (#1790536)
Sounds fantastic. Why don't you say that in the ad? The specific toolchain is the least important part of what you just described. I could care less if I'm doing those tasks in Ruby, Javascript or Java, if you want to sell it to engineers I think the actual problems are far more interesting - certainly that's what I'd want to know. While you're right that it's important your candidates understand the non-tech aspects of the role, I think you sell the tech part short.
Re:Stop Speaking in Bullshit by MrIncognito on Thursday October 14, 2010 @04:13PM (#1792401)
Yeah, I would include it if I could edit it (it doesn't appear to be editable).
Re:Stop Speaking in Bullshit by cperciva on Thursday October 14, 2010 @12:52PM (#1791587)
I agree with lemming: That comment should be in your job posting text.
Re:Stop Speaking in Bullshit by davidu on Thursday October 14, 2010 @11:18AM (#1791179)
Why aren't you saying what company it is?

What do you think you gain by keeping it secret?

Re:Stop Speaking in Bullshit by nkurz on Thursday October 14, 2010 @03:17AM (#1790134)
I think it might be a question of which double-speak speaks to you. The listing of languages is concrete in a sense, and says lots about the sort of culture they aspire to, but tells me nothing about the job. The other ads also say a lot about the culture you'd be working within.

Personally, I would care tremendously about what I am doing, and not just which tools I'd be allowed to use. The fact that you respond positively to it means that it's serving its purpose as an advertisement, but I'm not sure that means it's any more or less clear as to the job description.

So while I'd probably prefer being part of this mystery company to being a "Front-End Architect" in a cubicle, I still have no idea what the job would be and the ad doesn't offer enough specifics to make me excited in the abstract.