As someone who recently for a software developer, I've been reading websites and resumes, and let me offer my two cents, for what it's worth. I also want to me

As someone who recently for a software developer, I've been reading websites and resumes, and let me offer my two cents, for what it's worth. I also want to mention that aside from hiring for my team, I've also previously worked with paid interns from Google Summer of Code, both in the mentorship and the selection process. I'm not someone in a large company, so that made the process of hiring somewhat more open, but if someone send me your website or sent me your CV, I must admit that I don't think I would take it very seriously. There are generally three things that I look for in a candidate: 1. Is this candidate already familiar with what I need them to do, or would this be a stretch of their skills? Having the exact experience I need, with the exact tools, etc. is nice but not always necessary or the deciding factor. 2. Does this candidate have credentials that demonstrate their ability to do the job. This might be experience, a degree, of contributing to a FLOSS project in a notable way. 3. Do I think this person will be someone I want to work with? This is very "fluffy" but demonstrations of both professionalism, and also good communication are key here, as well as harder to measure things like attitude. Your resume links to a much better resume. The first resume on your website lacks anything "interesting" and if someone sent it, I'd simply pass. The frozen resume is better, but still quite challenged. Drop the huge logos; they don't impress and they feel "scammy" to me. I also think that there's some challenges with your English. For example "Backed by 10+ years of experience in the Software Industry." is off. It's not quite gramatically correct, or to be more precise, this gives off scammy vibes. :( It's not a problem in isolation to have people whose native language isn't English, if you're aiming at an English speaking audience, your resume should be better- spelling, grammar and "culture"-wise. Then in some of these jobs, describe what you did in a way that's more compelling. For example "Software Development internal to this State institution." That tells me nothing about the work. Even if it's something boring, you could say "Developed a web based application to manage employee payroll." My experience has been that when presented with a lack of detail, it equates to a lack of knowledge or participation, which is why I pass over such resumes. I agree with other posters and suggest you get some coaching in this, both in the resume and perhaps in the interview process.