Judge my resume...
-
No skill stands out. At least rate them like you would rate spoken language skills. What piqued your interest? How deep did you go? Do you grok metatemplates for breakfast or do pointers frequently outsmart you? Can you read / debug / write code, pull of a project? Focus on what you did and do, not the courses you passed. Formal IT education is still varying widely, so unless I know the college in question it's nothing to rely on (it's a talk hook at best). The best asset right now are the tutorials. They show at what level you are, what you could do left alone and how you think about programming. I'd either polish or drop the "HL-DT-ST BD-RE BH20N FIX" link. From the blog post it's not immediately obvious what you did (vs. what you found), and unless I'm into PS3 stuff, I won't read the forum. The "Android game team" appears twice but is conveniently vague. Are you just two guys talking about how great it was and a few hundred lines of code, or are you half-a-dozen creatives who already put in thousands of man-hours into a shared project you love? Anything else you are good at? There are many jobs where you can benefit from domain knowledge, where a hobby like "built my own speaker" makes you stand out. I'd include that only in a specific application where it matters, unless I'm really good at it.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
Suggestions:
- Replace "Skills" with "Expertise" and pick the ones you know really well.
- Mentioning HTML and MS Office Suite is like mentioning you know how to use a mouse and keyboard. Leave them out. :)
- Expertise first, experience next, education last.
Good luck! :thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Suggestions:
- Replace "Skills" with "Expertise" and pick the ones you know really well.
- Mentioning HTML and MS Office Suite is like mentioning you know how to use a mouse and keyboard. Leave them out. :)
- Expertise first, experience next, education last.
Good luck! :thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
They were relevant to the Job I was applying for and I forgot to take them off. >.< (Job was for an Excel/Access VBA spot at a furniture company. They also wanted someone with HTML/Javascript experience.)
-
On layout first: The width is very narrow so I would widen it. Start with a sentence or two that describes either your work experience of direction. Try and avoid buzzwords. "Qualified developer with leadership skills looking to... Put work experience before education. Detail: You weren't technical writing you are a Technical Writer "Lead programmer and sole programmer". That can't be. Try Analyst Programmer. "Reverse Engineer" Bad bad bad. Try Analyst Programmer. This is a hard one, remove as many of the I's as possible. And you didn't work for free you "contributed analysis". Also you provide more information about Pre-Computer Science Transfer than you do your Major. Provide details of all the subjects you studied. This is a great place to highlight your experience To be honest I think this resume is putting you down. I strongly recommend seeking professional assistance or someone who has experience in this area. This is too important not to get right.
"You get that on the big jobs."
-
I agree, though it is usually best to not mention jobs which didn't last long. We recently got a resume from a guy who has been changing jobs every three months for over ten years. (On the other hand, I've discovered I have a hard time trusting people who haven't changed jobs at all.)
Joe Woodbury wrote:
On the other hand, I've discovered I have a hard time trusting people who haven't changed jobs at all
May I ask why? I have had the same employer for 10 years (3 as a support / Implementation, 7 as dev) so this kind of thinking would obvioulsy affect me. Cheers
Just racking up the postings
-
Not sure why the dates of your Pre-CS Transfer course are after your CS Major.
-
I would dump that generic "Objective" statement. It is so cliche, that I'd dump the resume if I saw that on my desk.
The difficult we do right away... ...the impossible takes slightly longer.
Can You Show me a Resume You would never dump If you find on your desk ? It will be helpful to Modify my Resume. :-D
-
I like it, just not so prominently. Knowing someone can document code is nice to know. How about mentioning it as part of your Lead Android Engineer "job"? That would give it some context, but not make it a primary objective.
All of us can document code. Whether we do is another matter.
-
Aside from all the great replies you received, each one from very talented programmers, I would take what you can get at first, especially in today's job market. Build up at least 5 year's experience and then look to move up in your profession, if need be. You are going to have to toughen up. I say that in a "nice" way. The real world in brutal and will eat you alive if you let it. I may seem like a jerk to you, I can be, but I don't say things to just be mean spirited. I believe that sugar coating something is more detrimental than telling it like it really is. Good luck.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) "But you probably have the smoothest scrotum of any grown man" - Pete O'Hanlon (2012) -
Others have given you good advice, so I'll just add a couple that have been missed. Check your dates - you really didn't do anything in August 208; things like this get you onto the reject pile. When you talk about the tutor having you teach a course because of how advanced you are, that just sounds arrogant. Soften it. Others have talked about the order of things, but I want to mention your timeline. As you have items that overlap, you need to make sure there's an order to them.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier
-
-
Joe Woodbury wrote:
On the other hand, I've discovered I have a hard time trusting people who haven't changed jobs at all
May I ask why? I have had the same employer for 10 years (3 as a support / Implementation, 7 as dev) so this kind of thinking would obvioulsy affect me. Cheers
Just racking up the postings
In general, I've found that engineers who've worked at only one place tend to be less flexible in looking for solutions. This is especially a problem with a long timer at their first job. Almost without exception, their code is the hardest to understand and maintain; among other things, they've adjusted to and accept the bad parts of the code. They also very much tend to underestimate how long it will take someone else to get up to speed with the code, even if pristine--they know it and the technology so well. To be clear; this is a tendency which makes we wary. On the other hand, it's rare enough that I'm struggling to remember the last time I encountered it with someone I was interviewing (for the obvious reason that such people don't change jobs!)
-
All of us can document code. Whether we do is another matter.
viaducting wrote:
All of us can document code. Whether we do is another matter.
I respectfully disagree. An astonishing number of engineers can't write, let alone write API documentation.
-
Not sure why the dates of your Pre-CS Transfer course are after your CS Major.
Decided to go to a four year university, only 2 courses transferred so I came in as a freshman. I didn't do well and flunked out. So now I'm getting a transfer degree so that I don't waste money before going back to a four year.
-
Aside from all the great replies you received, each one from very talented programmers, I would take what you can get at first, especially in today's job market. Build up at least 5 year's experience and then look to move up in your profession, if need be. You are going to have to toughen up. I say that in a "nice" way. The real world in brutal and will eat you alive if you let it. I may seem like a jerk to you, I can be, but I don't say things to just be mean spirited. I believe that sugar coating something is more detrimental than telling it like it really is. Good luck.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) "But you probably have the smoothest scrotum of any grown man" - Pete O'Hanlon (2012)In my last thread you seemed a bit jerkish but this response isn't. No worries. ^^
-
viaducting wrote:
All of us can document code. Whether we do is another matter.
I respectfully disagree. An astonishing number of engineers can't write, let alone write API documentation.
I didn't say it would be done well!
-
Engineer Analyst Roman Army 208 I helped analyze Hadrian's Wall under the direct supervision of Emperor Septimius Severus. Due to my work, we breached the wall and won victory of the Caledonians.
