Good afternoon, all habrovchane!
And let's talk about the western bestseller, the translation of which somehow passed unnoticed.
We will talk about the book G. Lackman McDowell “Career manager of an IT project. How to get a job in a leading technology company ".

We already told about this book a year ago
habrahabr.ru/company/piter/blog/233993We were accused of incorrect name, but not in the name of the same problem?
A project is primarily a process, and a product is the result. But after all any project needs to be able to sell. Most people do not make a difference between project and product management, but in reality the difference is huge.
A year has passed, but there are still few books on product management in IT.
The product manager is responsible for ensuring that his team develops a first-class product. Some will say that a product manager (sometimes also referred to as a program manager or project manager) is a mini-product director. This statement is in a certain sense true, since the product manager has overall responsibility for the product, starting with the little things and ending with the product as a whole. The task of the product manager is to define the concept of the product and its development strategy. The product manager sets the criteria for success and makes decisions ...
')
An attractive feature of a product manager's career is that you find yourself at the intersection of technology, business and design. You play many roles and learn different points of view.
What is this book about?
About how to sell your work, but not the skills of a programmer, but the final product. For programmers, Lackmann McDowell wrote a great book, "A Programmer's Career," which continues to be in the top of the best books of Amazon, but in this book could not do without programming
Many companies, including Google, Amazon and Microsoft, are asking applicants for product manager questions about coding and algorithms. They may include both simple coding questions and more complex questions about algorithms (you may even be asked to write a code snippet).
Fortunately, usually interviewers do not require product managers with the same deep knowledge as developers. For many of them (although not all) it will be enough to get pseudocode from you.
Summary
1. Introduction ... 12
2. Responsibilities of the product manager ... 16
3. Companies ... 31
4. Acquisition of the necessary experience ... 54
5. Career development ... 72
6. Behind the scenes of the interview ... 101
7. Summary ... 112
8. Examples of a resume: before and after ... 124
9. Cover letters ... 145
10. Studying companies ... 150
11. Self-writing ... 156
12. Behavioral issues ... 171
13. Evaluation questions ... 189
14. Questions about products ... 227
15. Situational issues ... 249
16. Programming Questions ... 286
Appendix ... 344
- Ian McAllister: The Better Product Managers Are Different from Good ....................................... .................................................. ...................................... 344
- Adam Nash: Be the best product manager ......................................... ................. 346
- Sachin Rechi: A Good Product Release Roadmap ................................... 349
- Ken Norton: How to hire a product manager .......................................... ...................... 351
- Amazon's leadership principles .............................................. .......................... 358
In more detail with the book you can on a site of publishing house . The whole series "Career in the IT-industry" is here .
For Habrozhiteley 30% discount on the coupon IT-project for this book and series.