Study Guide

Tech Foundations for Product Managers

10 modules · 30+ questions · Level: PM without engineering background

Content 1/3

How Software Works

Before diving in, watch this short video for a bird's-eye view of how the web works — it sets the foundation for everything in this module.

A quick overview of how the internet and software work together — great context before we go deeper.

Content 2/3

The Basics: Frontend, Backend & Database

Every digital product has at least three layers working together. Understanding where each layer begins and ends is one of the most practical skills a PM can develop — it directly affects how you scope work, estimate effort, and communicate with your engineering team.

Frontend is everything the user sees and touches — the interface. In a mobile app, it's the screens, buttons, lists, and animations. In a website, it's the page in the browser. The frontend is the "face" of the product. When Netflix redesigns its home screen to show bigger thumbnails, or when Airbnb updates the search bar on mobile, those are frontend changes. They're visible, they feel immediate — but on mobile apps, they require a new release that goes through App Store or Google Play review before users can see it.

Backend is the brain behind the scenes. It's where business rules live, logic runs, and communication with other systems happens. The user never sees the backend directly — but they feel it constantly. When Spotify generates your "Discover Weekly" playlist every Monday, that's the backend running a machine learning algorithm against your listening history. When Uber's app shows surge pricing during a storm, the backend is calculating demand and supply in real time. None of that involves changing the app on your phone — it all happens server-side, instantly, without any update required.

The three layers of every digital product

🧠 Check your understanding

A team wants to change the feed ranking algorithm. Which layer is primarily affected?

Content 3/3

Database is the long-term memory. It stores information that needs to persist: user accounts, orders, product catalogs, history. Without it, the app would "forget" everything every time it closed. When you pause a Netflix show and resume it three days later on a different device, the database remembered exactly where you left off. When you look at your Uber trip history from two years ago, that's a database query returning records that were stored the moment your trip ended.

Think of a restaurant. The frontend is the dining room — what the customer sees: the ambiance, the menu design, the decor. The backend is the kitchen — where food is prepared, recipes are followed, and orders are prioritized. The database is the pantry and the reservation book — it stores what's available, who ordered what, and the full history of every transaction.

A request flowing from the browser to the database and back

💭 Reflect (optional)

Think of an app you use every day. Can you identify what is frontend, backend, and database in it?

Q1What is the difference between frontend and backend?▼

Frontend is everything the user sees and interacts with (the interface). Backend is the logic, business rules, and data processing that happen on the server — invisible to users, but felt in every interaction.

Q2Why can backend changes be deployed instantly while mobile app changes need App Store review?▼

Backend runs on servers you control — you update the server, all users get the new behavior immediately. Mobile app code runs on the user's device, so any change to the app itself requires a new version to be published and downloaded through the App Store or Google Play.

Q3What is a database and why does every app need one?▼

A database is persistent storage — it remembers data across sessions, devices, and time. Without it, apps would reset to zero every time they were closed. It's what allows Netflix to remember your watch position, Uber to show your trip history, or Spotify to keep your playlists.

Takeaways for PMs

When you request a feature, the first question to ask is: which layer does it touch? A backend change ships the same day. A mobile UI change might take two weeks to reach users after App Store review.
"The data already exists, just display it somewhere else" is one of the most common PM assumptions that turns out to be wrong. Sometimes that data isn't stored at all — and storing it requires a schema change, a migration, and testing.
When an app behaves differently on web vs. mobile, the reason is almost always in the frontend layer — not the backend. Both use the same API; the difference is how each client renders the response.
You don't need to know how each layer is built. You need to know where to look when something breaks — and now you do.

Found an error? Report it