what is good to "beef up" a resume
Ummmm... How about a couple thousand posts on a high quality forum like SQLSeverCentral.com ???
Or, how about a list of major accomplishments (gotta all be true) such as "Rewrote CDR dupe check routine to go back 3 months (~120M rows) instead of just 2 months (~80M rows) and to run in just 22 hands-free minutes (hasn't failed yet) instead of 24 constant-attention hours (to sometimes fail)."
When I'm interviewing someone for the postion of SQL Developer or DBA, I don't look at sheepskins... I've too often been disappointed by people that have a Masters in CS or Mathematics that can't tell me how much 20, 23, or 1416 is. Certifications? They mean nothing to me when the person's resume says they're (and I quote) a "9 out of 10 in both Oracle and SQL Server" but can't tell me how to get the current date and time or how to get the date "with no time". Supposed experience by listing jobs? Means nothing to me because your experience may be way out of whack. Take the Java developers with "5-6 years experience" I interviewed that couldn't tell me how to keep the user from hitting the "Submit" button twice... I got stories about how you would simply roll back the first transaction, or delete the first set of rows submitted, yada-yada-yada. Disgusting...
Going a little further, comments on a resume like "was part of a team that ... " doesn't mean squat to me. What did YOU do. How did YOU make an impact for the team? What have YOU done to ensure/improve performance or maintainability of the code? What is YOUR understanding of SQL? What have YOU done to make a real difference?
A big thing with me is "Honesty"... if you inflate your resume beyond your current capabilites (nice way of saying "you lied on your resume") and happen to get hired (not by me, I will flush you out and so will lot's of other folks), then you have the arduous task of meeting expectations or maybe not making it past your first 90 days. I would much rather (and have) hire someone that I can depend on to tell me the absolute truth, all the time, even if it may be at their expense, than to hire someone supposedly a bit "better with more experience" that I think lied on their resume (doesn't happen if I have the final word). I also judge work ethic and a whole bunch of other personal traits during the interview(s) like whether the person is confident or just arrogant.
When you go to "beef up" your resume, understand the difference between "beef" and "tofu"... Don't make your interviewer walk away shaking his/her head muttering "where's the beef?" and don't make a tofu burrito out of your sheepskins... put down what you've done, quantify it, and get ready to back it up in the interview.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)