Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Primary Key vs Unique Key

EasySQL & Data Manipulation00:00
Practice interviewer
In session
5 left
00:00

Your question is Primary Key vs Unique Key. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Context

At companies like Notion, interviewers often ask this to test whether you understand table design, data integrity, and constraint behavior in relational databases.

Question

Explain the difference between a primary key and a unique key in PostgreSQL. Your answer should cover:

  1. What each constraint does
  2. Whether each allows NULL values
  3. How many of each can exist on a table
  4. When you would choose one over the other
  5. A simple example showing both on the same table

Scope Guidance

Keep the explanation practical rather than theoretical. The interviewer is usually looking for a clear comparison, correct handling of NULL, and an understanding that both enforce uniqueness but serve different modeling purposes. A strong answer should also mention that a primary key is the main row identifier, while a unique key is commonly used for alternate candidate identifiers such as email or username.