I'm poking around and applying for jobs and I keep seeing the keyword Analyst. Could anyone share the job functions of this? Is it more planning and less implementation? Basically, the 'Designer' in the programming world? Or is it one of those titles that could mean several things?
I imagine being an analyst is a good way to break into the industry?
My job title is "senior developer" the guy that sits next to me is "analyst programmer". We do the exact same thing.
I wouldn't worry too much about the title. Take a look at the job description and see if the description of what the job entails aligns with what you want to do.
An analyst is typically someone who would analyze the business needs, and help translate those into software requirements.
I've held 3 different jobs titles in a little over 4 years, in order: Programmer/Analyst, Analyst/Programmer, and Systems Programmer. I've served nearly the identical job functions in all 3 positions.
Is it a good way to break into programming? No, not if they actually mean analyst (though many places take this to mean "programmer that also does design").
An actual analyst is someone who designs systems (ie, Systems Analyst) using lots of fussy tools and overcomplicated diagrams and CRCs to describe them. As a real analyst, you would do no actual programming.
However, if you can find a job as a "designing programmer" type of analyst, definitely take it.
Programmer Analyst would suggest to me that you would have a customer facing analysis task in your job. This job might require that you sit in customer meetings and gather requirements, ask questions and make suggestions that would ultimately lead to a solution that an architect might design (or possibly you, if your company doesn't have an architect). Another task you may have is documentation (ohhhhhh documentation). All of this is of course complimentary to your development tasks.
My current title is "Business Analyst" and our IT department got renamed to "Business Information System". This is all due to corporate politics in reaction to consultants wanting to outsource/reduce the IT department.
In short, as lomaxx said you need to look at the job description and ask them questions at the interview.