It would help to know what kind of position you are looking for. I think the style of résumé depends on the type of position. I'm assuming a software engineeri

It would help to know what kind of position you are looking for. I think the style of résumé depends on the type of position. I'm assuming a software engineering internship? In general, you have to think about the audience for your résumé. More than likely it will be a recruiter. Once it's picked out of hundreds or other résumés it will be forwarded to a hiring manager. Recruiters are probably looking for very specific criteria provided by the hiring manager. I'm not sure how effective an un-résumé is. It's a gamble, but you'll definitely stand out of the pile of other résumés. A recruiter might take a look at it and admire your creativity and give you a shot, or they will trash it because they don't want to spend time figuring it out. More than likely it will be the latter since yours leaves a lot of unanswered questions (see below). I would be more specific on your résumé in the following ways: 1. You mention over 4000 hours of development experience. What languages? When? For what companies? What did you build and what value did you bring to the table? 2. What's your GPA? Many recruiters filter by looking at GPA. What is your expected graduation date and what degree will you receive upon graduation? 3. Which independent albums? Be as specific as you can to show that you actually did work. Also, I'm not sure about including the "is looking for section." You have some very specific criteria with little leeway. A recruiter might look at this and say "Well, this kid looks bright and motivated, but we can only provide 1 out of the 4 things he's looking for" then move on to the next one. Also, the phrase "a job" might ring a wrong bell. Companies don't want to hire you for "a job" but for "a career." With that said, maybe a traditional résumé format will work better. Either that or you're going to have to redesign your résumé to quickly answer the above questions. If you're going into a technical field, I think a traditional format is better. Managers won't really care about your design skills, but they will care about your experience and your ability to solve problems. If you're going into a creative field, then this format may work. But it's still too broad. Try to be more specific.