Scribd
Upload
20 views2 pages

Resume For Graduate/research Assistantship - Do's and Don'ts

The document provides guidelines for creating an effective resume for a graduate/research assistantship position. Some key recommendations include keeping the resume neat and concise, using proper grammar, listing relevant experience in a chronological order, including only the most relevant skills that are up to date, limiting technical projects to a handful, and omitting coursework and extracurricular activities from the resume. The goal is to make the resume stand out among hundreds of applicants in a few seconds by focusing on quality over quantity.

Uploaded by

fourshare
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
20 views2 pages

Resume For Graduate/research Assistantship - Do's and Don'ts

The document provides guidelines for creating an effective resume for a graduate/research assistantship position. Some key recommendations include keeping the resume neat and concise, using proper grammar, listing relevant experience in a chronological order, including only the most relevant skills that are up to date, limiting technical projects to a handful, and omitting coursework and extracurricular activities from the resume. The goal is to make the resume stand out among hundreds of applicants in a few seconds by focusing on quality over quantity.

Uploaded by

fourshare
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Resume for graduate/research assistantship Dos and Donts.

Disclaimer: The guidelines below may not be perfect. They are based on my personal experience and from witnessing several employers select and reject resumes. The job nature and the employers line of thought make or break a resume. It is entirely left to your discretion to follow my directions or to leave it as the road not taken. You know the situation: Too many students seeking Assistantship, a huge lack of funds, every Department gets flooded with resumes and people holding existing positions dont graduate. n such an unfriendly environment, how far do you fancy your chances of finding a !raduate Assistantship" t is unfair to attri#ute success to having contacts in a Department or simply luck. The truth is, a wee #it of fine$tuning to your approach can make a whole lot of difference. The first o#%ective is to make your resume get noticed. &ome of the golden rules: '. A neat resume is of course a MUST. Avoid s(uee)ing too much text into your resume. *emem#er, every employer gets at least a hundred resumes. The average time spent on any resume on the first glance would #e very meager, may#e %ust a few seconds+ ,uantity does not matter, only uality matters. -. A grammatically sound resume always helps. .ommunication skills, #oth oral and written play a #ig role in finding Assistantship. Always run a spell$check #efore you send out your resume. Do not use active voice in your resume. A (uick grammar #rush$up: /.at caught the rat0 is active1 /The rat was caught #y the cat0 is passive. 2. G.P.A: Do not convert your percentage aggregate 34.g. 5678 into a !.9.A. of 2.:;<.: for your undergraduate study. t is a good idea to not use !.9.A. if your educational system did not follow that standard. <. E perience Try to follow a chronological order, always. 4nlist any experience in we# design, computer support and administrative duties. f you have a =achelors degree in lets say, .omputer &cience and you have worked in several companies, do not list all of them. >ost employers re(uire a handyman who can do a #it of everything1 they do not need an over$(ualified engineer.

Do not forget that every rule has an exception1 it may not #e true for all %o#s. &ome %o#s might re(uire a strong technical #ackground.

6. S!i""s Try to include only the more relevant skills and the ones you really know. The more skills you have, the more you lose your credi#ility. f you mention a particular tool or language, try to mention the version you are familiar with. 34.g. ?ffice -::: instead of %ust >& ?ffice8. f you claim that you are /skilled0 in lets say, Ado#e 9hotoshop 5.:, make sure that you at least know the #asics of the software and the new features that have incorporated into the latest version. Do not mention too many programming languages1 %ust mention the ones you are most familiar with.

@. Pro#ects Do not mention too many technical pro%ects. Again, would like to stress that very few positions re(uire a strong technical #ackground. Try to restrict yourself to half a do)en pro%ects or less. 9ro%ects in Ae#;!raphic Design and data#ases are a plus. Ahen including pro%ects in .;.BB;Cava, try to mention the simpler ones like Dome Accounting system or a #oard game simulation.

5. $ourse%or! and E tra&curricu"ar acti'ities: t is in your own interest to include these sections. n my opinion, coursework is not necessary. >entioning extra$curricular activities like Eorgani)ed #lood #anks in my undergraduate study or Eparticipated in tech$symposiums held in various colleges can #e avoided. Good (uc!))

You might also like