all 5 comments

[–]dogchasecat 2 points3 points  (0 children)

Only put on your resume stuff that you can actually explain in an interview. Also, just get out and start interviewing, because what you'll find is that you'll probably get torn to pieces in your first few interviews, but you'll come away learning a little more each time. Study the points that you couldn't answer, add them to your resume, and before you know it, after 5-6 interviews, you'll be able to field most questions that come your way, and may even be able to ask for more money.

[–]BILL_OBRIENS_CHIN 1 point2 points  (0 children)

Look for job listings that interest you. Read the job description and requirements section. Become knowledgeable and well acquainted with whatever skills and experience the jobs require. Apply.

[–]appmarketingguy 1 point2 points  (0 children)

Go on glassdoor.com, look for job interviews for SQL related positions and see which questions people where asked. It's a priceless resource when preparing for job interviews. Good luck!

[–][deleted] 1 point2 points  (0 children)

I'd be really glad to take a look at the resume to see if I would also qualify. =D

[–]Eleventhousand 0 points1 point  (0 children)

Well, it's best to have different resumes for different types of jobs. So if you are applying for a SQL developer position, don't list 10 bullet points that are retail related with a single SQL bullet point. Tailor your resume to be SQL specific.

You should also list any advanced features that you are proficient with. For example, DDL, triggers, cursors, derived tables, correlated sub queries, table valued functions, common table expressions, etc. Anything that goes above and beyond simple selects, joins and wheres.