> Show how you acquired and use that skill in your job This can be difficult to do especially as the years of experience add up. I have 20, and can only put so

> Show how you acquired and use that skill in your job This can be difficult to do especially as the years of experience add up. I have 20, and can only put so much on 1-2 pages. I typically limit short story telling to the most recent gig. > Share your expertise on public channels such as: StackOverflow answers, open source contributions, papers, blog posts I share stints and short responsibilities for the open source work/projects I'm involves in. Again, towards a reasonably-sized resume, listing any more than that could easily bump my resume to 3+ pages. > Daily contribution to GitHub for one whole year. Terrible metric. Perhaps this wasn't well-written. Consistent contribution is more important than vanity metrics like daily contribution. And even then, it doesn't represent what someone has been up to. A month's worth of work can be squashed into a single commit that is pushed. Not to mention this can be easily faked. This reflects poorly on the person writing this as a form of measure. > Having previously joined another early startup before and stuck around. Bad signal. Startups are fickle, and many don't last more than a few years. I've joined several that shut down a year or so after I started. And I get asked about it all the time during interviews. > I’m a bit hesitant when I see candidates who change jobs too frequently, e.g. 5 different companies in 5 years. I understand that not all jobs work out, so it’s okay, sometimes necessary, to move on. However, consistent job jumping can imply that you get bored or give up easily. A year at a job is hardly enough to get deep into a problem space and make significant contributions. I don't think the author fully understands the startup ecosystem, or hasn't considered the range of nuance that exists. > We look for people who can bring a unique perspective to the table. I like this, but they don't mention critical thinking, which goes hand in hand. > 5. We care about impact, not meaningless metrics Odd assertion, since they clearly care about meaningless metrics like github contribution frequency. > If you’re applying to a small startup, say, of less than 20 people, spend some time researching who works at that startup and email them directly. Careful here. This can quickly get you blocked if you're pasting the same message to multiple people. A better practice is to choose one person and reach out, wait, and try again. But write the message organically, don't just copy and paste. > Don’t include a link to your GitHub link if it’s empty. False. Include it with context. e.g. if contributions are hidden by a private project that you've been involved in. State why it may be sparse. A long-standing github account is a good signal. Another point of concern: The word "references" appears only once, at the top. References are under utilized, and I include a line at the end of my resume that states references are available upon request. As I don't provide them by default so their contact info cannot be farmed. Based on this article, I personally wouldn't bother submitting an application to this company.