Transitioning to Product Manager

1. Career Path of an EngineerCareer Path of an Engineer
Toufiq Mahmud Tushar
Senior Software Engineer - Augmedix
Note: This presentation focus only on Product Management

2. Project Manager
Product Manager
Development
Manager

3. Product Manager Vs Project Manager
Definition
Product — What you are providing to a group of users. It can be anything: a physical product that you hold in your hands, a software application, or a
service that you are delivering.
Project — A plan with a series of activities that has a defined outcome and a fixed start and end date. The project is completed when that outcome is
accomplished.
Role
Product manager — Often described as the CEO of their product. They set the strategy, prioritize releases, talk to customers, and clearly define features.Product manager — Often described as the CEO of their product. They set the strategy, prioritize releases, talk to customers, and clearly define features.
Their efforts are ongoing and involve managing the entire lifecycle of the product. A product manager’s goal is to deliver a product that customer
love.
Project manager — Oversee a fixed project from beginning to end. It can be a single project or a group of projects. Their job is to execute the strategy set by
the product manager or leadership team. A project manager’s goal is to work with a broader team with a diverse set of skills and to complete a
project on time and under budget.

4. Product Manager Vs Project Manager
Responsibility
Product managers own:
Strategy
Releases
Ideation
Features
Go-to-Market
Organizational training
Profit and LossProfit and Loss
Project managers own:
Budget
Delivery
Resources
Capacity
Cross-team organization
Problem resolution
Status updates

5. Product Manager Vs Development Manager
Definition
Product — What you are providing to a group of users. It can be anything: a physical product that you hold in your hands, a software application, or a
service that you are delivering.
Development manager - Defines and drives technical strategy and architectural vision for the product and sometimes the company. He is responsible for
defining the development methodology and ensuring adoption across the engineering team and organization. The engineering manager designs
appropriate solutions and recommends alternative approaches, when necessary.
Product Expert vs. Technical Expert - The product manager is the go-to product expert on the team. Where as Development manager is the technical lead
of the team.of the team.
Manage Indirectly vs. Manage Directly - The product manager is typically seen as the CEO of the product, even though no one reports directly to her. For
the product manager, this means she is responsible for making product decisions and must motivate and lead a cross-functional team of leaders from
across the organization. She is responsible for delivering an entire product experience and ensuring the company can market, sell, and support it.
The engineering manager must not only have technical chops but also directly manage a team of engineers. The engineering manager is responsible
for supporting the professional goals and development opportunities for the entire engineering staff — including providing coaching and mentoring,
one-on-one meetings and reviewing each engineer’s progress.

6. Software Architect
Definition
A software architect is a software expert who makes high-level design choices and dictates technical standards, including software coding standards, tools,
and platforms. The leading expert is referred to as the chief architect.
How to Become a Software Architect?
1. Understand and try several technological stacks – JAVA, PHP, C#, Android, iOS, Swift and many more.
2. Reading literature – Read, Read and Read.
3. Devops Knowledge – You have to know all devops related idea also.
4. Know all protocols – HTTP, TCP, UDP and select for the best case.4. Know all protocols – HTTP, TCP, UDP and select for the best case.
5. Others – Sound knowledge on UML, Design Pattern and other architectural pattern.
6. And finally always up-to-date with latest tools and technology. Because you are the one who select programming language, design system and scalable it.

7. Salary Comparison
Google:
Software engineer: $128k base, $168k total
Project manager: $117k base, $151k total
Technical project manager: $142k base, $158k total
Product manager: $150k base, $203k total
Program manager: $116k base, $161k total
Microsoft:
Software development engineer: $105k base, $118k total
Project manager: $102k base, $107k totalProject manager: $102k base, $107k total
Program manager: $106k base, $122k total
Technical program manager: $109k base, $120k total
Product manager: $116k base, $131k total
Amazon:
Software development engineer: $101k base, $124k total
Project manager: $87k base, $104k total
Technical project manager: $108k base, $145k total
Program manager: $97k base, $120k total
Technical program manager: $119k base, $132k total
Product manager: $118k base, $159k total

8. Salary Comparison
Facebook:
Software engineer: $125k base, $185k total
Project manager: $111k base, $117k total
Technical project manager: $124k base, $147k total
Program manager: $125k
Technical program manager: $150k base, $181k total
Product manager: $148k base, $257k total
Apple:
Software engineer: $122k base, $134k totalSoftware engineer: $122k base, $134k total
Project manager: $110k base, $115k total
Engineering project manager: $130k base, $157k total
Technical project manager: $133k base, $145k total
Program manager: $119k base, $155k total
Engineering program manager: $138k base, $164k total
Product manager: $131k base, $141k total

9. Look Back to Yourself 
You start out as a developer, and your job is to develop a new feature, to write a few tests and fix some bugs.
You might work with a designer. You’ll have interactions with managers of various titles such as product owners or product managers.
Ideally, you spend as little time as possible on office politics, presenting in boardrooms and creating reports. And if you love what you do, that’s probably a
really great outcome.
The question arises of how you should progress in your career. Should you stay in a technical role? Or do you want to start venturing into “management”?

