uffjedn
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.
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)
+ 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 [email protected] or to me personally.
Bloomberg article: http://www.bloomberg.com/news/articles/2015-07-06/trouble-se...