←back to thread

154 points davidandgoliath | 1 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. DamnInteresting ◴[] No.41874190[source]
I've been building sites on WordPress for almost 20 years. A couple of years ago I ran into an old friend, and it turned out she worked for Automattic. She encouraged me to apply there, so I did.

The initial interviews went well, so I moved on to the code test. It was a slog; I was working full-time and raising a three-year-old. But I loved the idea of working for the keepers of WordPress, so I powered through. During this process I got a peek inside Automattic, and there were some concerning oddities. One that stuck out to me was that there is an annual week-long gathering of employees, and it is mandatory.

Then my "trial" began. It was certainly within my technical capabilities, but it was something like 2 weeks worth of full-time work, all to write code that would ultimately be thrown away. I was instructed to invoice Automattic $30/hour for the time I spent on it, and told that taking too long to finish would result in rejection. I got a few hours in before I concluded that it was just not possible, and I withdrew my application.

There was also a fair amount of weird forced corporate jargon in the materials. Instead of "employees" it was always "Automatticians," and things like that. It felt a bit cultish. In retrospect, I think I dodged a bullet.