Behind the scenes, with made-up data. This is a read only copy of the admin for a fictional candidate. Reports, traces, spend and chat were produced by a scripted stand-in; the evaluation timeline shows real results of real models on fictional cases. Nothing here can be changed. Back to the real site
Reverse Apply

Settings

The CV visitors may see quoted

From the file /app/tools/sample_cv.md

Headings (a line starting with #) become the section names shown next to a quoted line. Email addresses and phone numbers are removed automatically. Saved in the app's database, not in the code or the repository, and it replaces any earlier upload.

Limits and spend caps

Visitors never see the amounts, only that a limit is reached

Extra facts

They count as evidence in your own runs only, never in visitors' reports. Write only what you can defend.

Cover letter rules: recruiters

Where the default comes from: adapted on 2026-11-11 from your own writing and positioning rules (no "new to me" lines, claims at the scope the CV line states, plain words, no flattery). They are copies, not links: a change in your project files does not reach the app. Since 2026-11-12 the default no longer opens with a question; compare drafts before you decide whether it should.

Cover letter rules: visitors' own CVs

Neutral defaults, with none of your own positioning: the same proof-first opening, without your voice. Changes here never affect letters written as you. Whatever you write in either box, the code checks every draft: at most 320 words, no banned words, no phrases that point to a gap, every body paragraph citing a CV line that exists, and no claim about the writer inside a question paragraph. These are checked in code and cannot be switched off here.

The CV your own runs read

Read-only here

Your runs read /app/tools/sample_cv.md. Contact lines are never quoted to visitors.

# Ada Example

Product manager for search and developer platforms

Lisbon, Portugal | ada@example.com | example.com/ada

## Profile

Product manager who has led product teams for nine years, with twelve years in product across developer platforms,
search and data infrastructure. I work with engineers and data scientists on relevance, and I read the results myself.

## Experience

### Example Corp, Director of Product, Search Platform

- Product owner for the site search API used by 2,000 developers; moved the share of queries answered in under 200 ms from 71% to 93%.
- Led a team of eight across engineering, design and data.
- Set up weekly relevance reviews with the data team and a labelled set of 400 queries.
- Shipped semantic search using an off-the-shelf embedding model and measured it against the keyword baseline before release.
- Wrote the public API guidelines and ran the developer advisory group of fourteen customers.

### Northfield Systems, Senior Product Manager, Data Platform

- Owned the ingestion and indexing roadmap for a managed data platform; cut onboarding from three weeks to two days.
- Introduced usage-based billing for the storage tier together with finance and engineering.
- Ran quarterly planning for three squads and coached two junior product managers.

### Side project: Notes search

- Built a small hybrid search tool over my own notes with keyword and vector retrieval, and a test set of 120 questions.

## Skills

Search relevance, embeddings, API products, developer experience, pricing, experimentation, SQL.