• If you're trying to get an actual job, then there are a couple of excellent routes to take.

    Believe it or not, SQL Saturdays are one of the best places to network. Take plenty of copies of your resume with you. If you do have a blog site or a forum that you regularly participate in, make sure you include that in the resume for people to lookup.

    The Local PASS chapter is an excellent place to network, as well. Don't be afraid to talk with the Chapter President and have him include a short section at the beginning of the meeting for those that either have jobs to offer or those looking for jobs. Again, copies of your resume should always be available on the spot. Yes, they can be electronic and you can email them to folks right at the Chapter meeting if you are at a place where you can get a connection and you remembered to take your computer with you.

    Also, spend an hour to either sit down and design a simple business card with the area of SQL Server that you'd like to work with on it (as well as your contact info, of course), or spend a sawbuck or two to have someone print up a hundred.

    While some people don't care for them, I stay in constant contact with good recruiters even though I'm not currently looking for a job. Of course, I don't even talk with the bad ones anymore. You'll know who the good ones are because you should actually take the time to interview the ones you find and ask them for references. 😉 The good ones will have no problem with that at all.

    Don't be like the store that opened without hanging up a sign. Advertise yourself. Like Steve Jones says, "Develop your own branding". If you ever get to an SQL Saturday where he's teaching his "branding" session, I strongly recommend you go to it. Some of it will seem obvious but take good notes because it isn't obvious until you've heard it. 😉

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    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.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)