How much coding experience do you have? Do you know OOP? Have you worked with Selenium before, or another UI testing framework?

Why do you need this? I have some ideas if you want to improve an apparent "QA bottleneck" (hint: It's often not actually a QA / test issue).

This is a good answer that clears up a major misunderstanding about the field of QA, and I'd love to see it expanded. There are many common types of information delivered to help make better decisions, and a brief analysis of the circumstances in which to deliver each would be wonderful (especially as this skill of knowing what to deliver when is key to developing beyond a junior or mid-level QA engineer). E.g.: bugs, risk analysis, advice on quality practices tailored to that company or team, metrics, and tools to gain quality information automatically.

The same thing goes for prestige. IME, "prestige" often translates into "respect and support to do my role well". I've often had to deal with huge amounts of overhead because helping the tester do their job just wasn't a priority for the team, even with 10-to-1 dev / test ratios.

You posted your (excellent) answer while I was writing mine :-)