# Segment positioning proposal

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

## Situation and outcome
Quenvorlen is a fictional company of about 220 people. It sells wireless pressure, flow and dew-point sensors for the compressed-air network of a manufacturing plant, with software on top: Leaklamp flags a new air leak, pressure-drop alerts warn at the point of use, an energy report gives kWh per plant, and Mendvessa, a beta AI assistant, drafts maintenance work orders for a person to approve. Dewnalveth, the dew-point sensor, has been on sale since May.

You are the product manager. The VP Product has asked you to write the positioning and value proposition for each of three target segments for FY27 planning: multi-plant discrete manufacturers (SG1, the core), food and beverage processors (SG2, the growth target) and GMP pharmaceutical and medical device manufacturers (SG3, an option). Today is Tuesday 6 October. The review with the two approvers, the product marketing lead and the VP Product, is on Friday 9 October. The team's positioning agent wrote a first draft overnight on 29 September, and nobody has checked it.

Your outcome is a **proposed positioning set** the approvers can decide on: for each segment you can stand behind, a value proposition and a positioning statement with the proof behind each; for any segment you cannot yet stand behind, a gap record; and a review note that lays out the decisions, the open disputes and who must sign off each proof point. Everything stays "proposed, not approved". A well-argued "the evidence does not support positioning this segment yet" is a valid result. Choosing or sizing segments, pricing, campaign and ad copy, running the message-check sessions, and approving, publishing or signing off claims are not part of this work. The message check is not run by you: its findings are in the correction note (U001) in your download.

The evidence period is 2026-06-01 through 2026-09-30 inclusive. Work with 62 source records (the request and rules, product facts, competitor pages, customer and prospect interviews, sales notes, call recaps, customer success notes and marketing material), and an AI-drafted positioning set. The records are supplied, not run by you. The AI draft is not an authority. Use the supplied source IDs and context; do not contact the fictional teams or customers or seek private data.

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

You own the positioning proposal for the in-scope segments: you judge per segment whether the evidence is sufficient, draft each value proposition and statement, revise after the message check, write the gap record and research ask, and prepare the review for the approvers. You propose proof points for external use. You may not approve or publish positioning (product marketing lead and VP Product), change the segment list (strategy), sign off air-quality or compliance claims (quality and regulatory), clear customer names (customer success) or write campaign copy.

## About the team
A product team that proposes per-segment positioning for FY27 planning to the product marketing lead and the VP Product, who approve it before messaging, sales enablement and the strategy update use it.

A positioning agent drafts the first per-segment set, a research agent writes a weekly market digest, marketing's AI assistant writes ad variants, and sales and success calls are summarised with AI. People own the statements, the proof points and every sign-off.

The product marketing lead and the VP Product approve positioning; customer success clears customer names and figures; quality and regulatory signs off air-quality and compliance claims; strategy owns the segment list; the PM proposes and routes but decides none of these.

## Work to complete
1. Read sources/coverage-and-access.md before you make claims about what the records cover. The request, the segment definitions and the claims policy are among the first records.
2. For each segment, assemble what the records say about who buys and why, what the buyer uses today, and what each claim rests on. Count customers and prospects as accounts, not as records: a repeated, copied or re-summarised record is not a new account, and a number in a deck is not a source. The counting unit is the company: one customer or prospect is one account however many plants or CRM entries it has. Use the account ID on each record, and when the records or the correction note show that two IDs are the same company (for example a second plant filed as its own CRM account), count them once and say which IDs you merged.
3. 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.
4. Judge, segment by segment, whether the evidence is enough to position on. Where it is, write the value proposition and the positioning statement (target, frame of reference, key benefit, reason to believe). Where it is not, write a gap record instead. Say how confident you are, and what would change your mind.
5. Propose proof points for external use, each with the permission or sign-off it needs. Tell apart what a record shows, what an AI tool wrote, what a person claimed and what is only a plan, and keep contrary evidence visible.
6. Write the review note for the two approvers: the decisions you ask of them, the disputes that stay open, and the proof points by permission status.
7. Apply the message-check findings in the correction note (U001) from the start. Carry each change through the positioning, the evidence table and the review note, mark your set v1.1 and keep the AI draft's earlier wording visible next to each revised wording in the change note.
8. 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-message-check-findings.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.
- positioning.md: the proposed set, at most 1,000 words. For each segment you position: the value proposition (the buyer's jobs, pains and gains mapped to capabilities; how you differ from the alternatives that segment actually uses; proof points with record IDs) and the positioning statement (target, frame of reference, key benefit, reason to believe; other forms that cover the same four parts are fine), your confidence, and the version, marked "proposed, not approved".
- gap-record.md: any segment or element you do not position, at most 300 words: the questions the records leave unanswered, the sources you checked, the smallest research that would close them and who receives the request.
- review-notes.md: for the approvers, at most 450 words, including the change note: the decisions asked of them, the open disputes, the proof points by permission status with the sign-off each needs, and what changed because of the message check and why.
- evidence.csv: the template already has one row for each record, R001–R062, with the record ID and account ID filled in. Do not type IDs. For each row, put SG1, SG2, SG3 or none in the segment column and fill in the use (benefit, alternative, proof point, contrary, gap and excluded are suggested; free text is accepted). You may add a row for a record that bears on a second segment. Record corrections explicitly, and add element, rationale and evidence_version values as useful. Cite the correction note as U001.

Word limits count every word in headings, paragraphs and table cells, and not table borders or the evidence table.

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 AI draft
- Hands off to the right owners
- Explains their own work
- Positions each segment on its evidence

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.
