HackerTrans
TopNewTrendsCommentsPastAskShowJobs

throwaway082729

no profile record

comments

throwaway082729
·7 tahun yang lalu·discuss
Not sure why I understand why this is a big commitment. The first two steps (manager call and a tech interview) are already happening. I'm changing the onsite to exclude whiteboard programming and do real hands-on keyboard programming plus code reviews and presentation which are all things that an engineer is expected to do.
throwaway082729
·7 tahun yang lalu·discuss
Interviewing is broken. Whiteboard tests with a bunch of algorithm and data structures questions are meaningless and have no relevance to reality. If I ran engineering, this is what I'd have candidates do.

1. Initial video conf meeting to make sure he/she can communicate well. Talk about the role. Have a technical discussion covering candidate's past experiences to evaluate whether they really did what they claimed to have done. Discuss a technical subject that the candidate is passionate about. If satisfied, go to Step 2

2. If the candidate is a strong referral, go to Step 3. Otherwise, do a technical phone interview where the candidate solves a simple problem (more complex than FizzBuzz but not the standard algo/DS/string manipulation question)

3. Onsite Interview. Session 1 - write a simple service (todo list, twitter clone, etc) - 2 hours. 4. Session 2 - Ask the candidate to do a code review where the code in question has bugs and is poorly designed. 5. Session 3 - Candidate does a presentation of some technical topic to the team or at least a few people in the team. 6. Session 4 - Lunch 7. Session 5 - System Design exercise focusing on testing candidate's depth

Train interviewers to provide objective feedback. Calibrate scores for each question ahead of time. Interviewers should be calibrated as well. Ideally, same pool of interviewers for each question.
throwaway082729
·7 tahun yang lalu·discuss
Not really. They could sell their technology to a car company and all cars sold by that company could be self-driving enabled. Maybe we'll get true ride sharing then. I'm at home and not planning to use my car for the day. It could be used to give someone rides without me having to go drive. Waymo/Lyft could still own some cars but not all.
throwaway082729
·7 tahun yang lalu·discuss
Self-driving cars will be feasible only if LIDAR/camera costs go down to $10k/car or lower. No one is going to pay $250k for a self-driving car. At $10k/car, it's $5B for 500k cars, something that Google can easily afford.
throwaway082729
·7 tahun yang lalu·discuss
Exactly. Also, having self-driving cars does not mean that you only have self-driving cars in your fleet. They could still employ drivers strategically (in areas where demand is high which in turn will increase profitability and distribution to drivers) while using self-driving cars for commutes.
throwaway082729
·7 tahun yang lalu·discuss
Once Waymo has fully autonomous vehicles on the road, they'll look to acquire Lyft for a decent price. Lyft has the brand value and the infrastructure for ride calling (intentionally not using ride sharing) except that drivers will no longer be needed. Profits will be through the roof when that happens.