Intermediate interview questions in Product Management, page 26
Design an analytics event schema
Consistent object-action naming, snake_case, typed properties with units, and shared context like user, session, timestamp.
Transform a Time Series for a Gradient Boosting Model
Tests your ability to convert a sequential problem into a tabular one. A great answer covers creating lagged/rolling features and time-based features (e.g., day of week), and crucially, specifies a time-aware validation split.
Transform a time series for a supervised learning model?
This tests your ability to reframe a time series problem for tabular models. A great answer explains creating features from lags, rolling windows, and calendar data, then emphasizes using a time-aware validation split. A red flag is forgetting validation.
Definition of Done vs. Acceptance Criteria: What's the difference?
Tests your grasp of Agile quality gates. Define both, then contrast scope (global DoD vs. local AC) and ownership (Team vs. PO). Connect them to creating a shippable, valuable Increment. A red flag is treating them as interchangeable.
Using mission to prioritize debt vs new feature
Map each task to mission impact, time horizon, and reversibility; weigh learning value against risk.
Design a multi-touch attribution model
Pick a model (time-decay, position-based, or data-driven Shapley), stitch touchpoints by user identity into ordered paths, then assign fractional credit.
Migrate a breaking analytics schema change
Dual-write both fields during overlap, backfill history, migrate consumers, then deprecate the old field.
Propose a multi-touch attribution model and its data pipeline
This tests your ability to choose a practical data model under real-world constraints. Propose a time-decay or position-based model, then describe the data pipeline: event collection, identity resolution, and aggregation. A red flag is ignoring signal loss.
Propose a multi-touch attribution model and its data pipeline
Tests your grasp of attribution models and their data engineering needs. Propose a rule-based model (e.g., time-decay), outline the data pipeline for it, and acknowledge privacy-driven signal loss. A red flag is ignoring the challenge of identity resolution.
A PBI is vague. How do you get clarity?
This tests ownership and proactive communication. A great answer involves documenting questions in the ticket, engaging the PM and tech lead for a discussion, and updating the ticket with clear acceptance criteria before starting any work.
Framing a build debate with the mission
Separate user simplicity from internal complexity, weigh new-framework risk, decide via mission and reversibility.
Implement CDC from OLTP to warehouse
Contrast log-based CDC with query-based timestamp polling, cover deletes and load on source, then pick log-based for minimal impact.
Design a streak-saver mechanism
Timezone-aware streak state, capped saver inventory with replenish rules, and A/B testing forgiveness against retention plus guardrails.
Implement CDC from an OLTP database to a data warehouse
This tests your grasp of production system trade-offs. A good answer compares log-based and trigger-based CDC, focusing on source impact and data fidelity, then recommends log-based for its low overhead.
How would you implement Change Data Capture (CDC)?
Tests your grasp of data replication trade-offs. A great answer compares log-based CDC (low impact, complete) with query-based methods (higher impact, misses deletes), and recommends log-based CDC for its minimal production impact.
How do you handle an unavailable Product Owner?
Tests your ability to solve process bottlenecks collaboratively. A great answer starts with data, then direct communication with the PO, proposes solutions like office hours, and escalates only as a last resort.
Designing an API for power vs novice personas
Power users want control, batching, and precise errors; novices want defaults, guardrails, and guidance; both want consistency.
Define a consistent day across timezones
Store events in UTC, capture the local/source timezone, then convert to a single reporting timezone at query time.
Components of a testable A/B hypothesis
A specific change, a predicted directional effect on one primary metric, a rationale, and a measurable success threshold.
How do you handle timezones for a global daily sales report?
This tests your ability to translate ambiguous business needs (a "day") into a robust data model. First, clarify the business definition of a day. Then, store all event times in UTC and convert to the target timezone at query time for reporting.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles