posted 9/3/2010 by sqlscottgleason - Views: [36463]
How does one get started in a technical field? One thing that I see from time to time is someone who just keeps taking class after class hoping that a resume full of classes will make their resume took impressive enough that a hiring manager will take a chance on them. And that is a key phrase you DON'T want 'take a chance on me', this signifies risk. Please don't use those words during a job interview.What entry level people should do is focus on three key areas only: education, experience, and network. I and I really don't care where the experience comes from. This could be a previous job, which the entry level person may or may not have, it could be working on your laptop/home pc, or if they worked every example in a step-by-step book. Years ago, I was hired over five other interviewees because I actually took my step-by-step book with me, held it up, showed it to the hiring manager and said "I've read every page in the book and worked every example. I can do this job" Education is worth a lot, it exposes you to things you didn’t know, but it's not the whole picture. Confucius stated it very when he said something along the lines of "I hear and I forget. I see and I remember. I do and I understand." There are a lot of good Step by Step books, professional courses, and Microsoft even has a learning center. (https://www.microsoftelearning.com/ )Experience is something you can not beg, borrow, or steal. It tells the hiring manager that you have the skill set needed for the position that is open, but it’s not the whole picture either, without Education, you might have gaps in your knowledge base about the topic. Education ensures that your knowledge base is wide. And as I stated above, practice on your own laptop/spare/pc, or as the comments below state: try to volunteer your time/skill somewhere, it counts!Networking will lead you to a mentor and will also give sometimes give you hot tips such as where the open jobs are in your local area. If you’re really lucky you will understand that at some SQL User Groups, the job interview is performed during the social/networking time. Just imagine a DBA going back to their boss stating that they know someone who might be a candidate for the open position. No hiring manager wants to take chances; all they have to go on is usually a resume (which could be a bunch of lies) and a 15 to 30 minute interview. It’s reassuring to the hiring manager to have someone they know to speak on behalf for your skill set/personality. I have seen this happen.I recommend that entry level people try to find a mentor; these people exist in your local community, and can usually be found within your local users group or yearly events [SQLSaturady, http://www.sqlpass.org/ <- find the list of local SQL Chapters on this website] Talk with them about focusing on ONE of the items listed below and get an education and experience and then certified.DBA Developer (T-SQL) Exam 70-433: Microsoft SQL Server 2008, Database DevelopmentDBA Production Support Exam 70-432: Microsoft SQL Server 2008, Implementation and MaintenanceBusiness Intelligence (SSRS, SSIS, SSAS) Exam 70-448 Microsoft SQL Server 2008, Business Intelligence Development and MaintenanceThis is by no means the end all, be all of breaking into the DBA/DEV/BI field, however, you should now have a better idea of what you need to do in order to convince the hiring manager that you have the right education and experience for an entry level person. Think I missed something? Want to add your thoughts? Do you know of a great site/blog which expands on this topic, drop me a line SqlScottGleason@gmail.com or leave a comment below.:-) Scott GleasonAnd to end, I have one shameless plug; did you know Pragmatic Works offers classes in Business Intelligence?
How does one get started in a technical field?
One thing that I see from time to time is someone who just keeps taking class after class hoping that a resume full of classes will make their resume took impressive enough that a hiring manager will take a chance on them. And that is a key phrase you DON'T want 'take a chance on me', this signifies risk. Please don't use those words during a job interview.
What entry level people should do is focus on three key areas only: education, experience, and network.
I and I really don't care where the experience comes from. This could be a previous job, which the entry level person may or may not have, it could be working on your laptop/home pc, or if they worked every example in a step-by-step book. Years ago, I was hired over five other interviewees because I actually took my step-by-step book with me, held it up, showed it to the hiring manager and said "I've read every page in the book and worked every example. I can do this job"
Education is worth a lot, it exposes you to things you didn’t know, but it's not the whole picture. Confucius stated it very when he said something along the lines of "I hear and I forget. I see and I remember. I do and I understand." There are a lot of good Step by Step books, professional courses, and Microsoft even has a learning center. (https://www.microsoftelearning.com/ )
Experience is something you can not beg, borrow, or steal. It tells the hiring manager that you have the skill set needed for the position that is open, but it’s not the whole picture either, without Education, you might have gaps in your knowledge base about the topic. Education ensures that your knowledge base is wide. And as I stated above, practice on your own laptop/spare/pc, or as the comments below state: try to volunteer your time/skill somewhere, it counts!
Networking will lead you to a mentor and will also give sometimes give you hot tips such as where the open jobs are in your local area. If you’re really lucky you will understand that at some SQL User Groups, the job interview is performed during the social/networking time. Just imagine a DBA going back to their boss stating that they know someone who might be a candidate for the open position. No hiring manager wants to take chances; all they have to go on is usually a resume (which could be a bunch of lies) and a 15 to 30 minute interview. It’s reassuring to the hiring manager to have someone they know to speak on behalf for your skill set/personality. I have seen this happen.
I recommend that entry level people try to find a mentor; these people exist in your local community, and can usually be found within your local users group or yearly events [SQLSaturady, http://www.sqlpass.org/ <- find the list of local SQL Chapters on this website] Talk with them about focusing on ONE of the items listed below and get an education and experience and then certified.
DBA Developer (T-SQL) Exam 70-433: Microsoft SQL Server 2008, Database Development
DBA Production Support Exam 70-432: Microsoft SQL Server 2008, Implementation and Maintenance
Business Intelligence (SSRS, SSIS, SSAS) Exam 70-448 Microsoft SQL Server 2008, Business Intelligence Development and Maintenance
This is by no means the end all, be all of breaking into the DBA/DEV/BI field, however, you should now have a better idea of what you need to do in order to convince the hiring manager that you have the right education and experience for an entry level person.
Think I missed something? Want to add your thoughts? Do you know of a great site/blog which expands on this topic, drop me a line SqlScottGleason@gmail.com or leave a comment below.
:-) Scott Gleason
And to end, I have one shameless plug; did you know Pragmatic Works offers classes in Business Intelligence?
The best advice on the experience piece I could give is to not overlook your local non-profits. Find one you believe in & volunteer, offer to help them with IT work they need done. It can be difficult at times but, figure out where databases make sense for them and work especially hard on that aspect, you will likely be asked to help with other "technical" stuff but, thats OK too, youll build a strong broad foundation. As you volunteer, you can take pride in helping others (it feels good) & youll learn as much or more about what it takes to succeed in 6 months with a volunteer org that *needs* help than you will in years with only a book.
I think one of the biggest barriers for people to get started is the feeling that they know more than they do and that there is no need for them to have to work their way up.
I'd recommend folks not be afraid to start at the bottom of the ladder and do sucky thing like change backup tapes and use Arcserve. I think this helps to lay some groundwork and get a few fundamentals. I would also recommend anyone deciding to embark on moving into the field to also look at the MCTS Windows exams so that they get a good grasp on the OS. After all, if you want to build a solid, long lasting house you need to make sure that you have a secure foundation.
Well, since you asked for links, here is a page I have set aside that is meant to help people understand how to get a job as a DBA http://thomaslarock.com/how-to-get-a-job-as-a-dba/
I like how you broke it done to education, experience, and networking. good stuff. years ago i had someone tell me that "education is nothing without motivation. when you combine education with motivation then you really have something". the trouble is that you always need someone to take a chance on you. in fact, any time you are interviewing for a job, you are asking someone to take a chance on you. why? because they don't know you except for a resume and a brief interview.
that's where your network comes into play. if you have a strong network, then you end up finding the right opportunities. why? because people already know you, they already know what you would be best at, and when those opportunities arise your phone rings. it's really that simple.
i think the hardest part is time. it takes time to get to the point that opportunities come to you, rather than you having to go find them. it took me years to get here, but to an outsider it may seem as if i have always been so fortunate. i can show you a stack of rejection letters if you want, i've kept them all as a reminder as to where i came from. its very humbling at times.
good post Scott, see you in November. or sooner if i take a class at Pragmatic...
I remember from way back when... and I still try to follow this when digging into newer stuff... while going through a technical book, I not only do the examples that are provided... I try use the example and create another using the data in which I am currently working with. For example... most examples will use AdventureWorks, Northwind, Pubs, etc... But these databases were meant for examples like those found in technical documentation and books. So, I look at my data (let's say I am working for Procter and Gamble).. I'll look at my own data and use the example to guide me. This really drills the material into my head. Just my two cents...
This is a fantastic post for everyone and I mean everyone as you can learn something from the main post as well as the comments. Thanks for initiating this Scott