Hacker News new | past | comments | ask | show | jobs | submit login

Compare this to DuckDuckGo’s interview process.

You get 2 assignments and get paid for both.

First one - write a feature implementation proposal

Second one - they pick a feature or an issue from their open source code on Github and you have to implement it

You get paid for the whole process, the work is remote, pay is equal across locations.




> You get 2 assignments and get paid for both.

Is this supposed to be a pro or a con?

This is very hard on people who are already employed. Who wants to work 2 jobs simultaneously? The pay of a short-term contract is basically nothing compared to the pay of a full-time permanent job.

Suppose I apply to 20 places, and they all want me to do this? It doesn't scale at all.


They pay very generously for your time and have a long deadline. I’d much prefer doing that than going to 20 one day interviews with nothing to show for it at the end of the day.


> Suppose I apply to 20 places, and they all want me to do this? It doesn't scale at all.

Neither does a 1 day on-site interview process. Give me the home assignment any day. At least that’s likely to be some kind of fun.


> Neither does a 1 day on-site interview process.

That seems to be jumping the gun. You don't normally get an onsite immediately, you usually have to go through much shorter screens, the first of which may only be an hour max. So you don't necessarily waste a lot of time on any one company unless you go deep into the process, and you're probably going to be screened out early by lot of them. The take home assignments are generally supposed to be replacements for technical screens, but they invariably take a much longer amount of time.

There's also an investment differential. Every hour that a candidate has to spend in an interview is also an hour the employer has to spend in the interview. Whereas an employer can send you off with a take home project for an indefinite number of hours while they sit back and do nothing. Are they going to spend the same amount of time reviewing the project as the candidate did writing it? Extremely doubtful.


> That seems to be jumping the gun. You don't normally get an onsite immediately.

True, but in my experience I always get far enough to waste hours upon hours interviewing only to be rejected in the final round.

I’ve yet to encounter the take-home assignment where I get rejected (so far it’s a 100% success rate).


Many companies have similar project based interviews without pay. This is typically not part of the application process, but rather the last step in the interview process.


How many employees ? Pay compared to bay area salaries ?


It’s $144k/year + equity for seniors. Most of their devs are in Europe, though.


Apple gets far more applicants per job position than ddg


They are also bigger and make more money.


It's much more efficient to pre-filter candidates before they get in front of an FTE.


So they make more people loose 4 hours of their lives?


Four hours is on the low end, even for regular companies. Online assessments, phone screen, on site, various calls with hiring managers and internal recruiters, post-interview follow-ups, all combined can easily push up to 8 hours or more over a few weeks.


4 hours is a bog standard interview process. I would seriously question the standards of a company that spent significantly less than that.


Guess our standards are terribly low then. Nonetheless get some pretty great candidates.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: