My husband is a software developer. He normally does a screening phone interview, a technical test (1-4 hours) and an in-person interview (which may involve other technical questions/tests). The whole process would take 4-8 hours.
I used to be a teacher. I normally did a job application and a teaching demonstration/interview. The whole process normally took 4-8 hours.
I can’t tell you if these processes were better or worse than EA org processes; I can only tell you that I now see 4-8 hours as a normal amount of time to spend applying and interviewing for a professional job.
When I applied to Google I did a phone interview and a full day of in-person interviews, plus a 1-hour conference call about how to do well in the second round. Lots of people devote significant time brushing up their coding interview skills as well; I only didn’t because things like Project Euler had brushed up those skills for me.
The job I took out of college included the tasks you mentioned, plus an overnight trip to the company for a series of interviews, which (if you log travel time as half of interview time) came out to something like 12 hours on top of the other tasks, or 16-20 hours total.
For an example from a different industry, the Vox Future Perfect work test was unpaid (unlike most EA work trials I’ve seen) and took me ~7 hours (I had a good amount of prior journalism experience and was familiar with the style they wanted). I don’t remember them giving any kind of guidance on how much time to spend, and I wouldn’t be surprised if other applicants spent much more.
As far as I know, this is pretty common for entry-level writing positions at publications (senior positions may rely more on reading work you’ve already done).
My husband is a software developer. He normally does a screening phone interview, a technical test (1-4 hours) and an in-person interview (which may involve other technical questions/tests). The whole process would take 4-8 hours.
I used to be a teacher. I normally did a job application and a teaching demonstration/interview. The whole process normally took 4-8 hours.
I can’t tell you if these processes were better or worse than EA org processes; I can only tell you that I now see 4-8 hours as a normal amount of time to spend applying and interviewing for a professional job.
When I applied to Google I did a phone interview and a full day of in-person interviews, plus a 1-hour conference call about how to do well in the second round. Lots of people devote significant time brushing up their coding interview skills as well; I only didn’t because things like Project Euler had brushed up those skills for me.
The job I took out of college included the tasks you mentioned, plus an overnight trip to the company for a series of interviews, which (if you log travel time as half of interview time) came out to something like 12 hours on top of the other tasks, or 16-20 hours total.
For an example from a different industry, the Vox Future Perfect work test was unpaid (unlike most EA work trials I’ve seen) and took me ~7 hours (I had a good amount of prior journalism experience and was familiar with the style they wanted). I don’t remember them giving any kind of guidance on how much time to spend, and I wouldn’t be surprised if other applicants spent much more.
As far as I know, this is pretty common for entry-level writing positions at publications (senior positions may rely more on reading work you’ve already done).