Are you a programmer? If yes, then I need to hear from you.
You heard what Dilbert has to say about the process of resume making. Now it’s time for you voice your thoughts.
According to you, what does it take to make a good developer resume? I’m not talking about the skills and experience part. Assume that you have enough skills to fill up an entire page and some experience too. My question is about how you present this data in your resume. To summarize, I need your thoughts on the below questions about a developer’s resume:
Questions for YOU!
- Do you prefer a single page resume or multi-page? If multi, then how many pages of resume you think is good enough to sell you?
- Do you elaborate on your work experience (like, job description, responsibilities, etc.) or you want to keep it short?
- Do you have more than one resume – like a master one with all details and one page resume targeted to a particular position?
- In what order you present information in the resume: Objective, Experience, Skills, Education, Summary?
- Do you really think the resume layout matters more than the content itself?
- Which font do you use for your resume? Arial? Verdana? Webdings?
- Do you prefer to maintain an online version of your resume?
This is an open thread for all. You are most welcomed to pour in your thoughts about any of the above questions. If you have any other opinion, you are welcomed to leave a comment for that also. I hope that this thread will bring some insights about the developer resumes and will help the newbies.
Related Articles (System generated)
Follow me on Twitter to get notified whenever I update this blog.
{ 9 comments }
In my opinion, you are asking all the wrong questions. What makes a good developer resume is not the form (what you are asking), but the content. If someone asked me that, I'd say: stop worrying about that stuff, and try to fill yourself with knowledge so that it doesn't matter so much. Write interesting stuff in your resume, that's it. Form doesn't matter much. It doesn't matter much to me after all.
In the past, I wrote a resume in Python. I was complemented on it by everyone despite the fact that there wasn't really anything terribly impressive on it. The thing about resumes is that they're not supposed to make the case for hiring you. They're supposed to jump out at an interviewer and say “HEY! I'M WORTH SPENDING TIME ON!”
Thus, don't worry so much about the details. Try to make your resume have one (or preferably several) “killer features”. And also make sure that your resume *isn't* really screaming “HEY! DON'T HIRE ME”.
Now, when interview time comes, *then* worry about the details.
Java, web and web design! have you any idea on how to take web surveys smartly? You could've written a survey app using those 3 right?
At least I wont like writing something more than this
Off course, i could have posted a poll instead of questions. But i
didnt want to take a survey. I wanted to hear the people thoughts in
their own words.
Aaaaha…
Creating a new Resume. Are we???
yes!
i prefer two pages of resume only, dont make it too long. the interviewer on reading long might just get bored in reading long resume.
yeah. short is sweet!
Text resumes will be around for a long time. Because everyone can type.
But everyone cannot write a story or a poem.
So, there will also be a demand for expert / professional resume – writers, for a long time to come.
But an ever-increasing number of recruiters feel that graphical / visual / audio resumes have an edge over plain text resumes – prompting emergence of job-portals such as
? http://www.VisualCV.com
which inspired me to come-up with my own
? http://www.CustomizeResume.com
( it is easy to be inspired, but , at the age of 77 , difficult to implement ! )
With regards
hemen parekh
hcp@RecruitGuru.com
Mumbai — India
Comments on this entry are closed.