Studied math a long time ago and one of my profs was proud about not going into the details. He said "Once you did something 100 times, you can go and say -as easily observable- and move on."
HN user
uffjedn
Paul Hofmann, Hiring Manager and Director of Engineering auto1.com
contact me with firstname.lastname at company
Hey,
I'm currently reading a lot about technical writing and documentation, as we're started hiring into this direction. In this context I was curious about the article from a very narrow angle when clicking the link.
I still read it all and I do think you're reaching the goal of your article as outlined in the comment, so all good.
I just wanted to make a tldr kinda disclaimer to people that might be coming from my angle and being interested in stuff like documentation best practices and alike.
This is almost not at all about writing documents, but more about how to not suck at meetings with Jeff Bezos (a manual).
There is a third one where the deadline is knowingly set too low to see how you deal with time trouble.
I designed two of those challenges. We're successfully using it for international hires for quite some time now. We hand those out after you made it through two telephone interviews, which should assure mutual interest in actually making hiring happen. We base our hiring decision on the outcome of the challenge. If you do good, we relocate you and your family, care for everything you need. Our success rate is around 30%. So I wouldn't say we ask you to work for free. We designed the challenge to be without example on github by giving extreme amounts of individual freedom in the task. Also, you're allowed to share the solution - but without mentioning the company name, so that other candidates cannot just google and find your stuff.
Not everyone has a "significant" github profile. Actually the minority of people has such a thing. So many reasons for not having one. Current employer's policy, having a family, having non-IT hobbies, etc pp. Also just having such a profile doesn't necessary proof that you can solve the company's problems, because just looking at solutions of arbitrary problems doesn't give you any information about the constraints of the problem, how you solved them and it also doesn't put your solution to this problem next to solution of the guy sitting one desk away that solved the same problem in the same amount of time under the same conditions.
(removed a stupid passive aggressive statement here, sorry folks)
auto1.com - Berlin - onsite only, visa possible Java (spring-cloud, rest), PHP (fullstack), node.js (fullstack), devops (aws, saltstack), QA (automatic, manual)
+ berlin startup spirit (didn't you always want to go to Europe? ;) + billion dollar club startup + automotive disruption, european market leader in 3 years + all kinds of roles are open, from junior/starter to engineering manager/director level
Hiring process may include coding puzzle
Send CVs to hr@auto1.com or to me personally.
Bloomberg article: http://www.bloomberg.com/news/articles/2015-07-06/trouble-se...