214 karma · joined March 25, 2012
https://sg.linkedin.com/in/mailshanx
Yes, the names of the engineers on the team are present in the acknowledgement section: but, this is a single line at the bottom of the post, whereas the name of the PM and the fact that he is the author is featured prominently below the title. This pattern is common across many product/OSS library announcements.
Sure, one could argue that the PM has a holistic view of the product or library being announced, and that developing this perspective is in fact their job. But surely a sufficiently senior engineer can (and often does) have an equally holistic, or perhaps even more insightful overview. At least sometimes. Even if this were not the case, why not acknowledge everyone's contributions at the same place in the article?
I think this is symptomatic of the ubiquitous class divide between the "suits" and "nerds" in the corporate world.
Open sourcing the core solution hugely dilutes your value proposition - I hope that you will reconsider your decision.
If Auto ML has commercial value, why are you open-sourcing it?
I think it would be a bad idea to open-source your solution, unless you plan on competing on services, rather than an Auto ML product.
For many good devs, immigrating to the USA is close to impossible in these times. Would be nice to know if these kinds of salaries are attainable outside the states.
Ah - thanks, its amazing how I tend to become "blind" to errors in my own writing!
Great point about the "cto" suffix! I once applied for a CTO position, and saved the tailored version of my resume at that time with a "cto" suffix. Since then I have been using modified versions of that resume, but I must get rid of the suffix now.
I held the top 1% rank in 2014. I'm not active on Kaggle anymore. They have since changed the way they calculate rankings, and you lose your rank if you don't stay active. As a result, while I still have my Kaggle profile, its now unranked. I figure its easier to explain this when asked, rather than link to a profile page that seems to contradict the claimed achievement.
>> I see a few grammatical errors, "i"
Do you mean I'm using small-letter "i" somewhere? I triple-checked, but can't seem to find that anywhere?
>> If you use google link, I would suggest doing analytics tracking to see how many times its clicked
That's a great idea!
>> The "Subnero" link is broken by the way
Thanks for catching that!
>> Make sure the PDF is OCR readable, and make sure there is an accompaning .docx format as well
I suspect its not OCR readable, and there is no .docx version either - the disadvantages of making your resume with Latex!
https://www.dropbox.com/s/n41w2zja8au26wp/shankar_resume_cto...
How high are we talking about? Let's say around ~5 yrs exp dev who would otherwise be considered intermediate level elsewhere spends the equivalent of 3-6 months of full time effort in preparation: what comp can such a candidate expect to negotiate in the big4/5?
Your solution to the anagram problem is very ingenious, indeed. I have seen this question a bunch of times and know all the "standard" approaches - but your solution, which i've never heard of before, is correct, clever and far superior. Kudos to you for coming up with it under such stressful conditions!
Your description of the interview process is very sad. The interviewers' attitudes and response induced an icky feeling in me.
I think that the attitude you encountered at Kaggle is an artifact of rather poor quality, insecure and insufficiently experienced / accomplished engineers. Whenever i interact with really accomplished and senior technical people, the conversations tend to be of stellar quality - they like to discuss actual past work in depth, are able to comprehend new and (perhaps unusual to them) concepts, and are generally a lot more respectful and pleasant. On the other hand, everything you described reeks of junior, inexperienced and rather insecure technical talent.
This reminds me of my own very-first tech interview. I had spent 5 years in a research lab, working on autonomous vehicles, writing software for things like signal processing algorithms, error correction codes, ML / reinforcement learning algorithms optimised to run on power-constrained devices and the like.
I went to interview with a VC-funded startup. They were looking for "experts in signal processing and machine learning experts". I figured my years of signal processing / ML experience might be a good fit. After the initial pleasantries, i get asked "How will you design a server that can detect anagrams of any word in the english language?"
For the life of me, i couldn't come up with a reasonable solution. I went home and hung my head in shame.