1. Use of cliches: Look at the CV if it contains some of the words/phrases like innovative, dynamic, motivated, extensive experience, results-oriented, proven track record, team player, fast-paced, problem solver, and entrepreneurial.
Eliminate them! We all know that everyone is a group gamer with confirmed history but only one hand strikes Get into after writing shut down immediate.
2. Overbrand yourself: too much details in the CV: No need to clarify in several webpages what you did for each and every venture. Nobody has a chance to read all that. Really! It is quite everyone wants to discuss about all his abilities and details but ignore about such a technological innovation you have used for only few several weeks or even worst: used for decades but mostly on PowerPoint.
3. Including technological innovation you do not expert well: A significant error is to add to the CV all possible IT application and components you can get in Search engines. I question very much the presence of a DBA who can provide all database producers, knows all operating-system, storage space providers and is also a programmer/developer. And here I would factor a hand to some companies who requirement too much in their job ads.
4. Writing old stuff: One of the WSJ article’s feedback says “The issue with all continues is that they focus on previous times, not on the future”. Absolutely! It is quite amusing when you see in the CV terms like Oracle 7, Oracle Similar Server and Forms/Reports. As if somebody really likes you of how well someone experts the Concept Centered Optimizer, the appropriate establishing for gc_file_to_locks or when to use the Click to Lines function instead of Anchoring.
5. Uneven DBA skills: Few years ago, there was a CV where it study “IT skills: Online Traveler and Oracle”. This is a high example but from the CV one should get the concept (for example) if the individual is Mature DBA or not. For all I have seen, a typical CV is so unbalanced that after studying it there is a worry and confused of how excellent the DBA is and what he is most powerful at. Two examples: you happen to be a SQL Adjusting professional who has never observed of SQL Information or has several decades of EM encounter but does not the distinction between Database Management and Lines Management.
6. Simulate the job ad: Déjà vu, it is so interesting when you see in the CV all you want. The most severe is when individuals are so sluggish that they even copy/paste from my job ad. These applicants will be declined.
7. Using DBA jargon: The one who flows your CV is not really with DBA qualifications. Too many abbreviations without description in supports might cause to the disappointment of the one studying it and neglecting you without cause. Even the phrase DBA should be prevented and use Database Manager instead. For many individuals outside IT the phrase DBA appears like a career from a John Knitter guide. Literally!
8. Undervaluing the achievements: In the very starting area of your CV, you want your key abilities to glow out at interviewers. Consist of on the top of the first web page what you are best at, your most essential achievements, your top abilities. One paragraph! Highest possible 5 principal points. That might be your essential factors achievements for getting to the meeting at least.
9. Picture in the CV: Do not put images unless the employer/job ad demands one. You may be assessed depending on clothing, your listen to develop, how you grin. Who knows.
10. Inadequate Sentence structure and Spelling: A very latest case: most powerful expertise was MSSSQL
All of the above relies on my encounter and I know that DBA employment is often lifestyle based. For example, in the US you cannot ask applicants about age and members of the family position. But in European countries, these matters can be at periods quite essential.