News for hackers. Stuff that matters.
Re:Getting a job at Apple without going to college or doing ... by kaashif on Thursday August 17, 2023 @01:22PM (#37165135)
"Please timebox to an hour" is a bit dodgy though. If one candidate really does that, but the rest give it an extra 2 or 3 hours, that 1 hour candidate will probably be at a disadvantage.
Re:Getting a job at Apple without going to college or doing ... by neon_electro on Thursday August 17, 2023 @02:19PM (#37165883)
Thank you for mentioning this. I always find myself going further back and forth with employers who allow a take-home exercise but ask that it be time-boxed nonetheless; it's difficult to try to unpack how they're trying to communicate what kind of time pressure a role experiences, and that if I took longer than their expected time box, does that look bad just because I needed some more time to understand the problem?
Re:Getting a job at Apple without going to college or doing ... by remich on Thursday August 17, 2023 @06:36PM (#37169141)
I don't think most employers are out there looking at the timestamps on your commits to see if you really completed it within the timebox or not -- I certainly wouldn't.

I don't think that candidates who spend less time or turn in incomplete take homes are necessarily at a disadvantage. Sooo much can be discerned from a take home even if it's not finished. I can evaluate a candidate's familiarity with modern syntax, how they organize functions, how readable their code is, whether or not they used ChatGPT/CoPilot or copy/pasted from an online tutorial (surprisingly easy to discern when you're evaluating many submissions), and so on.

All of that tells me a lot about how well someone functions as an engineer, as well as what level they're operating at, and it doesn't require the completion of the take home problem.

Re:Getting a job at Apple without going to college or doing ... by neon_electro on Friday August 18, 2023 @08:53AM (#37174967)
Thanks for sharing your take. I wish I came across interviewers like yourself in the last 18 months of job searching.
Re:Getting a job at Apple without going to college or doing ... by PaulRobinson on Friday August 18, 2023 @08:46AM (#37174909)
I often ask for them to version control and send me a zip of the git repo, so I can look at commit histories. Yes, they can fake that, sure, but I can normally tell a lot about a dev from that, and actually if I see 4-5 commits over an hour perhaps with some wrong turns, that pushes the candidate up in my estimation than somebody with 1-2 commits that don't tell a story, but does show a complete solution - which is most likely what would happen if you edited history a bit.
Re:Getting a job at Apple without going to college or doing ... by kaashif on Friday August 18, 2023 @05:45PM (#37182562)
When I'm actually writing code and hashing out a solution over the course of a single hour in my job, I'm not going to commit the wrong turns.

What you're really asking for is a candidate to spend extra time inventing a convincing git history.

I really think the only way this actually works is if the problem is on a page which you can only view after you start a timer or something.

Or do it on site and watch them.

This is all high pressure but if you really want to time box, there can't be a way around it.