Skip to main content

How important is proofreading your resume?

There are various types of mistakes that need careful proofreading of your resume before you can make the cut. Poor punctuation and gawky sentence structure hamper smooth flow stamping you as careless. So, always proofread.

While watching bloopers, you laugh at the funny slip-ups, gaffes and blunders. But certainly, you wouldn’t want a similar response when it comes to your resume, right? If your resume contains malapropisms, it’ll be a laughing stock failing to fetch any impression. So, meticulous proofreading of your resume is essential. Share it with friends and colleagues for the reassurance that inadvertent word substitution is absent. Remember, computer spell check function often doesn’t find these errors as it’s the problem of incorrect word use rather than misspelling. So, when you proofread your resume, it should reflect your editing skills, being concise and error free.

Mistakes are of various types, from typos to poor punctuation marks and gawky sentence construction that obstructs smooth flow of reading, stamping you as careless and ignorant. Be careful about:

Correct word usage and sentence constructionCorrect use of abbreviationsWord capitalizationConsistency in information and text formatting Consistency in visual designProper sequencing and links working. Here’s the checklist on what to avoid:

Misspellings: No one wants grammatical and spelling errors but many submit resumes with small, yet deadly errors, showing lack of attention to detail, writing and linguistic skills. Ask someone to proofread for you to check them. If it’s not possible, read the document aloud, word by word. While making a correction, read the whole thing over again. Never use words you aren't familiar with and consult a dictionary, when you write. Punctuation mistake: Check for periods at the end of sentences and be consistent, putting periods and commas within quotation marks. Avoid using exclamation marks. Grammatical errors: Check the use of tense in your resume. The duties you perform presently should be in present and the ones you have performed at past jobs in past tense. Capitalize proper nouns and make sure the date formatting is correct. Wrong choice of words: Look for confusing words and be careful of their usage, making use of action words.Overdose: Sometimes in your endeavor to impress, you overdo using big, unfamiliar words. Validate Facts: Check dates of prior employment as also your address and phone number. Bad design: Don’t crowd your resume allowing plenty of white space. Limit use on the number of fonts and don’t justify the lines on your resume. Egomaniacal tone: Never use grandiose statements, making yourself an absorbed narcissist.

Remember your resume is your marketing tool. So, proofread it to perfection to get the desired job.

Regards
Priyadarshan Mohanty
Software Engineer
Mindfire Solutions

Comments

Popular posts from this blog

Examples MYSQL injections

  MySQL Injection Cheat Sheet Basics. SELECT * FROM login /* foobar */ SELECT * FROM login WHERE id = 1 or 1=1 SELECT * FROM login WHERE id = 1 or 1=1 AND user LIKE "%root%" Variations. SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 SELECT * FROM login WHE/**/RE id = 1 o/**/r 1=1 A/**/ND user L/**/IKE "%root%" SHOW TABLES SELECT * FROM login WHERE id = 1 or 1=1; SHOW TABLES SELECT VERSION SELECT * FROM login WHERE id = 1 or 1=1; SELECT VERSION() SELECT host,user,db from mysql.db SELECT * FROM login WHERE id = 1 or 1=1; select host,user,db from mysql.db; Blind injection vectors. Operators SELECT 1 && 1; SELECT 1 || 1; SELECT 1 XOR 0; Evaluate all render TRUE or 1. SELECT 0.1 <= 2; SELECT 2 >= 2; SELECT ISNULL(1/0); Math SELECT FLOOR(7 + ( RAND () * 5)); SELECT ROUND(23.298, -1); Misc SELECT LENGTH(COMPRESS(REPEAT('a',1000))); SELECT MD5('abc'); Benchmark SELECT BENCHMARK(10000000,ENCODE('abc','123')); ...

Cross-Site Scripting (XSS) - The Internet is Definitely a More Dangerous Place

Phishing schemes are about to get a whole lot easier. Targeted attacks are much more likely to work now than ever before. Cookies stored on your computer can be retrieved by bad guys half a world away. Even big search engine companies like Google and Yahoo are shaking in their boots. What happened? The bad guys have discovered Cross-Site Scripting (XSS) and the Internet has sudden become a lot more dangerous. Through the magic of Cross-Site Scripting (XSS) even professional security people will have a hard time recognizing a phishing message. XSS also allows for the theft of cookies, and thus personal information and possibly passwords, stored on your computer. XSS may also have a detrimental affect on public search engine results and the trust we put in search results. This and much more is covered in this article. We've tried to boil things down so the subject is easy to understand. At the same time several examples are given showing just how bad XSS can be. Hopefully by the end...

BUG TRIAGE

Bug Triage– Severity & Priority "Triage" is a medical term. It refers to dividing wounded or sick people into three categories: those who will die no matter what you do, those who will recover even if unaided, and those who will recover only if aided. In a situation where there's too much to do, you must concentrate on the third group. Bug Triage Meetings (sometimes called Bug Councils) are project meetings in which open bugs are divided into categories. The most important distinction is between bugs that will not be fixed in this release and those that will be There are three categories for the medical usage, software also three categories - bugs to fix now, bugs to fix later, and bugs we'll never fix Triaging a bug involves: Making sure the bug has enough information for the developers and makes sense Making sure the bug is filed in the correct place Making sure the bug has sensible "Severity" and "Priority" fields Let us see wh...