There absolutely is a hierarchy in IT. The progression that I've seen in most places is - from bottom to top:
Tech Support I - Usually filled with people that have the least amount of computer knowledge. They can cover the basics of "is it plugged in?", read from a script, reset passwords and record trouble tickets in a support system.
Tech Support II (or above) - General troubleshooters. Can usually determine that the latest video driver you installed is the reason why the computer no longer boots. Often involved in cleaning malware / viruses from systems and generally just dealing with computer health issues.
QA - Likely a similar level of knowledge of a TS I. Good at breaking things and recording exactly what they did. Natural progression for the less technically inclined who still likes working in IT.
Business Analyst - May or may not have any in depth tech knowledge. Great communication skills. Usually comes from other areas of the company due to domain knowledge.
Project Manager - Similar to a BA in that they might have zero clue on how to operate anything beyond MS Project. Strong organization skills required. A few organizations conflate this position with Programming Manager or even Lead Programmer. However they are not the same thing. That said, corp politics is often a determining factor in where this person sits. Sometimes Development, QA and BA's report to them. Sometimes they are just there to make sure meetings go well and everyone knows what to do in more of a non-managerial role.
At this point we have two major branches Operations and Development. Some organizations place a higher priority on one branch over the other but it varies.
Dedicated Server Managers - Not a real title, more of a classification. Sharepoint admins, Exchange/Email admins, Web server admins, etc fall into this. They usually have strong skills in a very particular technology. Usually seen only in the larger organizations. Way Back When these were the lower paid people that just watched the green screens to make sure nightly batch jobs worked. Due to specialization and the plethora of complicated off the shelf products they've evolved into respectable careers.
Network Administrators - Slightly higher rating than a Dedicated Server Manager (DSM) simply because they are the work horses for keeping a company's network going while also performing the same roles as a DSM in medium to smaller organizations. They might even be utilized for TS II. The next step for a network admin is CTO / IT director.
Jr Programmers - Usually fresh out of college although there are other entry points. May end up causing as many problems as they help solve, but they exist because you have to "start somewhere" on this path.
Sr. Programmer / Lead Developer - Things become a bit murky here. Some places have enough Sr's that only one is the actual Lead. Lead is a step towards being a Programming Manager, or may even be the Programming Manager. Sometimes it's only a differentiation due to pay scale. Either way, these people ought to know exactly what they are doing with code. In environments without BA's they are often the ones who speak with the end users.
Programming Manager - Usually coordinates programmers, BA's and QA to produce a finished product. Sometimes BA/QA people report to them, sometimes not. Company politics plays a big part in their job - both in getting this position as well as the level of control they have. Next step is CTO / IT director.
IT Director / CTO / CIO - The face of IT outside of the department. Really it's just all their fault, but at least they are paid well for taking the fall.
I left out a few roles such as Network Security. These are just higher specializations in the above. That said, pay scale is often (not always) along the above lines.
The above list is an attempt to rank the jobs the OP mentioned in terms of money, power and prestige within an organization from lowest to highest. Positions in IT are NOT roughly equivalent; not by a long shot.
Rather that "prestige" is based on the level of difficulty in filling the positions which is roughly equivalent to the level of technical knowledge required. For example, even though a basic support person is usually required for any size business there are far more people "qualified" to handle that role than you'll ever find who can be a solid network admin. Because of that, saying you are in Tech Support doesn't bring along the same level of "prestige".
Now, if you look at @blankip's answer, you'll see that "Support" can be broken down and specialized much further. If a business's "product" is in providing "support" services then their job titles are going to be quite a bit different than what I've listed.