This reminds me of a take home software engineering interview I was once given via email. Same deal, I was told about 5 hours. I’m an iOS developer, so I was expecting a pretty simple app. I opened the PDF to find not one, but three separate tasks. Completion of all three was expected, with an estimate of about two hours each. One of the tasks was to replicate Apple’s ‘Reminders’ app in its entirety, backend sync fun…
I turned my interview task for Google into a startup
41–50 of 615 posts
Re: I turned my interview task for Google into a startup
#42Earlier quoted context omitted.
Can you illustrate that in practice? You took out the time to go to some office. You just spent an hour talking about your hobbies and attitudes and the company's working culture etc. Then, a programmer asks you to balance a red/black tree. You do.. what? You angrily throw the marker on the ground, cry insult, and run out the building? No, right? So then what? I see this repeated a lot on HN and I'm not sure I'd have…
> You took out the time to go to some office. How about a phone call or a quick email to ask what is their hiring process, what is the work and how it is usually fulfill? In the current market you are not a seller, you are the buyer. Why should I consider working for you?
Re: I turned my interview task for Google into a startup
#43When people are turning their interview questions into successful companies, maybe it is time to start asking some easier interview questions. This is a visceral demonstration of how absolutely ridiculous interviews have gotten.
And sometimes its easy to memorize such solutions. Translating a real life problem into a computer science one requires some skill.
Re: I turned my interview task for Google into a startup
#44Earlier quoted context omitted.
Can you illustrate that in practice? You took out the time to go to some office. You just spent an hour talking about your hobbies and attitudes and the company's working culture etc. Then, a programmer asks you to balance a red/black tree. You do.. what? You angrily throw the marker on the ground, cry insult, and run out the building? No, right? So then what? I see this repeated a lot on HN and I'm not sure I'd have…
> You took out the time to go to some office. How about a phone call or a quick email to ask what is their hiring process, what is the work and how it is usually fulfill? In the current market you are not a seller, you are the buyer. Why should I consider working for you?
I'm with your comment's parent: I don't think I'd have the guts to walk out of an interview either, especially for a job I applied to first.
Re: I turned my interview task for Google into a startup
#45Earlier quoted context omitted.
I would never spend 4 hours on a task after hours for a company I'm interviewing for, that is my time and I value my work life balance. It is my humble opinion that a serious interview should take max 1 hour.
If you don’t see any value in learning and trying something new, I can understand it. At the same time there are plenty of people who see it differently and accept such challenge, willing to commit much more time to this kind of task. Maybe it’s not the kind of the job you would be interested in, but then why your opinion on it would matter? One hour interview cannot be more than just screening, when split 50-50 to g…
Re: I turned my interview task for Google into a startup
#46Earlier quoted context omitted.
My policy, before finding a place I like and plan to stick around at, is no programming tasks. There's plenty of companies desperate to hire than you can be picky if you know your stuff. I also will walk out if they start up with those 'clever' programming questions that have nothing to do with the job.
I have a large-ish personal project to show and if 700+ commits of my code don't tell them enough, nothing will.
Re: I turned my interview task for Google into a startup
#47Never forget that the interview process is two way ...
Re: I turned my interview task for Google into a startup
#48https://www.wareable.com/media/images/2017/03/google-fit-app...
WTF Google?
Re: I turned my interview task for Google into a startup
#49Awesome to read about you turning this into your own startup. One thing I came to think about regarding the "4-5 hours" and throwing 5 working days on it, is that, maybe as an interviewer it is quite obvious that you put more than 4-5 hours into it and what they were "really" after were the trade-offs you would have made if you put 4-5 hours into it. Just a thought.
Re: I turned my interview task for Google into a startup
#50Earlier quoted context omitted.
>> advised that we should spend no more that 3–5 hours on the task I have to wonder if they didn't get the position because they spent more than the advised time for the task.
No one could do what they ask in 3-5 hours. At this point they are not testing your ability, they are testing your commitment.
It'd be more useful to know they could execute roughly what I'd expect in 3-5 hours. As in they think quickly, come up with something, get the basics down and are ready to progress or not.
...Of course, if they're doing it at home they could spend 3-5 days on something I'd spend 3-5 hours on and I'd never know...