Not every engineer is product focused. I am myself am, but I understand that many engineers (including great ones) just like solving hard technical problems in a stack they like, the product itself is an afterthought.
By presupposing some ideal type of candidate and using that as a main signal, I think you're blundering and missing out on good candidates. I see that with a lot of startups that have more ego than they ought to.
>Why should I read your CV when you didn't bother skimming through my landing page, docs, or open source repository. What's the purpose of sending a CV when I have to do all the hard work?
How are you doing all the hard work, and aren't you getting paid to do that workâso what do you care? The candidates have a lot more to lose, it's much easier to skim through a CV than try to grok your homepage, repo, docs etc., and perhaps the more experienced engineers know the cost-benefit analysis of wasting their time going through arbitrary hoops after being burned many times before.
By presupposing some ideal type of candidate and using that as a main signal, I think you're blundering and missing out on good candidates. I see that with a lot of startups that have more ego than they ought to.
>Why should I read your CV when you didn't bother skimming through my landing page, docs, or open source repository. What's the purpose of sending a CV when I have to do all the hard work?
How are you doing all the hard work, and aren't you getting paid to do that workâso what do you care? The candidates have a lot more to lose, it's much easier to skim through a CV than try to grok your homepage, repo, docs etc., and perhaps the more experienced engineers know the cost-benefit analysis of wasting their time going through arbitrary hoops after being burned many times before.