← All questions
Technicalstandard
Explain how a third-party login like 'Sign in with Google' works.
How to approach it
Describe the flow in user terms first, then name what is passed between the parties and why the app never sees the password.
How a strong answer opens
“From the user's side: you tap the button, sign in on Google's page, approve what the app may see, and land back in the app signed in. The app never sees your password.”
Outline of a strong answer
Try answering out loud for a few minutes before you open this.
- User taps the button and is sent to the identity provider
- User signs in there and approves the requested permissions
- The provider sends back a one-time code, which the app's server swaps for tokens; the app never sees the password
- The app uses the token to get basic profile info and create a session
- Benefits: faster sign-up, no new password
- Risks: dependence on the provider, account linking edge cases
Where this question usually goes wrong
Saying Google shares your password with the app, or skipping the step where the user approves what the app can access.
Learn the method
APIs and integrations in Module 6, Technical for PMs.
The full kit has worked answers in full, start to finish, for every round type. $129 once.
More technical questions
- Explain what an API is to someone who isn't technical.
- What's the difference between REST and GraphQL, and when would a PM care?
- What's the difference between latency and throughput, and how would each show up for users?
- Your checkout went down for an hour. What do you do during the outage and after it?
- What happens when you type a URL into a browser and press Enter?