You’ll learn how modern products are built, how services communicate through APIs, and how to make better technical decisions without writing code. Essential skills for PMs working with complex, scalable products.
Technical Skills
for Product Managers
Hands-on course
This simulator:
Course duration: 50 hours
No prior knowledge needed
Designed by Lead PM
▪
▪
▪
▪
▪
▪
Tech PMs:
Understand APIs and services
Accurately estimate deadlines
Speak the same language as the dev team
14000+
38%
★4.8/5
alumni since 2020
come from colleagues’ recommendations
average review score
19000+
PMs in our community
trusted by:
I really enjoyed this course! In just two weeks, I gained more knowledge and confidence in my technical skills and AI prototyping abilities. What sets this course apart is its use of a simulator that guides you through real-world PM cases, allowing you to think and reason at your own pace. Coming into this course with minimal knowledge of APIs, backend logic, or vibe coding, I now feel equipped with a solid foundation to continue learning and growing in these areas.
I joined the course as a Product Designer, and it’s been a true game-changer for me. The active learning format with simulator conversations makes the experience immersive, practical, and genuinely fun. I went from having zero technical background to understanding product architecture, backend, databases, and APIs, which dramatically improved how I collaborate with developers. My AI prompting skills also improved a lot, helping me create clearer, more effective prototypes. I applied what I learned immediately at work, and the impact was noticeable. Huge thanks to Vladimir for the supportive teaching and such a valuable course.
This course has been an eye opener for me. Not only i know way more about frontend and backend now but also i've been successfully implementing it thru both technical artefact and prompting in AI prototyping. The self-paced simulator also helps me solidify the new knowledge i obtain from the course. Will come back to learn on different topic for sure!
Really solid course! It breaks down the technical side of product management in a clear, practical way. Loved the hands-on examples — super useful for connecting product strategy with engineering.
After each class, I would return to work and immediately recognize a way that I could implement the learnings from that day. This includes things like building a sequence diagram for API requirements, writing an SLA for a third party agreement, etc. Overall I'm thrilled that I signed up for this course, and that it was so easy to work in with my schedule.
Game changer! Honestly, the whole course felt like rebuilding myself as a PM from the ground up.You know that feeling when you're a self-taught PM, you have read all the books, done all the frameworks, and then you're in a meeting with your engineers and realize you are nodding along to stuff you don't fully get? That was me(( No tech lead on the team. Every technical call is mine. And I was winging half of them. This course fixed that. Not with theory, with practice - "learning by doing"! I now get how architecture works, what tradeoffs actually mean, and how to talk to my engineers like a real partner, not just the "business person" And the prototyping part? That rewired my brain. I went from writing long specs nobody reads to building working prototypes myself.
The course keeps the focus on what’s most important for PMs to understand without getting lost in unnecessary technical details.It provided a strong foundation in backend capabilities, which will help me have much more effective conversations with their technical partners. The AI prototyping with Replit was incredibly fun and practical, it taught us how to build product prototypes in a matter of hours, which is amazing!
Solid on fundamentals- the exercises are built around real-life scenarios you face as a product or program manager, and the kinds of conversations you have day-to-day. They’re hands-on and force you to think through what you’ve learned, building a strong foundation across AI-prototyping, APIs, front-end, back-end, service diagrams, and service blueprints. I can confidently visualize and apply these learnings in my current role and beyond.
This course is structured as a case study, allowing participants to learn through small projects and reflection on their work. Vlad refers to these as 'simulators,' which serve as an effective learning tool.
While many of the concepts were familiar, the formalization of tools and hands-on practice will enhance my collaboration with engineering colleagues. I highly recommend this course to product managers who feel they aren't technical enough.
While many of the concepts were familiar, the formalization of tools and hands-on practice will enhance my collaboration with engineering colleagues. I highly recommend this course to product managers who feel they aren't technical enough.
I haven't seen anything similar on the market. It is a decent course that helps to answer the main question of Project Managers or Product Managers - How deep should I dive into the tech rabbit hole to perform my job well? Now I know the depth. Thank you, ProductDo.
"I cannot recommend this course enough and I wish I had found something like that sooner! The material is explained in a comprehensive manner both during the live sessions and in a simulator. You get lots of practical tasks; the topics explained are straight to the point without unnecessary noise, and of course you are always supported by the mentor [during the session and whenever you have a question while going through the simulator]. It helped me to grasp the core topics and now I actually understand what my BE team is building and how I, as PM, can contribute in the technical conversations!"
"Really enjoyed Technical Skills for PMs by Vladimir Kalmykov. For me, it was a great mix of live sessions and simulator practice at my own pace. Materials are well structured, and the storytelling and real-live PM's cases and products kept me focused without getting overwhelmed by technical details. Even as a non-techy, I got a taste of APIs and testing — and it actually made sense!"
"There was a lot to cover, but the concepts were clear. The simulators were well thought out and not too simplistic. There is a lot of information to get through, but given the materials are available to you, it is helpful to have the time to review and reference as needed."
"What I liked:
— The simulator is excellent, the material is easily absorbed
— All tasks with an independent drawing of architecture: at first you freeze, then it becomes easier and clearer
— Different possible immersion depths: you can dive right in at any knowledge level, you can follow the links and read more
— Special thanks for the shared templates
— I definitely learned a lot of new things, especially about APIs and Security, and I want to study further
In general, during this course, my idea of what PMs do in general and how much knowledge is needed has changed. Previously, it had seemed that this was one of the most humanitarian disciplines in Tech, but on this course, I realized that it was not. Additional knowledge and understanding of how IT systems work is critical."
— The simulator is excellent, the material is easily absorbed
— All tasks with an independent drawing of architecture: at first you freeze, then it becomes easier and clearer
— Different possible immersion depths: you can dive right in at any knowledge level, you can follow the links and read more
— Special thanks for the shared templates
— I definitely learned a lot of new things, especially about APIs and Security, and I want to study further
In general, during this course, my idea of what PMs do in general and how much knowledge is needed has changed. Previously, it had seemed that this was one of the most humanitarian disciplines in Tech, but on this course, I realized that it was not. Additional knowledge and understanding of how IT systems work is critical."
"I really liked the presentation of the material: clearly, to the point, in simple language, and with practical examples. It’s lovely, you rarely see this! And the most useful thing for me was doing exercises and getting feedback. This is probably the highlight of the program — more practice, not theory:) Of the topics, I really liked metrics (SLI, SLO) and architecture, as if I dove into a level deeper. My tech lead is no longer enthusiastic about my new knowledge because I ask him difficult questions:)"
"Guys!!! This course is a bomb that destroyed my whole idea of my work and my tasks. Firstly, I realized that I can do waaaaaay more than I do now. Secondly, now I know which way to go and even what exactly needs to be done, where to start! It’s very cool! And live workshops are an incredible pleasure. After them, I had a charge of energy and creativity for two or three days :))) Vladimir, you are cool! You are all very cool!"
"Guys, it’s a very, very cool course: the presentation is cool, and I haven’t seen anything comparable in content. I’ve attended many different courses, and I gotta say, this one is the best. I liked that you give a general theory (how the api works, how top-level architecture is created), and specific tools (sequence diagram, templates for prd and complexity, I use them every day). The presentation is cool, and additional materials and articles are cool. I will miss Jane and Daniel:)"
"The course is really cool. It all starts with "I know this," "I understood this," and "I have already read it somewhere." BUT THEN I UNDERSTOOD EVERYTHING and, moreover, remembered it so that if someone wakes me up at two in the morning, I can make a 1-pager for the CEO =)) The authors managed to I-don't-even-know-how shove into my head all the info I came for. Everything is simply and clearly laid out on the shelves, and everything is repeated exactly as many times as you need to remember. Moreover, you determine the level of immersion for yourself. Simulations just rock, and the atmosphere at the workshops makes brains melt."
"The course lived up to all my expectations. At first, it was difficult, since this is really a new direction for a PM of general expertise. But over time, in the simulator, in practice, you begin to pump new skills and get excited. I pumped "neurons in the brain", as Vladimir says. There are very cool simulator cases that you can immediately practice on your product. In the process of training, I used a lot in my work and plan to continue to implement all the materials and tools I have learned into my work."
"For quite a long time I used to delegate the development of the technical side to the team 100% and thought that this did not concern me. Until, during my vacation, our production went down for an hour, and I realized that problems on the architectural side directly affect my product metrics. At "Tech for PM" I was able to clearly separate my area of responsibility and team lead’s one in my head, I understood what technical metrics are and why it is important for me to work with them."
I want to note this:
1. Practical tasks for the lecture. Very engaging, and interesting to do.
2. Learned new tools, including checklists, this is top :)
3. The simulator gave me the opportunity to think about some things from a different angle, it's cool
4. Cool lecturer! Always prompt and ready to tell more "
1. Practical tasks for the lecture. Very engaging, and interesting to do.
2. Learned new tools, including checklists, this is top :)
3. The simulator gave me the opportunity to think about some things from a different angle, it's cool
4. Cool lecturer! Always prompt and ready to tell more "
"I really liked it! The material, presentation format, simulators, department! Thanks to Vladimir for all the live lectures! And for participating in those moments that I shared with him! The course is absolutely worth the money! Advice to everyone who has gathered: watch the webinar live, actively participate and do not be afraid that someone is smarter or more experienced."
"ProductDo Tech is another way to see the complexity of PM’s work, and one that can sketch the Product Architecture, decompose it into services and APIs, know what is the key and what can be done last. "Playing in the Department" will once again show the complexity of working with the API. Each lesson is reinforced by a simulator on the topic covered. Topics of monitoring, metrics, security, and integration will all be covered and shown in 5 different cases, and one of them will be yours! My neural connections have been created, now they will work for me in my PM job."
"The course has become one of the best I’ve taken lately. First of all, I would like to note the practicality of the course, Vladimir’s ability to explain any complex topic in simple words and, again, reinforce it in practice. I will separately highlight the pool of knowledge and real skills that a PM should have in reality: what we should and should not do, how to communicate with techies, the limits of PM’s responsibility, useful tools, and much more. As a result, you get a set of skills and knowledge for the job of a PM at the level of an international company."
"A course with excellent structuring of information and examples that are affected specifically at the Middle / Senior level. I learned a lot. I recommend it to everyone who is already in product management, but wants to expand and deepen their knowledge."
Who do you think will be chosen?
Who is this simulator for?
Jr. Product/Project Managers
To effectively communicate with the team and assess the complexity of features, one should be able to understand how the system works.
PMs wishing to lead innovative projects
Those who can see the nuances are more likely to deliver a working product and thus are more likely to be hired/invited to lead it.
Product Managers who want to join IT-giants
"Experience in tech" is often mentioned in the job offerings, and for many, this is the weakest side of the product interview.
Reasons Why PMs Want to Boost Their Tech Skills
I studied the first two chapters (architecture and API) and it allowed me to get an offer for Tech PM position.
I passed the technical acumen phase for a PM interview. I was given a task to explain the end-to-end feature development process and draw an architecture diagram for it.
Before the course, I ended up unemployed, so had to pass a lot of interviews. Results of those during and after the course - heaven and earth.
Free resources
Product Manager Technical Skills Checklist
Checklist for everyday situations: architecture decisions, feature complexity estimates, API integrations — what to do and what questions to ask.
Get the checklist
Stay tuned!
Subscribe for our newsletters and get 20% off for our products.
What does the simulator look like?
How You'll Become a PM Powerhouse
Product Manager
Tech Product Manager
Can break up the product into the pieces of logic
See borders between the PM (what/why) and tech (how)
Keep systems healthy and business running
Speaks the same language as the team
Can not always estimate overall product complexity
No clear responsibility line between PM and tech
Not always able to effectively set and delegate tasks
Can turn backend systems into successful products
Not sure how to work with service metrics
Not aware that backend product is also a product
Meet the Author
Vladimir Kalmykov
Current Lead Technical PM at Booking.com, Netherlands
Only a select few can tell a PM how to use the knowledge of the technical world in business. Vladimir is one of them.
- PhD in Computer Science, Former developer
- 10+ years in product management
- One of the first Tech PMs at Booking.com
- Leads a department as a manager of PMs
- Trained 1,000+ Tech PMs on various edu-platforms
- Intro Course on Udemy: 4,500 students, rated 4.5+
Simulator Program
Throughout 10 chapters, you'll face real product situations and apply various Tech PM instruments to build a taxi startup, food delivery service, city scooter service, and even a music streaming platform from scratch.
To understand how to approach building a Taxi startup, we'll start with an important tool: the Service Blueprint. It allows you to connect user actions (Customer Journey Map steps) with frontend, backend and auxiliary processes.
What You Will Learn:
→ How to build a Service Blueprint table step by step using the example of two cases
What it Looks Like:
→ You start by examining at a real Figma app prototype
→ You help Principal PM build a Service Blueprint for a taxi passenger
→ And then for the taxi driver (a different CJM!)
→ You receive a Miro Service Blueprint template that you can use in your work
→ The lesson will take from 1 to 3 hours to complete
What Students Say About the Lesson:
→ Kristine: "Gives an excellent understanding of the basic Service Blueprint from scratch"
→ Max: "SBP is a really useful tool, I already built it for my product and surprised the CTO"
What You Will Learn:
→ How to build a Service Blueprint table step by step using the example of two cases
What it Looks Like:
→ You start by examining at a real Figma app prototype
→ You help Principal PM build a Service Blueprint for a taxi passenger
→ And then for the taxi driver (a different CJM!)
→ You receive a Miro Service Blueprint template that you can use in your work
→ The lesson will take from 1 to 3 hours to complete
What Students Say About the Lesson:
→ Kristine: "Gives an excellent understanding of the basic Service Blueprint from scratch"
→ Max: "SBP is a really useful tool, I already built it for my product and surprised the CTO"
One of the important qualities of an experienced PM is the ability to quickly figure out the complexity and main components of your product. This allows you to communicate with the team using the same language, share work, calculate the time more efficiently, and understand where risks may lie or interesting opportunities may be hiding.
What You Will Learn:
→ What the main building blocks of products are (services, integrations, databases, etc.)
→ How to build a service diagram and why a product needs it
→ What types of service architectures exist, and why is it important for scaling
What it Looks Like:
→ You help CTO to build taxi service architecture step by step
→ You get the "Architecture for PM" checklist which can be applied in your work
→ You receive additional materials on the topic
→ The lesson will take 2 to 5 hours to complete
What Students Say About the Lesson:
→ Eugene: "I began to think differently. Quite an interesting approach with a description of services like the name + what it does. I applied it at work, and it helped show several teams the areas of responsibility for each part of the project at once."
→ Anton: "It's like I've lost my technical virginity now, I'll drink coffee for that."
→ Mira: "The lesson structures knowledge well. In my product, I have an understanding of what microservices are needed, but there was no beautiful interconnected structure to draw. Now there is."
→ Ivan: "It's great that complex things are described in a very accessible way! It was useful to learn about the services within the projects and their architecture. I hadn't thought about it before because the project used a monolithic approach, but now I'll figure out what services we might need."
→ Veronika: "Finally, I have a little understanding of how I can start working on a new version of the delivery product!"
What You Will Learn:
→ What the main building blocks of products are (services, integrations, databases, etc.)
→ How to build a service diagram and why a product needs it
→ What types of service architectures exist, and why is it important for scaling
What it Looks Like:
→ You help CTO to build taxi service architecture step by step
→ You get the "Architecture for PM" checklist which can be applied in your work
→ You receive additional materials on the topic
→ The lesson will take 2 to 5 hours to complete
What Students Say About the Lesson:
→ Eugene: "I began to think differently. Quite an interesting approach with a description of services like the name + what it does. I applied it at work, and it helped show several teams the areas of responsibility for each part of the project at once."
→ Anton: "It's like I've lost my technical virginity now, I'll drink coffee for that."
→ Mira: "The lesson structures knowledge well. In my product, I have an understanding of what microservices are needed, but there was no beautiful interconnected structure to draw. Now there is."
→ Ivan: "It's great that complex things are described in a very accessible way! It was useful to learn about the services within the projects and their architecture. I hadn't thought about it before because the project used a monolithic approach, but now I'll figure out what services we might need."
→ Veronika: "Finally, I have a little understanding of how I can start working on a new version of the delivery product!"
More and more online services are emerging in the world. A modern PM builds only what is needed, integrates with ready-made APIs for everything else, and exposes the API of their service.
What You Will Learn:
→ How to describe the API of your service and understand the integration documents
→ How to call the API using the GET and POST methods
→ How to formulate the API of your product
→ How to use Sequence Diagrams in practice
What it Looks Like:
→ You test the API delivered by the team yourself
→ You help a senior PM with a Sequence Diagram
→ You help Jr.PM and SPM colleagues formulate APIs for their services
→ You receive additional materials on the topic
→ The lesson will take 2 to 5 hours to complete
What Students Say About the Lesson:
→ Ivan: "Thank you for the useful sequence diagram service, I will use it in my work. It was interesting to practice building relationships between different APIs, and in general, it became clearer how complex services work."
→ Tviga: "A very powerful lesson. Honestly, I always thought only about external integrations when it came to APIs. Now I look at everything differently. A very cool tool for creating diagrams. It's much more convenient than the other ones"
→ Polina: "Postman and SequenceDiagram, I'll put them in the treasury of tools."
→ Dmytro: "Great value, and it's clear where the line of responsibility of the PM is."
→ Ksenia: "Complicated things written in simple language."
What You Will Learn:
→ How to describe the API of your service and understand the integration documents
→ How to call the API using the GET and POST methods
→ How to formulate the API of your product
→ How to use Sequence Diagrams in practice
What it Looks Like:
→ You test the API delivered by the team yourself
→ You help a senior PM with a Sequence Diagram
→ You help Jr.PM and SPM colleagues formulate APIs for their services
→ You receive additional materials on the topic
→ The lesson will take 2 to 5 hours to complete
What Students Say About the Lesson:
→ Ivan: "Thank you for the useful sequence diagram service, I will use it in my work. It was interesting to practice building relationships between different APIs, and in general, it became clearer how complex services work."
→ Tviga: "A very powerful lesson. Honestly, I always thought only about external integrations when it came to APIs. Now I look at everything differently. A very cool tool for creating diagrams. It's much more convenient than the other ones"
→ Polina: "Postman and SequenceDiagram, I'll put them in the treasury of tools."
→ Dmytro: "Great value, and it's clear where the line of responsibility of the PM is."
→ Ksenia: "Complicated things written in simple language."
Even though what/why of the technical world is enough for a PM to do an excellent job of creating great products, sometimes it is helpful to understand a bit of the "how" of technologies to avoid being afraid of trendy names and to see beyond the line of where the territory of techies begins and how jumping for no reason is not worth it.
What You Will Learn:
→ What the frontend consists of under the hood
→ What is the difference between web and mobile development
→ What the backend consists of in addition to services
→ How to call API using Python
→ How to build an architecture of a food delivery startup
What it Looks Like:
→ You get tons of valuable information to read
→ You will help the Tech lead with a bit of code
→ The lesson will take about 30 minutes to complete
What You Will Learn:
→ What the frontend consists of under the hood
→ What is the difference between web and mobile development
→ What the backend consists of in addition to services
→ How to call API using Python
→ How to build an architecture of a food delivery startup
What it Looks Like:
→ You get tons of valuable information to read
→ You will help the Tech lead with a bit of code
→ The lesson will take about 30 minutes to complete
You already know how to determine the basic metrics (conversion, retention, etc.), but this, of course, is not all. The state of a real product is determined by a complete tree of indicators, including several technical metrics, and we will analyze them in detail.
What You Will Learn:
→ What are direct/balancing/proxy metrics
→ Why we need the main technical metrics or Service Level Indicators (SLIs)
→ What is the difference between SLI and SLO, and SLA
→ How all these form a tree of metrics
→ How to define "stable" and "fast" for a service
What it Looks Like:
→ Help the CEO deal with metrics at different levels
→ Choose the right SLIs together with your lead
→ Help Jr.PM and SPM with SLIs for their services
→ Formulate a metrics tree for a Taxi service
→ You get a checklist "Full Metric Tree" which can be used in your work
→ The lesson will take 2 to 5 hours to complete
What Students Say About This Lesson:
→ William: "I liked building the metrics tree step by step. The transition from business indicators to technical metrics is cool"
→ Diana: "The chapter about the tree of metrics is so cool. No other course has explained it so simply, but now I feel it settled in my head!"
→ Dariana: "Very important lesson, once again, to see and in practice to try the relationship between business - PM - technical metrics."
→ Maria: "Learned about SLI, started writing them for a working project."
→ Maxim: "Seeing the whole picture is a very cool skill that this lesson develops. The metrics tree is a must-have for me now."
→ Lua: "For a long time, I wanted to understand the technical metrics rating system. It was very useful but difficult. This made it easy."
What You Will Learn:
→ What are direct/balancing/proxy metrics
→ Why we need the main technical metrics or Service Level Indicators (SLIs)
→ What is the difference between SLI and SLO, and SLA
→ How all these form a tree of metrics
→ How to define "stable" and "fast" for a service
What it Looks Like:
→ Help the CEO deal with metrics at different levels
→ Choose the right SLIs together with your lead
→ Help Jr.PM and SPM with SLIs for their services
→ Formulate a metrics tree for a Taxi service
→ You get a checklist "Full Metric Tree" which can be used in your work
→ The lesson will take 2 to 5 hours to complete
What Students Say About This Lesson:
→ William: "I liked building the metrics tree step by step. The transition from business indicators to technical metrics is cool"
→ Diana: "The chapter about the tree of metrics is so cool. No other course has explained it so simply, but now I feel it settled in my head!"
→ Dariana: "Very important lesson, once again, to see and in practice to try the relationship between business - PM - technical metrics."
→ Maria: "Learned about SLI, started writing them for a working project."
→ Maxim: "Seeing the whole picture is a very cool skill that this lesson develops. The metrics tree is a must-have for me now."
→ Lua: "For a long time, I wanted to understand the technical metrics rating system. It was very useful but difficult. This made it easy."
Despite all the efforts of the development team and excellent monitoring, the reality of complex systems is that your product will break sooner or later. Let's figure out what a good PM should do.
What You Will Learn:
→ What are Service Level Objectives (SLO) and how to set them correctly
→ Why we need alerts and what they are
→ What are Service Level Agreements (SLA) and why they are needed
→ How to do post-mortem analysis
What it Looks Like:
→ Help the CEO deal with the accident
→ Formulate tests for your systems and help colleagues
→ A checklist, "Product Manager and Accidents", which can be used in work
→ You receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete.
What Students Say About This Lesson:
→ Dmytro: "Previously, the team only talked about SLA. Now it has become clear how to determine them and that we should start not with SLA but with SLI. Very timely - I will apply it in my work And one more thing - now it’s clear what to ask from whom :) "
→ Leo: "All good, already used some smart phrases when talking to the dev team lead :)"
→ Annette: "Alerts!!! We don't have them, and we read the support chat; when we went down for an hour, it hurt."
What You Will Learn:
→ What are Service Level Objectives (SLO) and how to set them correctly
→ Why we need alerts and what they are
→ What are Service Level Agreements (SLA) and why they are needed
→ How to do post-mortem analysis
What it Looks Like:
→ Help the CEO deal with the accident
→ Formulate tests for your systems and help colleagues
→ A checklist, "Product Manager and Accidents", which can be used in work
→ You receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete.
What Students Say About This Lesson:
→ Dmytro: "Previously, the team only talked about SLA. Now it has become clear how to determine them and that we should start not with SLA but with SLI. Very timely - I will apply it in my work And one more thing - now it’s clear what to ask from whom :) "
→ Leo: "All good, already used some smart phrases when talking to the dev team lead :)"
→ Annette: "Alerts!!! We don't have them, and we read the support chat; when we went down for an hour, it hurt."
How to reduce the "pain" of a crash for your product? Automated functional and non-functional testing will help us with this. We will figure out what the PM should know about them.
What You Will Learn:
→ Why do functional testing
→ How a PM should formulate the correct test for a dev story
→ How to define test coverage
→ Why do non-functional testing
What it Looks Like:
→ Formulate tests for taxi systems and help colleagues
→ Define the approach to non-functional testing
→ Offer tests for the delivery service
→ Receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete
What You Will Learn:
→ Why do functional testing
→ How a PM should formulate the correct test for a dev story
→ How to define test coverage
→ Why do non-functional testing
What it Looks Like:
→ Formulate tests for taxi systems and help colleagues
→ Define the approach to non-functional testing
→ Offer tests for the delivery service
→ Receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete
With the growth of the product and its customer base, the amount of confidential information about users, which is better not to lose, also grows. Moreover, when the service starts to pass large amounts of money through itself, there are many fraudulent attempts to redirect this flow. Let's see what the PM should do about it.
What You Will Learn:
→ How to protect the public APIs of your services
→ What is personal/PII data, what the GDPR requires, and how to protect it
→ What types of fraud exist
What it Looks Like:
→ Help the CEO deal with the security of user data
→ Understand PII and regulations for the Taxi service
→ Propose a strategy to protect the API and fight against fraudsters
→ Help the CEO with security for the delivery service
→ You receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete
What Students Say About This Lesson:
→ Alexander: "It was necessary to plunge into the hitherto unknown sphere of the regulations (GPDR, PCI DSS) and immediately figure out what difficulties this creates for the business and what it will cost. A very pleasant practice."
→ Yarko: "Learned a lot about the GDPR and other regulations. It was interesting. As for the methods to defend from DDos, I'll add it to the list to read more."
What You Will Learn:
→ How to protect the public APIs of your services
→ What is personal/PII data, what the GDPR requires, and how to protect it
→ What types of fraud exist
What it Looks Like:
→ Help the CEO deal with the security of user data
→ Understand PII and regulations for the Taxi service
→ Propose a strategy to protect the API and fight against fraudsters
→ Help the CEO with security for the delivery service
→ You receive additional materials on the topic
→ The lesson will take 1 to 3 hours to complete
What Students Say About This Lesson:
→ Alexander: "It was necessary to plunge into the hitherto unknown sphere of the regulations (GPDR, PCI DSS) and immediately figure out what difficulties this creates for the business and what it will cost. A very pleasant practice."
→ Yarko: "Learned a lot about the GDPR and other regulations. It was interesting. As for the methods to defend from DDos, I'll add it to the list to read more."
Now we understand what the product consists of, how to measure its condition, and where the problems are most likely to come from. In the final lesson, we will combine the knowledge gained to turn several projects/services/features into a series of structured documents with an assessment of complexity.
What You Will Learn:
→ What parameters make up the overall complexity of the product
→ How to apply this pattern to projects (whole companies/startups), services (team level), and features (sprint level)
→ 4 new cases to consolidate knowledge
What it Looks Like:
→ Help the CEO decide to launch a new "internal" startup: urban scooters
→ Help the team evaluate the complexity of the service within the company and the features within the service
→ For each case, you build architecture and apply the Full Product Review Template
→ You receive a "Full Product Review" checklist
→ The lesson will take 3 to 6 hours to complete
What Students Say About This Lesson:
→ Eugenii: "Connecting ideas in an architectural diagram is cool. It gives the idea some stability or something. Well, the assessment of complexity is generally priceless."
→ Vladimir: "Now I know what is more important when evaluating the technical complexity of a product, and most importantly, I know where to dig further and what to do to improve my competence."
→ Daria: "What a cool template! I will use it in my work!!!"
What You Will Learn:
→ What parameters make up the overall complexity of the product
→ How to apply this pattern to projects (whole companies/startups), services (team level), and features (sprint level)
→ 4 new cases to consolidate knowledge
What it Looks Like:
→ Help the CEO decide to launch a new "internal" startup: urban scooters
→ Help the team evaluate the complexity of the service within the company and the features within the service
→ For each case, you build architecture and apply the Full Product Review Template
→ You receive a "Full Product Review" checklist
→ The lesson will take 3 to 6 hours to complete
What Students Say About This Lesson:
→ Eugenii: "Connecting ideas in an architectural diagram is cool. It gives the idea some stability or something. Well, the assessment of complexity is generally priceless."
→ Vladimir: "Now I know what is more important when evaluating the technical complexity of a product, and most importantly, I know where to dig further and what to do to improve my competence."
→ Daria: "What a cool template! I will use it in my work!!!"
The CEO has a new idea, so it's time to apply what we've learned to another use case.
What it Looks Like:
→ Once again, you will practice building architecture, metrics tree, complexity estimation
→ You'll think about the future of the project and suggest ways for the development of architecture
→ The lesson will take from 3 to 6 hours
What Students Say About This Lesson:
→ Nina: "The combination of architecture + complexity is great, it helps to consolidate knowledge and feel confident."
→ Dmytro: "Cool case!"
→ Antony: "Will there be a new season? :)"
What it Looks Like:
→ Once again, you will practice building architecture, metrics tree, complexity estimation
→ You'll think about the future of the project and suggest ways for the development of architecture
→ The lesson will take from 3 to 6 hours
What Students Say About This Lesson:
→ Nina: "The combination of architecture + complexity is great, it helps to consolidate knowledge and feel confident."
→ Dmytro: "Cool case!"
→ Antony: "Will there be a new season? :)"
Pricing
Self-Paced
Choose this option if you want to start hands-on learning immediately and practice on your own. 80% students prefer this.
850 €
— €
• Start learning immediately
• 200+ practical challenges
• 5 real industry use cases
Pay via Stripe • 200+ practical challenges
• 5 real industry use cases
• PM checklists to use at work
• Digital certificate
• Unlimited access
Cohort-Based
Choose this option if you want to combine hands-on practice with group workshops led by the author and solve 5 additional use cases.
Live cohort 17 Apr - 12 May on two related simulators: Technology Foundations + AI Prototyping for Product Managers
Live cohort 17 Apr - 12 May on two related simulators: Technology Foundations + AI Prototyping for Product Managers
• Start learning immediately
• 200+ practical challenges on Technology
• 50+ practical challenges on AI Prototyping
• 5 + 2 real industry use cases
+ Private community of peers
+ Direct access to instructor
+ Guided feedback & reflection
Learn more • 200+ practical challenges on Technology
• 50+ practical challenges on AI Prototyping
• 5 + 2 real industry use cases
• PM checklists to use at work
• Digital certificate
• Unlimited access
+ 4 interactive live sessions+ Private community of peers
+ Direct access to instructor
+ Guided feedback & reflection
Self-Paced
Choose this option if you want to start hands-on learning immediately and practice on your own. 80% students prefer this.
884 $
— $
• Start learning immediately
• 200+ practical challenges
• 5 real industry use cases
Pay via Stripe • 200+ practical challenges
• 5 real industry use cases
• PM checklists to use at work
• Digital certificate
• Unlimited access
Cohort-Based
Choose this option if you want to combine hands-on practice with group workshops led by the author and solve 5 additional use cases.
Live cohort 17 Apr - 12 May on two related simulators: Technology Foundations + AI Prototyping for Product Managers
Live cohort 17 Apr - 12 May on two related simulators: Technology Foundations + AI Prototyping for Product Managers
• Start learning immediately
• 200+ practical challenges on Technology
• 50+ practical challenges on AI Prototyping
• 5 + 2 real industry use cases
+ Private community of peers
+ Direct access to instructor
+ Guided feedback & reflection
Learn more • 200+ practical challenges on Technology
• 50+ practical challenges on AI Prototyping
• 5 + 2 real industry use cases
• PM checklists to use at work
• Digital certificate
• Unlimited access
+ 4 interactive live sessions+ Private community of peers
+ Direct access to instructor
+ Guided feedback & reflection
Get in touch
Please connect with our team and briefly describe your needs.
Want to increase your discount up to 30%?
Create your own bundle and unlock discounts! The more you add, the more you save:
2 courses → 10% off
3 courses → 15% off
4 courses → 20% off
5 or more → 30% off
2 courses → 10% off
3 courses → 15% off
4 courses → 20% off
5 or more → 30% off
Choose your payment method:
Once you complete the simulator, you will receive an electronic certificate to add to your LinkedIn profile.
Our Students Work at
Still not sure?
Check out a free workshop on Tech 101s from Vladimir
Frequently Asked Questions
Highlight business impact: Explain how AI-prototyping knowledge will help you build smarter products that solve real customer problems and drive growth.
Emphasize upskilling ROI: Show that investing in your skills now means faster delivery, better decisions, and fewer costly mistakes down the road.
Connect to company goals: Align the course benefits with your company’s strategy, whether it’s innovation, efficiency, or entering new markets.
Stress team advantage: Point out how your new AI-prototyping skills will uplift your whole team’s expertise and collaboration.
Assure minimal downtime: Reassure your employer the course is hands-on, flexible, and won’t disrupt your current workload.
Simplify payment: Let them know we can issue an invoice if needed, making the process easy for company reimbursement.
Contact Sales
Emphasize upskilling ROI: Show that investing in your skills now means faster delivery, better decisions, and fewer costly mistakes down the road.
Connect to company goals: Align the course benefits with your company’s strategy, whether it’s innovation, efficiency, or entering new markets.
Stress team advantage: Point out how your new AI-prototyping skills will uplift your whole team’s expertise and collaboration.
Assure minimal downtime: Reassure your employer the course is hands-on, flexible, and won’t disrupt your current workload.
Simplify payment: Let them know we can issue an invoice if needed, making the process easy for company reimbursement.
Contact Sales
Yes, the course is designed for Product and Project Managers who understand nothing about tech. We will talk about the basic concepts that a Product Manager needs in practice to manage a team and build a successful product.
Read the reviews: we had a lot of guys with no experience who are already using their knowledge to the fullest in their projects.
Read the reviews: we had a lot of guys with no experience who are already using their knowledge to the fullest in their projects.
10 years ago, technical knowledge was needed only by programmers and tech leads. 5 years ago, they became necessary for the PM. Today we observe that any IT specialist (Product Manager, Project Manager, Analyst, Marketing Manager, even Sales) is valued higher if they understand what is hidden behind the screen of the “website”, because this allows them to ask more substantive questions, estimate deadlines and, well, be more respected by techies.
In the simulation story, the main character is the product leader of the team. At the same time, the technical topics and cases presented fully apply to any modern IT role.
In the simulation story, the main character is the product leader of the team. At the same time, the technical topics and cases presented fully apply to any modern IT role.
In this course, we talk about a very specific area of knowledge, "Tech for PM". On their own, without a base, technologies will not make you a super-specialist, but at the same time, the gained piece of knowledge will always stay with you. It's like building a powerful engine for a car that doesn't have wheels. There's nothing to drive on yet, but at the same time, the engine is waiting for its moment.
Thus, we advise total newbies to take this course together with other special courses. There are a lot of basic materials, and they are relatively simple, and a specialist who works at the necessary (complex) disciplines will grow much faster than others because they will be immediately immersed in real and not simplified tasks.
Thus, we advise total newbies to take this course together with other special courses. There are a lot of basic materials, and they are relatively simple, and a specialist who works at the necessary (complex) disciplines will grow much faster than others because they will be immediately immersed in real and not simplified tasks.
If you practice for 30 to 60 minutes a day, then it will take about 10-15 days. But rest assured you’ll be too busy having fun as you take your time to analyze and creatively solve the problems in the simulator.
Cases are indeed real and demonstrate a diversity of products out there in industry - not everything is a "website" or a "shop". In the "Tech for PM" simulator, we cover an Uber-like taxi app, Spotify-like music streaming service, a food delivery app, and more. In the "A/B testing" simulator, we dive into "Meditation app" services and in "Product Discovery", we de-assemble a cloth rental business.
The more cases you practice, the more experienced a Product Manager you become.
The more cases you practice, the more experienced a Product Manager you become.
No, the simulator and additional materials will be available to you forever, so go at your own pace. Please note that, as in life, you cannot go back and "live" the task again: all your progress will be preserved in its original form.
We help by giving you a bunch of practical tasks and sharing our mistakes and experiences. We have already built so many products that with our examples we can help you formulate your area (more technical or more payment, related to ML / AI, or sales, etc.). We believe that a good PM chooses their favorite product themselves and does not need to be led by the hand.
Yes, students who have successfully passed the course may generate a certificate and proudly add it to their LinkedIn profile to Licenses & Certifications, or upload it to Facebook in the Schools section.
You can be sure of the materials' quality and our mentors' experience. We've been teaching for many years, and we have thousands of happy PMs. Feel free to take a look at the student reviews for verification.
If you passed less than 30% of tasks and materials included the simulator you could refund your money in full.
If you passed less than 30% of tasks and materials included the simulator you could refund your money in full.
- Alex from ProductDoWe hope we answered all of your questions.
Still have more? Contact us via any messenger plug-in at the bottom right, or drop us a line at support@productdo.io, and we'll be happy to assist you.