Live data from Hacker News

The Tech Recruitment Process at Drivy

drivy.engineering

1–10 of 29 posts

Re: The Tech Recruitment Process at Drivy

#4
To start, thanks for the self-submitted promo piece on your company. If you want publicity, earn it. You ought to make a statement about this fact in the comment section. Or, submit this using an official account.

Here is basically how it goes:

- Phone screening

- Take home assignment

- "Resume” interview

- Technical interview

- Product interview

- Interview with another team

- Finalizing the hire

This might seem that there are a lot of steps… and maybe it’s true. However we feel that it’s good for both parties if they get a good look at what working together would be like.

Are you kidding me? That is more time spent interviewing with you than the legal French work week. Who has time for that? I don't know about Paris, most candidates would laugh in the face of your recruiter. Those that don't are push-overs with nothing better to do.

Put yourself in someone else's shoes and imagine going through 7 days of 1-4hr interviews, concurrently, with a half dozen other companies at the same time. What makes your company so elite? Prove it.

Some some respect.

Re: The Tech Recruitment Process at Drivy

#5
post #3

or the codebase from a previous position That was a little startling. Other than open source companies, how many employers would be happy to know their code is being shown off to potential future employers?

Presumably this company is happy for you to take their codebase and walk your next potential employer through it. Probably their competition.

Re: The Tech Recruitment Process at Drivy

#6
post #3

or the codebase from a previous position That was a little startling. Other than open source companies, how many employers would be happy to know their code is being shown off to potential future employers?

Yes, some people prefer not to share this and it is totally fine by us. It's really up to the candidate to decide in accordance to the previous company's policies.

Personally I wouldn't mind if a previous employee would like to demonstrate his/her work using the codebase - as long as they're not applying to a competing firm :) We also have a lot of people that created their own companies or interesting side projects that will present this.

Re: The Tech Recruitment Process at Drivy

#7
post #4

To start, thanks for the self-submitted promo piece on your company. If you want publicity, earn it. You ought to make a statement about this fact in the comment section. Or, submit this using an official account. Here is basically how it goes: - Phone screening - Take home assignment - "Resume” interview - Technical interview - Product interview - Interview with another team - Finalizing the hire This might seem tha…

[deleted]

Re: The Tech Recruitment Process at Drivy

#8
post #3

or the codebase from a previous position That was a little startling. Other than open source companies, how many employers would be happy to know their code is being shown off to potential future employers?

Presumably this company is happy for you to take their codebase and walk your next potential employer through it. Probably their competition.

I don't think that there much one can learn by looking at a couple of classes. On our end we let the candidate decide based on their previous company's policies.

Re: The Tech Recruitment Process at Drivy

#10
post #4

To start, thanks for the self-submitted promo piece on your company. If you want publicity, earn it. You ought to make a statement about this fact in the comment section. Or, submit this using an official account. Here is basically how it goes: - Phone screening - Take home assignment - "Resume” interview - Technical interview - Product interview - Interview with another team - Finalizing the hire This might seem tha…

If you sum it all up, it is less than a day. The phone screening is ~20 minutes, the assignment takes a couple of hours and so on.

I think it's fair to expect that a candidate is willing to invest at least 5-6 hours in an interview process. Compared to what I've seen before (full day interviews, freelance period etc) this seems fair to me. But like you comment proves, it might not be for everybody.

Post reply on HN