thanks to all...

1 - Name your resume something different than untitleddocument (1).doc.
1a - Preferably begin by writing your name in the filename. HRs get a lot of Resumes, and if all of them are named "resumes" they'll simply overwrite one another. Having your name both means the HR knows whose resume this is, and ensures it is not accidentally deleted.
2 - Your resume states experiences, but not dates. I see you've worked at a few places, but I don't get to see how long, nor what projects you've contributed to at these places.
3 - I'm surprised that your first name is just "M". Most HRs around here would want to refer to you by your first name alone, so it "could" be a problem.

4 - I would compartiment data. For example, having a header which includes ways to contact you (including a linkedin entry, phone number, etc) might be a good idea. You have your email and website portfolio up there, but I'd put more info. Some HRs/Recruiters are more familiar or prefer certain approaches (and linkedin offers a way for them to uncover references from other professionnals without asking for them: this can be a big plus, trust me!).

Otherwise, aside from reorganizing some of the info, it looks good.

Generally you use reverse chronological order.

As written you have a huge objective statement rather than a single sentence that helps HR put your paper in the right pile.

Then you have your education, which implies you are a recent grad because you didn't list your employers.

Then you list several pages of personal projects (probably too many), indicating that you are a tinkerer, but each one of those is sparse on details. The link to each one is a good thing, but the lack of details is frustrating (perhaps in a good way.)

Then you list your employers, which seems very bizarre for someone with experience; reverse chronological means professional employment is before education.

Then you list a "skills" section which is generally a useless block. Stating that you know Wordpress when you said you wrote Wordpress plugins, or stating that you know "Microsoft Visual Studio" or "Adobe Flash" doesn't help HR or employers very much, especially since you demonstrated that elsewhere.


You absolutely need some dates, at least the years, so I can figure out how much experience you actually have.

Based only on that document I have no idea to place you as a recent college student who tinkers a lot and changes interests rapidly, or to place you as a professional who worked on many tiny different projects, or to place you somewhere in between. That makes it difficult to know if you are actually a good fit for any particular job.