What skills should a project Manager (product)?

Hello! A month ago received a diploma IN degree in marketing and has raised the question of further employment. It so happened that during training at University I worked in the specialty. The first year was a web designer in a small Studio, then went freelance, after you learned JS, PHP and SQL (HTML and CSS knew almost from childhood) and began to provide services for the development of turnkey websites and programming. At the moment I want to apply for the position of Manager-project/product in IT, hence a number of questions.
  1. What is the difference of the first position from the second? Tasks and requirements are all about the same.
  2. What knowledge you need to have for successful employment in these specialties?
  3. How I can apply my knowledge in design and web development?
  4. Whether higher education in the profile (management or project management) or enough IN marketing?
  5. What approximate salary count at the start and how soon will be able to increase it?

Thank you in advance for your answers.
July 8th 19 at 12:20

Related questions

More answers about "What skills should a project Manager (product)?"
4 answers
July 8th 19 at 12:22
Solution
No offense, but, according to the FAQ, You still generally too early to think about such positions. Employment - it is, however, one (there may be lucky), but successful operation is quite another. And for this You have to gain and to gain experience. On:

1. The project Manager organizes the development so that with the available resources to meet the budget (money or time) and release a working and quality product. To do this, he first leads people coordinate dates, external dependencies, defines the methodology, sets out the reporting forms, but may recruit staff and to buy equipment... in short, he is responsible for everything you need in order all around, i.e. determines HOW to develop.

The product Manager is responsible for the fact that not just something they developed, but it's something to sell and, most importantly, to make a profit. Its task is to make the product competitive and in demand in the market, but to do it effectively and at the right time. To do this, it communicates with the user (studying for his needs), competitors (studying their strengths and weaknesses), monitors trends in the market and in technology, the prices, patents and trademarks, standards and regulatory laws, hang out at exhibitions, finding partners, makes and concludes a contract with them... in short, it fully defines a product strategy, i.e. WHAT needs to be developed.

Of course, both work in close contact with each other, and generally without a formal "separation of duties", you know the product is not worse (and sometimes better) of any ordinary developer and, ultimately, jointly determine the success or failure of the entire venture... for that and get either the laurels of winners and prize, or a kick in the ass. Sometimes, in small projects it can carry one person.

2. For employment - as lucky, but to work you need to have a solid knowledge and experience in all these areas, plus, ideally, a deep knowledge of the technical side of the issue... at least to know what's different interface from the abstract class ;)

3. If it's important for a product, it is VERY useful, but if not, you will have to deal with those technologies that are important.

4. The crust itself is a little who cares, but at least a General idea of the project management methods, reporting forms, document management, psychology, standards, legislation and similar things probably expected. Without it (especially if there is no portfolio), the probability that applicant didn't get a chance to learn about the existence of these wonderful things so that such summaries often dismiss already personnel officers, and to interview just case comes.

5. The funniest part question... first show in practice that they are able to earn money for the firm, and then worry over how much to ask for this skill :)
Thank you for the detailed response. Now, many things fell into place. Only not quite understand why it is early to think about this position? Why then should you begin to gain experience? It seems now there are many positions of assistants of the same MP, it will help or need any global theoretical knowledge? - Sonia.Considine commented on July 8th 19 at 12:25
: Ideally it would be good to start from the position of developer in the project, to look at this kitchen, so to speak, from the inside. In the end, rebrab is the one who determines the success or failure, others only help or hinder :) But the assistant PM is also good, if you already have at least a minimal development experience. Oh, and in parallel, of course, to read the literature on the topic. Start with the same De Marco, and further in the direction ogylnych technologies. You should at least understand the essence of waterfall, V-model, scrum/Kanban, to have an idea of the more fancy techniques like Sigma six (which You almost certainly in the next 10-15 years, and sometimes even do not have to apply, but once to read about them still stands!), on the principles of quality management, methods of risk assessment and management, on methods and principles for requirements management, know the basics of the psychology of team formation. After that 2~3 possible DIFFERENT projects as an assistant you will be thinking about the position of PMA. - Cristian.Cruickshank commented on July 8th 19 at 12:28
thanks, understood, in what direction to move. - Sonia.Considine commented on July 8th 19 at 12:31
: And yet... how to determine what is enough experience? The books can be read the theory, but the reality is much tougher. Imagine your first day of work. Most likely, the first time You, as a newcomer, nobody will give the organization of the project from scratch will give You a half-dead horse (plans, documentation, requirements, TK XS. where super busy XS. what the budget has long been exhausted, and surrender a month later) that you want to recover, Amaravati and transform into Arabian horse. And here You introduced the team, I said "yeah" and turned everyone to his own monitor. Head left, and said, tomorrow at 9 to provide at least a rough plan of action. Ask yourself right now, exactly what are You going to do in this situation, step by step, until 9 am the next day... that's when you know the exact answer to this question, it will mean that You have enough experience for the position of PMA :)
Good luck and patience! - Cristian.Cruickshank commented on July 8th 19 at 12:34
July 8th 19 at 12:24
With this experience Yes Manager?
Only in the cowboy office for pennies.
What you need experience? - Sonia.Considine commented on July 8th 19 at 12:27
:
In serious offices use CI, for example.
You know what this is? - Cristian.Cruickshank commented on July 8th 19 at 12:30
I don't intend to go in SAP or Google. Want to know what it takes to start and grow. - Sonia.Considine commented on July 8th 19 at 12:33
CI is used in offices with 10 employees.
If it is a normal office and not a cowboy.
I'm serious. - Cristian.Cruickshank commented on July 8th 19 at 12:36
July 8th 19 at 12:26
What knowledge you need to have for successful employment in these specialties?

View relevant jobs, there needs to be requirements.
Watched. Somewhere - MP - symbiosis account Manager and sales. Somewhere is a synonym of Tim-Lida, somewhere almost the assistant Director. What are the requirements to navigate? - Sonia.Considine commented on July 8th 19 at 12:29
July 8th 19 at 12:28
the Manager must be able to manage people, tasks, and risks.
well, a good Manager can easily apply for SN 200-300K in Moscow.

Find more questions by tags Project managementCareer