Product Engineering interview guide

Every question carries the same frame: the team situation behind it, what it is actually testing, what a strong answer sounds like, and the flags on both sides. The red flags are specific wrong answers a confident engineer really gives — not 'does not know the topic'.

18 of 18 questions
The ticket says "Add a wishlist to the store." Before you estimate it, what do you want to know?Outcomes

The PM wrote the ticket after a competitor launched one. It has a mock of a heart icon on the product page and a "My wishlist" tab on the account page. Refinement is tomorrow and the team is expected to give a size.

Your team shipped "save cart across devices" last quarter, on time and without incidents. How do you know whether it was worth it?Outcomes

The feature took one engineer about six weeks. The quarterly review slide lists it as "Delivered". Nobody defined success before it started, and the manager now asks each engineer to present one thing they shipped and its impact.

Finance asks for a new discount type for one large wholesale customer, "just a small change to checkout". Your team is mid-quarter on other work. How do you respond?Outcomes

The wholesale customer places large orders by email today and finance keys them in by hand. The requested discount is tiered by quantity and applies only to their account. Checkout already has percentage codes and free-shipping codes.

Tell me about a decision you made on a feature, and the option you rejected.Decisions

A behavioural question in a product-engineering interview. The interviewer wants a real example; a hypothetical is allowed if the candidate says so. The follow-ups probe whether the reasoning survives contact with a sceptic.

In a planning review, a director asks you: "Will one-click reorder increase revenue?" You do not know. What do you say?Decisions

The team is proposing one-click reorder on the order page. The director has to pick two of five proposals for next quarter. There is no data on repeat purchase frequency by product category in the room, and the question is asked in front of the whole planning group.

On the same day you have to decide the wording on the "Place order" button and whether order numbers in customer-facing URLs switch from sequential ids to random ones. How do you treat those two decisions differently?Decisions

Order confirmation URLs look like /orders/104233. Security raised that sequential ids leak order volume to competitors. Separately, the designer wants to test "Pay now" versus "Place order". Both are small tickets on the same board.

Customers want to return items without emailing support. What is the first version you would ship?Shipping

Today returns happen by email: support checks the order, emails a label, and finance issues the refund when the parcel arrives. The PM's spec includes a returns portal, label generation via the carrier API, reason codes, exchanges, store credit and automatic refunds.

How do you use feature flags, beyond hiding unfinished code?Shipping

The store has a flag service that engineers use to merge incomplete work. There are a lot of flags in it, many of them on for everyone for months. The PM has never looked at it.

When is a feature done?Shipping

The team's board moves tickets to "Done" when the PR merges. The PM counts features shipped per sprint. Last month a delivery-date feature was "done" for two weeks before anyone noticed it showed the wrong date for one warehouse.

The team is redesigning checkout from four steps to one page. What single metric decides whether it worked, and what else do you watch?Measuring

The designer's goal is "reduce friction". Finance cares about revenue. Support has complained about address errors. The redesign will run behind a flag for a portion of traffic.

An experiment on free-shipping thresholds shows order completion up slightly in the variant after one week. The PM wants to ship it. What do you check first?Measuring

The variant lowered the free-shipping threshold. It ran for one week, which included a public holiday. The dashboard shows the variant ahead and marks it "significant". Nobody has looked at margins or returns.

The checkout dashboard is green: conversion flat, error rate low. Support says customers are furious about checkout this week. Who is right?Measuring

Support forwards a dozen tickets saying the page "spins forever" after paying. The dashboard counts orders created and HTTP 5xx rates. Nothing in either has moved.

The PM wants to add a mandatory account-creation step before checkout. You think it will hurt conversion. What do you do?People

Marketing wants more accounts for email campaigns and the PM has agreed to the change. The PM owns the roadmap; you own the checkout code. You have a strong opinion and no data from this store.

Refunds were delayed for three days because of a bug in your service. Write the first three sentences of your update to the finance lead.People

A change to the refund job skipped orders paid with a gift card plus a card. The fix is deployed and the backlog processed. The finance lead has to answer questions from the CFO and from customers' banks.

The designer hands you a cart mock that shows live stock for every item, updating as the customer watches. How do you respond?People

Stock lives in a warehouse system that is queried in batches. The mock is polished and has been shown to the PM. The designer's intent is to reduce the disappointment of items going out of stock at payment.

Checkout was down for about forty minutes on a Saturday. You were on call; the fix is in. What else is your job?Ownership

A config change to the payment timeout caused all card payments to fail. You rolled it back. Support fielded complaints; some customers placed duplicate orders when they retried. It is Monday morning.

The promotions code in checkout is hard to change and every new discount takes weeks. How do you get time to fix it?Ownership

Marketing keeps asking for new promotion types. Each one takes weeks and has caused a pricing bug twice this year. The PM has a full roadmap and has previously declined "refactoring sprints".

Product reviews on the store get almost no new reviews and cause regular moderation tickets. How would you propose removing them?Ownership

Reviews shipped years ago. Few customers write them, support spends time moderating spam, and the reviews widget slows the product page. Some old products have many reviews; marketing likes showing star ratings.