# Make a trustworthy feedback readout

Quaymere · Product-management work sample
All company, account, participant and incident information is original synthetic material.

## Situation and outcome
Quaymere is a fictional B2B operations product that exports daily files, manages destination approvals and provides searchable records. The product lead needs a weekly readout before a separate planning discussion. Your outcome is a reviewed theme report **or a justified evidence-gap record**, not prioritization, tickets, a roadmap commitment or a customer promise.

The feedback period is 2026-09-14 through 2026-09-27 inclusive. Examine 48 selected records from support, sales, research, success and engineering alongside a prior digest and an AI first grouping. Those analyses are drafts, not evidence authority. Work with the supplied source IDs and source context; do not contact fictional accounts or seek private data.

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

Choose a defensible synthesis question within the stated period, explain relevant source coverage, resolve or preserve conflicting interpretations, and prepare the reviewed readout for the product lead. You own the synthesis recommendation; security and source owners validate their domains. Planning and customer promises remain separate decisions.

## About the team
A B2B operations software team preparing a weekly feedback readout for the product lead.

Agents may draft groupings; a person verifies evidence, counts and uncertainty.

People own evidence approval, escalation and any later prioritization or customer commitment.

## Work to complete
1. Define or refine the question, period, boundary and relevant coverage. Read sources/coverage-and-access.md before making population claims.
2. Audit the first grouping against original records. Retain, merge, split, reject or leave records unplaced with a stated reason. Keep contrary evidence visible; distinguish a quoted customer observation, a seller inference and missing evidence.
3. Explain record counts and unique-account counts for your chosen themes, including repeated escalation or copied-observation dependencies. Do not turn account counts into user counts or population prevalence without an eligible denominator.
4. Treat severity separately from frequency. Identify consequential exceptions and the human verification owner without overstating impact or declaring an incident closed.
5. Apply the correction note (U001) in your download like the other sources. Propagate justified revisions and note limitations, and keep the original reading of any record it changes visible next to the revised one. The revision log is your own account of how you worked.
6. Produce a concise handoff, with peer-review questions, missing evidence and owners. A well-supported evidence-gap record is a valid outcome when conclusions cannot be sustained.

## 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 seven typed questions about your own files, for about 10 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-identity-and-context-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.
- report.md: at most two pages equivalent (about 900 words); a reviewed digest or explicit evidence-gap record. Explain counts, contrary evidence, confidence, limits and handoff.
- evidence.csv: required columns source_id,theme,disposition,account_id. One or more rows per record is permitted, but map every R001–R048 at least once. Record IDs and account IDs must remain traceable; preserve original identity and record corrections explicitly if available. Add fields such as rationale,observation_group,evidence_version,contrary_to as useful. Cite the correction note as U001.
- revision-log.md: material changes, verification checks and remaining gaps. No private prompts or unrelated files.
- questions.md: a short peer-review question list with suggested owners and decision boundaries.

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
- Judges what the evidence supports
- Checks and repairs the analysis
- Hands off to the right owners
- Explains their choices

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.
