←back to thread

154 points davidandgoliath | 4 comments | | HN request time: 0s | source
Show context
bityard ◴[] No.41873059[source]
Last year, I was contacted out of the blue by an Automattic recruiter who encouraged me to apply for an engineering position there. I was intrigued for a few minutes because I recognized the company and knew they did some really terrific open source work once upon a time.

But then I regained my senses... I don't have any kind of reputation or extensive proof of accomplishments or character outside of my resume and real-life social circle. Any company that would cold-contact someone like me is 100% dealing with either abnormally low offer acceptance or abnormally high employee turnover, or both. I also remember reading (on Reddit and such) from previous employees that the CEO was best described as "mercurial."

There were enough bright waving red flags that I did not bother to respond.

replies(7): >>41873238 #>>41873420 #>>41873468 #>>41873686 #>>41873749 #>>41873789 #>>41873966 #
FireBeyond ◴[] No.41873468[source]
Automattic's recruitment process is also... "involved":

> Write a thoughtful cover letter, and thorough responses to application questions.

I've seen these kind of application questions before. These are not from Automattic but comparable to what I saw from them: "Describe in detail, including the metrics, KPIs and reasoning you used when you launched your previous 0 to 1 product to ensure a good fit to your customer", "Describe in detail the biggest challenge and obstacles you've overcome getting a product to market, including both the technical aspects and business/people components, and be specific about the role you played in making sure these were surmountable" and so on.

> a Slack interview

This is actually novel and kinda cool, especially when it's one of the primary ways you might communicate day-to-day.

> 30-60 minutes Zoom interview

> Code Test for engineers - We expect the code test will take no more than a couple of days, and this is done asynchronously over the course of approximately a week

That's starting to add up.

> Trial "can last anywhere from a few hours to a few weeks. Most candidates complete the trial while working full-time and we know life is busy"

Better check your existing employment contract about moonlighting / outside employment (I am not saying I agree with such restrictions, but given how common they are, maybe this should be called out a little more....)

replies(4): >>41873624 #>>41873737 #>>41873839 #>>41874190 #
1. kuschku ◴[] No.41873839[source]
> Code Test for engineers - We expect the code test will take no more than a couple of days, and this is done asynchronously over the course of approximately a week

Doesn't that run foul of minimum wage laws and social security laws? At that point you're doing unpaid work.

replies(3): >>41874066 #>>41874080 #>>41874173 #
2. ◴[] No.41874066[source]
3. swores ◴[] No.41874080[source]
How is it legally different to sitting a one hour interview? You're not getting paid for that either, that doesn't make it a minimum wage violation because its not doing work.

I think their code test / interview process sounds terrible, but the two days of code test is part of the interview, it's not producing code for the company to use.

(I do think that any company that wants applicants to spend that much time should pay for that time, but only for ethical, not legal, reasons.)

4. bityard ◴[] No.41874173[source]
Under US labor laws at least, you only have to pay someone if they are doing work that benefits the company materially somehow. They would be forbidden from grabbing bugs out of their queue and saying, here go fix this and maybe we'll hire you. Same with unpaid internships which are _supposed_ to be training and shadowing opportunities only, no actual work being done.

That said, I did just peek and my notes and I read that candidates are paid two week's salary for the coding assignment.