# Triage two weeks of feature requests

Eddowick · Product-management work sample
All company, customer and product information is original synthetic material.

## Situation and outcome
Eddowick is a fictional hosted build-and-deploy platform with about 1,900 paying accounts. Customers run their jobs on runners that Eddowick hosts or on runner agents they host themselves. You are the product manager for Pipelines. It is Monday 5 October, last week's triage pass was skipped, and a nightly triage agent has drafted a disposition and a reply for most of what arrived from 21 September to 2 October. Nothing has been sent. The agent also reports what it counted, and the backlog snapshot shows who had already asked for each item.

Your outcome is the **triage record** for the pass: a log that gives every record a disposition, a backlog item and an account; the replies you would send; a short note of what needs someone else's decision or action now; and a revision log of what you changed from the AI draft. A well-argued "this item needs a question first" or "the pass is honest about what it did not get to" is a valid result. Setting priority, giving product delivery dates, deciding a customer's contract request, diagnosing a bug, running a security incident response (the reply to the reporter is part of your work) and running discovery calls are not part of this work.

The evidence period is 2026-07-06 through 2026-10-02 inclusive: reference notes from July onward and items received 21 September to 2 October. Examine 47 records: the triage rules and other reference notes, and the items that came in through support tickets, account notes, sales requests, the community forum, in-app feedback and internal notes. The records and the correction note (U001) stand in for the people; do not contact fictional organisations or seek private data. The AI draft is not evidence authority. Work with the supplied source IDs and account IDs.

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

You own this week's triage pass for Pipelines: every item's disposition, the replies and the referrals, prepared to send today. You may link or add backlog items (priority unset), ask for clarification, decline with a reason, and route bugs and security reports. You may not set priority or product delivery dates, accept or refuse customer-specific or contractual commitments (the commercial review decides), or change the triage rules.

## About the team
A developer-platform product team working through two weeks of inbound feature requests and feedback after a skipped weekly triage.

A support bot tags and forwards feature requests, a community assistant writes the weekly forum digest, and a nightly triage agent drafted the dispositions and replies you audit. People send every reply and own commitments.

The commercial review (VP Sales and Head of Product) decides dates, contract terms and customer-specific builds; the security on-call and support engineering own their queues; the monthly planning review sets priority; the Head of Product owns the triage rules.

## Work to complete
1. Read sources/coverage-and-access.md before making claims about demand. Then read the triage rules, which are the first record.
2. Check the AI draft against the original records, row by row, and check what it left out. Keep what the records support, and change only what they do not, naming the record that shows it. A row that still stands is kept, with its reason.
3. Give every record one disposition. If you did not get to a record, the disposition is "not reviewed": write it in the disposition and backlog_item columns, say in the rationale what stopped you, and list those records in the README coverage section. Never leave a cell empty or guess to fill it. Check each item against the backlog first, shipped and declined items included. Read the need behind the request, not only its wording, and write a new item as the problem, not the requested solution.
4. Count by account, not by record. Say how many accounts stand behind each backlog item this pass and how many with the accounts linked before it, in the counts-and-coverage section of README.md. A repeated or relayed record is not a second account asking.
5. Say what each source can bear, in the same section. Keep rare but serious reports, contrary evidence and unsupported claims visible, and ask rather than guess when a request is unclear.
6. Write the replies a person would send. A reply is owed to each person who wrote in or is waiting for an answer (tickets, forum posts, in-app feedback, account notes and customer or prospect requests relayed by sales). The reference notes, the weekly digest and internal notes need none. One shared draft is enough for several records that get the same answer, with their record IDs listed; write a separate reply only where the content differs. Replies give no delivery or availability dates and make no commitments about delivery, customer-specific builds or contracts, and say plainly what each request does and does not commit Eddowick to.
7. Send what needs someone else now to the right owner with what they need to act, and leave the decision with them.
8. Apply the correction note (U001) from your download, as you would any other source. Carry each change through the log, the replies, the decisions note and the revision log, and keep the earlier reading visible.

## 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-correction-and-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 and say how you used the correction note (U001), and add a short counts-and-coverage section: the accounts behind each backlog item this pass and with the accounts linked before it, what the sources can and cannot bear, and which claims in the records are unsupported.
- triage-log.csv: it already has one row for each of the R001–R047 records, with the source ID and the account ID filled in. Fill in the empty columns on every row. Use a disposition such as link, add, clarify, decline, escalate, route, reference or not reviewed. Put the backlog item the record belongs to in backlog_item (an existing BL number, a short name for a new problem, or the destination for a clarification, decline, referral or reference), and a short reason in rationale. You may add use_case, duplicate_of and reply_ref columns. Do not retype or delete source IDs or account IDs. If the correction note (U001) changes a record, revise its row, put U001 in the evidence_version column and keep the earlier reading visible in the revision log.
- replies.md: the replies a person would send, one per destination and separate replies where the content differs, about 700 words at most. Replies are drafts for a person to send.
- decisions-now.md: what needs someone else's decision or action now, who, by when and what they need to know, about 400 words at most. Do not decide for them, and do not set priority or product delivery dates; record any deadline the records already give.
- revision-log.md: each problem you found in the AI draft with the record check that shows it, the rows you kept, the items the draft did not place and what the correction note (U001) changed, about 300 words at most. No private prompts or unrelated files.

Words are counted in the prose of each document you write; headings, tables, the triage log 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
- Reads the need behind each request
- Checks and repairs the AI draft
- Hands off to the right owners
- Explains their choices
- Routes requests and replies honestly

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.
