# Worked shortlist for the fictional candidate

Use the source IDs in `source-facts.md` and candidate IDs in `README.md` to check this reasoning. These are GTM Vibes' editorial choices about Alex's next effort, not employer screening results. The source snapshot is October 26, 2026; recheck it before acting.

## O: Prepare a focused application or question

**Constraint status:** `no conflict shown` between O1 and C1. This resolves only the supplied remote-work comparison. It does not settle every employment condition.

**Work-evidence status:** `relevant examples`. E1 and E2 provide concrete production and analytical work to discuss against O2–O3. C3 meets the stated numerical experience floor; E3 addresses the named tool, without proving its required depth. Do not infer complete qualification from those matches.

**Preference status:** `unresolved` on the responsibility split. C2 favors hands-on work, but Alex needs to understand how the pod responsibility changes the week. E4 is mentoring, not formal management. O4 allows more than one route, so lack of prior formal management is not itself a demonstrated contradiction.

**Next action:** Prepare two concise accounts of E1 and E2. Ask: “How is this role's time divided between individual building/analysis, setting direction and people management, and what management responsibility exists at the start?”

**Revisit when:** The employer clarifies those responsibilities and any other conditions material to Alex. A predominantly managerial answer could make the role less aligned with C2 even though C1 remains compatible.

## V: Hold behind better-supported options, or clarify the gaps

**Constraint status:** `no conflict shown` between V1 and C1, with other terms still unresolved.

**Work-evidence status:** `material gap`. E1 and E2 are partly relevant to V2, but G1 and G2 leave central expectations in V3 unsupported. Five years alone does not resolve the missing evidence. HubSpot/API work should not be relabeled as hands-on ownership of a different platform.

**Preference status:** `mixed`: C2 and the role's emphasis need an honest comparison.

**Next action:** Keep this behind options with a stronger evidence match unless Alex can supply additional relevant work. If pursuing it, ask: “Which parts of the listed campaign and platform experience need to be demonstrated from day one, and would you consider adjacent systems experience?” State the actual gaps when asking.

**Revisit when:** Alex identifies a real example omitted from the packet, the employer clarifies flexibility, or Alex deliberately chooses to pursue this kind of work. A new learning project must remain labeled as learning, not prior professional delivery.

## F: Defer under the fixed constraint

**Constraint status:** `conflict`: F1 contradicts C1.

**Work-evidence status:** `relevant examples` for parts of F2–F3, especially E1. That relevance does not change the location conflict. The bonus-stack distinction in F3 is not the reason to defer.

**Preference status:** Some building work may appeal to Alex, but it does not determine the next action while C1 is fixed.

**Next action:** Defer rather than spend this application's preparation time now. If there is a reason to believe the arrangement has changed, verify that specific change with an authoritative source; do not presume an exception.

**Revisit when:** Alex changes C1 or the employer confirms a compatible arrangement. Another candidate who can meet F1 may reach a different conclusion using the same source facts.

## What the comparison did not decide

No role is labeled “fully eligible,” “guaranteed interview” or “best employer.” All three retain the unresolved terms identified in the packet. If an unsupplied condition is essential to a real candidate, add it to the worksheet and resolve it before treating the shortlist as ready for that candidate.

The result is an effort plan: prepare a focused case for O, hold or clarify V, and defer F under the current constraint. Keep the evidence trail and the condition for revisiting each choice. Do not add numerical scores that allow optional tool matches to cancel a fixed conflict.