# Get price-alert tracking ready to trust before launch

Hollenmere · Product-management work sample
All company, customer and data in this exercise are original synthetic material.

## Situation and outcome
Hollenmere is a fictional marketplace for used outdoor and sports gear in the US and UK, with about 420,000 weekly active buyers on iOS, Android and web. In its new price alerts feature, a buyer taps "Keep me posted on this price" on a listing and is told when the listing's price drops, optionally below a target price. Alerts arrive by push on the apps and by email on web, and sellers of watched listings get a nudge to drop their price. A "N buyers watching" badge for sellers is planned for phase 2.

You are the Saved and Alerts product manager, in post since Monday 28 September. The feature has been in a 10% beta on iOS and web since Monday 21 September, and Android joined on Wednesday 30 September. Today is Monday 5 October. App code freeze for release 6.15 is Wednesday 7 October, the release readiness review is on Thursday 8 October, where you state the instrumentation status, and the full rollout is on Tuesday 13 October. An analytics agent drafted the tracking plan in August, built the beta dashboard from it, and overnight wrote a v2 specification summary and a beta readiness statement. Nobody has checked them.

Your outcome is a **final instrumentation specification (v2)** for price alerts, a **verification log** that gives every event and every metric a status against the team's own checklist, and a **handoff** that routes whatever fails to the people who own it. "Reporting is confirmed", "reporting is not confirmed, defects raised" and "blocked until a review decision" are all valid results if the records support them. Building fixes, choosing the launch, changing what a metric means, analysing how well the feature works and designing an experiment are not part of this work. The privacy reviewer's and the engineering lead's replies on the open items are in your download, in the correction note (U001).

The evidence period is 2026-07-01 through 2026-10-05 inclusive. Work with 59 source records (the feature's requirements, success metrics, release plan, decision rights, privacy standard, verification checklist and event routing rules; the tracking plan; the data catalogue; engineering review comments; the privacy referral; beta extracts; the dashboard tiles; QA checks; and team messages) and an AI-drafted summary. The beta extracts are aggregates; you cannot query anything live. The AI draft is not an authority. Use the supplied source IDs and context; do not contact the fictional teams or seek private data.

## Your role
You are joining the team as Product Manager.

You own the price-alert instrumentation specification and its verification sign-off for the 8 October readiness review. You may change the spec, ask data engineering to block or strip data, file defects and refer fields to privacy. You may not clear personal data, decide remediation of data already collected, change metric definitions or decide the launch.

## About the team
A product team that owns a new price alerts feature in a 10% beta, preparing the instrumentation status for the release readiness review chaired by the Head of Buyer Product.

An analytics agent drafts tracking plans and builds the dashboard tiles from them, an AI digest summarises the beta weekly, and QA runs an automated payload checker. People own specification sign-off, clearance of personal data, fixes, metric definitions and the launch.

The product manager signs off the specification and its verification; the privacy reviewer alone clears personal data and decides remediation of data collected outside the standard; engineering leads decide how and when fixes are built; the Head of Buyer Product owns metric definitions and decides the launch; the PM recommends and routes but decides none of these.

## Work to complete
1. Read sources/coverage-and-access.md before you make claims about what the extracts cover. The requirements, metric definitions, release plan, decision rights, privacy standard, checklist and routing rules are the first seven records.
2. Audit the AI draft against the original records, row by row. Change only what the evidence warrants. A row that still stands is kept, with its reason.
3. Verify every event in the tracking plan against the team's checklist, and say for each metric whether it computes to its written definition. Use the right source of truth for each volume, apply the checklist's rules as written, and tell apart what a record shows, what an AI tool wrote, what a person claimed and what is only a plan. A repeated or re-posted statement is not a second observation. Keep contrary evidence visible.
4. Write the final specification (v2): which measurement questions it serves and which it sets aside, each event with its trigger, properties, identifiers, platforms and the metric it feeds, how each field that can hold personal data is handled and by whose decision, what changed from v1, and the criteria that will verify each event.
5. Route every defect and open item to the person who owns it, with what you ask of them and by when, and act on what the company's rules in the records require of you. Say in one line what Thursday's review can rely on.
6. Read the correction note (U001) in your download like any other source and apply it. Carry each change through the specification, the log, the handoff and the evidence table, and show which earlier reading each change replaces. You do not need to write a version from before the note.
7. Keep to your role. You may recommend and route; the people named in the records decide what is theirs.

## Time
You have 90 minutes of work time. The clock starts when you press Start.

After that comes a 10-minute break, then a written interview: up to eight typed questions about your own files, for about 15 minutes. If you submit early, your break starts straight away.

## Mid-task correction
There is no mid-task correction in this take-home. Everything you need is in the files you download at Start, including the correction note **updates/U001-privacy-decision-and-engineering-notes-v1.md**. Read it with the other sources, apply it where it changes your work, and cite it as U001.

## Tools and help
Use any tools and help you like: AI tools and agents, search, your own notes, friends or colleagues. You don't need a paid tool, an API key or an account.

Nothing you do in your own tools is watched. Only your files and your interview answers are reviewed. When you submit, you can say which tools or help you used. That is optional, and leaving it empty is never held against you.

## Submission
Hand in one ZIP with these files at its top level. Start from the copies in the templates folder.
- README.md: list every file you hand in, at most 150 words.
- instrumentation-spec.md: the final specification, at most 1,200 words, table cells included, headings and record IDs not. Use the template's six headings.
- verification-log.md: a status for each event (confirmed, defect, not built or not yet verifiable) with its checks and records, whether each metric computes to its definition, and what cannot be verified yet, at most 600 words.
- evidence.csv: your template already has one row for each of the 59 records (R001–R059), with its source ID and event code filled in. Fill in your own finding in the finding column and a value such as supports, contradicts, limits, context or not used in the use column, and add a short rationale. Leave no record out. Add a row only when a record bears on a second finding. Keep the original event code visible and record any correction explicitly. Fill in observation_group where records repeat one observation. Cite the correction note as U001.
- handoff.md: what you do today, each defect report, the privacy referral and blocker record, your questions for owners, what the 8 October review can rely on, and what changed after the correction, at most 700 words.

Words are counted in the prose and table cells of each document you write; headings, table borders, record IDs and the README do not count.

Use plain text files only: .md, .txt, .csv or .json. Put your work in the files themselves; a link to a document somewhere else does not count. Your ZIP can be up to 5 MB, or 20 MB unzipped, with at most 39 files of up to 2 MB each. Programs, macros, password-protected ZIPs and ZIPs inside your ZIP are not accepted.

Upload your ZIP on your take-home page and wait for **Received and checked**. It normally appears within a few seconds of the upload finishing. If it has not appeared after a minute, upload the ZIP again; if it still does not appear, use **Help and support**. You can replace your ZIP until you submit. Submitting is final and starts your break.

If time runs out before you submit, the last ZIP marked **Received and checked** is handed in for you. If none was received, the team is told that you need support.

If something goes wrong, use **Help and support** on your take-home page. A technical problem is never counted against you. Writing to us does not pause the clock.

## What happens next
The written interview covers these parts of the job:
- Checks sources and counts
- Weighs evidence and risk
- Checks and repairs the AI draft
- Hands off clearly
- Explains their reasoning
- Specifies measurable events

An AI then drafts a review from your files and your answers. Each point quotes what it rests on. A person at the company reads the review and makes any decision. No one is hired, rejected or ranked automatically.
