Hello All,

I just graduated with a Master of Science in IT.  This was a career change for me at 42.  I was a small mail order business owner for the last 8 years, a science teacher for 5 and a QC Tech for 3.  I do not come from a programming background and every Job I see on monster/career bulider wants at least 2 years experience.   I have been at this search for a month...no interviews.  This is really getting me down <:-(  

 I was told my lack of IT experience would not get in the way of being a good Systems analyst.  However, I can't help but think it is a barrier to being hired.  Am I wrong?  What do you experience people think?  I would especially like to hear from others who also tried to change careers to get into IT by getting a Masters degree.  Do you folks have any suggestions?

Hi:

Do yourself a real big favor:  First thing:  Nail down what a Systems Analyst REALLY is.    There is a ton of confusion about this.   I suggest reading Tom DeMarco's classic book on structured systems analysis.  Hopefully, you will find that systems analysis, even  for a systems analysis working on IT projects, has little to do with design or programming.  (It has alot to do about determining essential (technology independent) functionality.)   I say hopefully, because there are alot of people in the industry who will tell you something like "BA's determine business requirements, and SA's design internal system functionality".    Don't let your thinking get scrambled.  I can really drain your energy level! 

Granted we live in a disfunctional world full of job descriptions like:  Wanted: Systems Analyst.  Must have 5 years experience with C++    We have to accept such..

I also suggest looking more at job functions and less so at job tiltes.   To become a be a "real" SA, you might need a job with a BA title.   Alot of  BA  job descriptions are just as disfunctional:  Wanted BA, must have 5 yrs experience in [insert whatever technology you can think of here].  However,  from what I have seen,  BA jobs are listings are often less technical and more focused on specifiying essential functionality than SA jobs.  Frankly, many SA jobs are held by programmers who just like the SA title for ego purposes. 

Finally,  I have found that strength in interviewing can overcome alot of technical deficiencies.    This is especially important when one is doing a career transistion.  I am 54 and am currently doing business process re-engineering, with first priority given to how to best engineer complex electronics-based systems.  What do I know about electronics?   A few months ago I could only - cautiously - plug in a toaster.   Before this assingnment, I lead efforts to solve large scale web middle-tier integration problems.  What did I know about the web going into that job?   I could only, with some trial and error, log into my Yahoo e-mail account.  I did not know a WSDL from a walnut.   But the others did not know what analysis (SA or BA) really is, and I know this is the typical senario.  I really focused on the essentials and this give me the strength to interview strongly .

(Note:  I was contacted about these contract jobs through DICE.com and Monster.com)

Tony