3 ms·
The company might not have considered their request a burden (though it was -- company's mistake and author is right to be upset). Here's an example where that
by gumby 6y ago
The company might not have considered their request a burden (though it was -- company's mistake and author is right to be upset). Here's an example where that could be true:
My gf has a PhD in $FIELD. She always has to give a 'job talk' for every job (since I've known her that's been all of FAANG plus some non-early-stage startups -- so most of the gamut). The talk isn't that different from the post doc job talk or faculty job talk, except the content is a bit more industry focused. Of course this is a function of the kinds of jobs she looks for. Every time she's decided to change jobs she worked on her job talk first (as Jessime had done for her talks as well). And to have the audience be more than just the engineering side is consistent with that. So the hiring team may have just assumed this was a "job talk" position, and assumed that the candidate would already have it ready to go.
Clearly the company was quite wrong, and that lead to an unreasonable burden on the candidate. It's a good reason to avoid the company: if they can't get the first impression right, well, perhaps the first impression is actually accurate as to how everything else in the company is run.
Again, I'm not trying to defend this unknown company in the slightest, just trying to imagine how this kind of thing could happen. Sounds like Jessime dodged a bullet, job-wise.
- tidepod12 6y agoIt's really hard to tell if the company was "wrong" here based on the available information. I'm tempted to say the company is, because I certainly have personal experience with companies that do shitty things during interviews, but I'm not so sure the presentation is an automatic indicator of that. It's possible that the presentation was not meant to be a burden at all. I've done similar interview presentations in the past, and it only took me 2-3 hours to prepare for it because my job experience is in a field where giving hour-long presentations with only a day's notice is commonplace. 2-3 hours preparation is annoying, but it's about what I expect to spend preparing for any interview. If OP was interviewing for a Solutions Engineer or Consultant role, for example, then asking for a 1 hour presentation isn't that unreasonable and it's likely that the company would expect OP to be able to prepare for that without it being a burden. OTOH, if it was for a software engineer role and they were requiring a presentation even though it has nothing to do with the job function, then yea that's absurd. But which is it? I can't tell from the OP.
- gumby 6y agoI said "wrong" because it appeared that the author was not expecting a job talk. The recruiter should have prepped her for the process right up the front. Given the kind of talk she described it sounds like a big miscommunication. It's possible the miscommunication was about the role itself. In any case IMHO the responsibility lies with the company.
- anon946 6y agoGiving a talk is normal for many academic and "scientist" level positions. Being interrupted with questions is also normal, and I'm personally completely fine with it. The only annoying thing is that the company canceled at the last minute, but that's probably because they had multiple candidates "in-flight" at the same time.
- mattkrause 6y agoFrom their website, the poster also has a recent PhD (2019), so I'm a little surprised that the talk request caught them so flat-footed. I gave job talks at ~85% of my interviews after grad school, and those talks were usually adapted from my PhD defense. I did make some changes: add in more background, emphasize parts of the project that are more similar to the job, etc. However, this certainly wasn't weeks of work; more like 1-2 evenings to edit the slides, plus a few run-thrus to practice.