Sometimes its real hard going talking to recruiters, you routinely get eliminated because of job description to C.V. skills match, e.g. i would get told either

Sometimes its real hard going talking to recruiters, you routinely get eliminated because of job description to C.V. skills match, e.g. i would get told either i didn't get a job or wouldn't get put forward to a job because i'm not "an Agile" or "an Node.js" despite doing JavaScript for around 8 years or so now. Sometimes the non technical recruiters are infront of some really lucrative clients who don't have a good grasp on hiring either. A technical recruiter i like is aline lerner she has a blog http://blog.alinelerner.com/posts/ http://blog.alinelerner.com/posts/ and founded interviewing.io some really good data driven insights there e.g. spelling on a C.V. matters more than what school you went too believe it or not. I also have my C.V. online and found its worked well for me using that as a portfolio http://leepenkman.appspot.com http://leepenkman.appspot.com its open source can be forked on Github/self hosted. When deciding to hire a developer, what i personally look for is passion (something that stands out e.g. personal projects, good grades, good sounding application/well researched) and a depth/breadth of experience rather than a specific industry/exact match skill set which id say you demonstrate, you didnt go to a CS uni so its good you have some things about algorithms on your blog. For depth id ask more specific questions around some of that e.g. i noticed the recursion post fairly light so id perhaps check for depth and ask more about caching, stack overflow, removing recursion with stacks/memoizing, traversals many interviewers also ask compsci questions like how to write factorial recursively/non recursively which makes the interviews skew toward formal education. for breadth id check for experiences: where/what/how/when/why (five whys) into experiences building things at a high level and what your experiences are of things relevant to this position. breadth can be very high level and you may be asked abstract things like how do you think one of googles products works or how would you trouble shoot if say a large system like that went down. Id say some advice would be to leverage your personal network, tell everyone your looking (already done here i suppose). How have you been finding clients currently? you seem to be doing well, i run a SaaS cryptocurrrency prediction system https://BitBank.nz https://BitBank.nz and basically everyone is from reddit/HN. Most jobs i've had either through knowing someone or applying, remote jobs have proved difficult even when i have done lots of open source work in and around the company without knowing anyone it seems a bit super hard, i settled on doing my own thing with BitBank.nz and contracting in person