10. WHAT’S Product Manager?WHAT’S Product Manager?

11. Business People
Designers Engineers

12. Business People
Designers Engineers
PM
(You one
day. Maybe)

13. WHAT’S THE PM’S SUPERPOWER?

14. Business People -
> Sell
Designers
-> Design
Engineers
-> Code
PM
-> ?

15. Superpower for Product Manager
1- Listen/Research (Customers/Market/Team/Competitors, etc.)
2- Prioritize (and justify) what to build next
3- Communicate internally what the Designers need to design and what Engineers need to code
4- Keep track of time/cost/quality4- Keep track of time/cost/quality
5- Communicate externally to Customers what was built (so they can use/buy it more)
6- Analyze impact on the business of what was built

16. HOW TO GET A PM JOB?HOW TO GET A PM JOB?

17. THE PERFECT PMTHE PERFECT PM
in the Software field

18. What you need
1. Communication/Soft Skills - Learn to explain the "why" and "what" before you talk about the "how." Great product managers understand the customers
and market first and talk tech second.
2. Technical Background – You have convince customer instant by your technical knowledge. It would be very beneficiary for engineering PM to take
decission instant based on client voice.
3. Industry Domain – Need to know current insdutry trendz and also must need an eye to look and search for future trendz.
4. Writing skills – PM is a mini CEO for product. You have to submit various docuement to stakeholder, Boss, Customers. So, need good command on ppt,
excel, word or other documentary tools.
5. Analytical Skills – Need to analysis product outcome in organization. Prioritize customer’s requirement.
6. Business Acumen – As you’re the mini CEO of product. So ROI of this product is depend on you. You have submit Business value of product to top6. Business Acumen – As you’re the mini CEO of product. So ROI of this product is depend on you. You have submit Business value of product to top
management.
7. Act Strategically or Diplomatic – Act diplomatic or Strategically to your customer.
8. Visionary thinking- As a PM, need to create products that your users love and swear by. This usually means that you start out by thinking big. There will
be a point when the project is scoped down to appropriate levels for speedy and iterative delivery. However, you need the ability to think big: to
inspire your developers and your management to get a project off the ground.

19. TECHNICAL BACKGROUNDTECHNICAL BACKGROUND

20. What’s Technical Background?
1- You DON’T need a CS Degree
2- You DON’T need to code like a pro
3- You NEED to understand the Product at every level and have the ability to have a technical conversation with your Engineering Team

21. How?
1- Build your own website or mobile app
2- Contribute to an Open-Source project
3- Finish an Online course and do all the homework assignments
4- Ask your Engineering Team to let you fix easy bugs
5- Ask your Engineering Team to give you access to run SQL queries5- Ask your Engineering Team to give you access to run SQL queries

22. INDUSTRY DOMAININDUSTRY DOMAIN

23. What’s Industry Domain?
1- You DON’T need an MBA
2- You DON’T need to sell like a pro
3- You NEED to know everything about your industry, competitors and customers in order to build something that they love (and makes you money)

24. How?
1- You can use industry-related products
2- You can study
3- You can attend to industry-related events -> meet industry-related people
4- Join LinkedIn Groups / Follow Twitter Influencers

25. COMMUNICATION SKILLSCOMMUNICATION SKILLS

26. What’s Communication Skills?
1- You DON’T need to be a Public Speaker
2- You NEED to help your team
3- You NEED to help your customer (and make money)

27. How?
1- Create a Blog (and write)
2- Participate in Events as a guest-speaker
3- Tweet

28. How should you prepare yourself?
1. Read enough so you don't feel out of your element in product management related discussions.
2. Find a role such as technical product manager, where your domain experience will be a big asset.
3. Spend time learning how the product managers in your company work.
4. Build a product in your spare time and focusing on user interaction, story acceptance, market evaluation.
5. Spend time focusing on describing the WHAT vs. the HOW in your work. It can be tough for engineers at first.
6. Volunteer to head up a small group at your company building a side-product. The Product Owner can be an engineer. This isn't out of the ordinary.

29. What Scrum Say
At Scrum there is no Development Manager and Project Manager. But the Scrum Master’s role kind of Project Manager role. But it is very high level if you
comply scrum, not any technical task have to do. As a scrum master, you are only the facilitator of the team, no super power. But Product Owner
likely Product Manager at legacy culture, is the owner of the product that the development team would work. Product owner have the right to
add/remove/control items of backlog. S/He is the CEO of the product. PO’s task to maximize the ROI and customer negotiation. S/He is the real world
hero for the organization .

30. Now choose your career path Now choose your career path 

31. References
1. https://www.quora.com/How-does-one-transition-from-an-engineering-role-to-a-product-management-role
2. https://www.sitepoint.com/developer-product-manager-3-stage-plan/
3. https://plan.io/blog/post/134848365448/from-developer-to-manager-and-back-again
4. https://www.reddit.com/r/cscareerquestions/comments/33lyz3/who_make_more_money_software_engineer_or_project/
5. https://blog.aha.io/the-product-manager-vs-project-manager/
6. https://blog.aha.io/the-product-manager-vs-the-engineering-manager/