slateremote

finding

Portfolio projects that convert on remote tech applications

Which kinds of public projects actually move response rates on remote applications.

Portfolio projects function as filters. The ones that lift response rate share characteristics that often are not the ones candidates intuit. ## What converts Substantial deployments solving real problems, with documentation showing decision tradeoffs. Open source contributions to recognized projects. Technical writeups explaining work shipped at previous roles (within NDA limits). ## What does not convert Tutorial clones (todo apps, weather apps). Personal blog with thin content. Side projects with no users. ## Volume vs depth One substantial project (six months of work, real users) outperforms five tutorial clones consistently in screening data. ## Public visibility The benefit of a portfolio is partly that it gets read. Projects buried on GitHub with no traffic generate less signal than the same projects with even modest visibility (a few hundred GitHub stars or active users).

Sister site · slowmadly.com

Pick a basecamp for remote life.

Country guides for nomads who stay a while.

Read on slowmadly.com

Related guides